This is a very serious bug.CyberTod wrote:
Some variables in notifications seem to be missing, for example :
[Service.Status]
[Service.ProblemDescription]
Thank you. The fix for this will be included in next release.
Any chance of getting the dude on PPC?
Can u reproduce this problem
dudebug.png
As u can see on the picture (in label appearance) Dude can read two functions but probe says "time out"
After rebooting Mikrotik Device - where Dude is installed all back to normal for some time
Edit. I inspected the problem, I come to this findings
pic3.png
For some reason Dude stop reading values from device, as u can see on picture values are wrong they are "stuck" at the point where dude probably lost connection to the device but for some reason Dude cant reprobe or cant get new values from the Device
But when I try dabble click on device in RouterOS TAB - Interfaces I can see interfaces as it should be (on ether1 bits are rolling every second as traffic passing by)
pic2.png
That mean Dude have access to the device
After Rebooting Dude server Functions- start reading again and Probes go up again.
Another thing on Device label as u can see two from tree probes are down Device have orange colour as normal but there is no info about 2 probes on label [Device.ServicesDown]
Function are made using ros_command for example "ros_command(":put [/system resource get cpu-load]")" and etc. etc.
I have totally the same problems with notifications.Permit only login to hesitate, not allowing api, winbox web, etc.
+1 Radius login
Serious problem..
Some variables in notifications seem to be missing, for example :
[Service.Status]
[Service.ProblemDescription]
try now.... 6.38rc9 is availableERROR: missing dude-6.37.1-tile.npk (on Current/Stable channel)
ERROR: missing dude-6.38rc8-tile.npk (on Release Candidate channel)
you know there are old fashion way of upgrading - downloading packages manually, uploading them to the router and rebootingERROR: missing dude-6.37.1-tile.npk (on Current/Stable channel)
ERROR: missing dude-6.38rc8-tile.npk (on Release Candidate channel)
TheDude package 6.38rc8 download link in the MT website was broken too.you know there are old fashion way of upgrading - downloading packages manually, uploading them to the router and rebootingERROR: missing dude-6.37.1-tile.npk (on Current/Stable channel)
ERROR: missing dude-6.38rc8-tile.npk (on Release Candidate channel)
I think it's not possible. All packages must be same versionIs it possible to upgrade only dude package to 6.38rc on the CCR side?
These values will keep updating, but it might take some time, we will see if we can improve it.For some reason Dude stop reading values from device - Dude cant reprobe or cant get new values from the Device
Another thing on Device label as u can see two from tree probes are down Device have orange colour as normal but there is no info about 2 probes on label [Device.ServicesDown]
Fixed in 6.38rc9my email notifications doesn't work anymore
i get ERROR SENDING EMAIL: DNS RESOLVE FAILED
Will try to reproduce the problem.we are having a similar problem, SNMP queries will stop going out from the DUDE server after a short while.
We confirmed that there was no SNMP request leaving the dude server after about 5 minuets of operation
Reported for fixing.But there is a new bug - popup and flash notifications not working me.
Reported for fixing.upgraded to 6.38rc9 ....
can't connect via WINBOX
No you have to update the system package too.Is it possible to upgrade only dude package
Can you please give more detail ? Could not see any problems with adding devices.otgooneo:
This is release still doesn`t have possibility to add device with mandatory basic values.
Me too . support says - Must remove dude server from mikrotik, when winbox is works.After update to 6.38rc10 still can't connect via WINBOX...
But just Dude server is the reason for my testing rc versionsMe too . support says - Must remove dude server from mikrotik, when winbox is works.After update to 6.38rc10 still can't connect via WINBOX...
Thanks for you advice! It is not really so difficult and I've done it before my question. But I interested by telegram notifications from The Dude. I think that for this advantage would be enough add functionality /fetch to The Dude.Please add in notifications any metod to post messages
/fetch from Router os
/tool fetch url=”https://api.telegram.org/bot153358077:A ... unnel_DOWN” keep-result=no
or native telegram support (https://1spla.ru/blog/telegram_bot_for_mikrotik/)
is it really so difficult?
Great monitor but can not notify anybody.
Thanks for you WORK.
+1Any chance of getting the dude on PPC?
Because server is now using winbox port. It no longer has separate port to access.testing the winbox dude session
on device i put a mk device and iam getting connect failed: Connection refused(111)
EDIT:
find it, winbox port i cant understand way it is still not possible to set the on witch port Dude need to connect,
1. Is this CHR still using free license level? Usually with CHR / The Dude setups with free license level the 1Mbps limit on interface is causing that Client/Server performance issues.Hi,
I am running Dude on CHR - v 6.37.1 now, and looking for futher updates.
Here are the issues so far:
- Slow response when double clicking on device - changing Agents from default to server speeds up to no delay, but we are not using Agents now, so default should be server ?
- Users in read only mode cannot change own passwords
No, we have P1 full licence.Because server is now using winbox port. It no longer has separate port to access.testing the winbox dude session
on device i put a mk device and iam getting connect failed: Connection refused(111)
EDIT:
find it, winbox port i cant understand way it is still not possible to set the on witch port Dude need to connect,
1. Is this CHR still using free license level? Usually with CHR / The Dude setups with free license level the 1Mbps limit on interface is causing that Client/Server performance issues.Hi,
I am running Dude on CHR - v 6.37.1 now, and looking for futher updates.
Here are the issues so far:
- Slow response when double clicking on device - changing Agents from default to server speeds up to no delay, but we are not using Agents now, so default should be server ?
- Users in read only mode cannot change own passwords
2. Which exact password do you mean?
Yes i know but i dont use default winobox port 8291 for security reason it will be very nice to be possible to tell dude on witch winbox port connectBecause server is now using winbox port. It no longer has separate port to access.testing the winbox dude session
on device i put a mk device and iam getting connect failed: Connection refused(111)
EDIT:
find it, winbox port i cant understand way it is still not possible to set the on witch port Dude need to connect,
Sorry for been annoyingLakis we are having a similar problem, SNMP queries will stop going out from the DUDE server after a short while.
We confirmed that there was no SNMP request leaving the dude server after about 5 minuets of operation, a reboot will get it working again for a short while.
We are running the dude from CHR, are you also running the dude from CHR?
Can u reproduce this problem
dudebug.png
As u can see on the picture (in label appearance) Dude can read two functions but probe says "time out"
After rebooting Mikrotik Device - where Dude is installed all back to normal for some time
Edit. I inspected the problem, I come to this findings
pic3.png
For some reason Dude stop reading values from device, as u can see on picture values are wrong they are "stuck" at the point where dude probably lost connection to the device but for some reason Dude cant reprobe or cant get new values from the Device
But when I try dabble click on device in RouterOS TAB - Interfaces I can see interfaces as it should be (on ether1 bits are rolling every second as traffic passing by)
pic2.png
That mean Dude have access to the device
After Rebooting Dude server Functions- start reading again and Probes go up again.
Another thing on Device label as u can see two from tree probes are down Device have orange colour as normal but there is no info about 2 probes on label [Device.ServicesDown]
Function are made using ros_command for example "ros_command(":put [/system resource get cpu-load]")" and etc. etc.
Great move! So I guess winbox will be dude client.Changes for builds up to v6.38rc19:
*) Added - AES encryption method for snmp v3
*) Added - Dude configuration interface in Winbox (Requires latest Winbox version 3.7)
*) Added - Dude configuration interface in Webfig
** Maps are view-able in web mode.
*) Agents - Now any RouterOS device can be used as The Dude agent. It no longer requires
server package and ROS login. THIS FEATURE BECOMES AVAILABLE STARTING WITH v6.37rc18
*) Agents - Old agent section removed from client.
*) Fixed - Bandwidth test tool. (broken since v6.37)
*) Fixed - Auto-discovery was adding devices with non-usable characters in name field.
*) Fixed - SNMP server didn't work without dns name. (broken since v6.38rcX)
*) Fixed - Some notification types:(flash, popup, log event) didn't work properly. (broken since v6.38rcX)
*) Fixed - Fixed some issues with client where menus didn't display correctly at first access after upgrade. (broken since v6.38rcX)
*) Fixed - It wasn't possible to delete some elements from network map. (broken since v6.38rcX)
*) Fixed - Default variable [Device.RosVersion] didn't return correct value. (broken since v6.38rcX)
*) Fixed - Issues with link not changing color when traffic grows.
*) Fixed - It wasn't possible to open multiple simultaneous panels. (broken since v6.38rcX)
*) Some improvements for DB data write in store.
PS. to use ROS device as agent you do need to have valid user login and "Router OS" check-box marked.
You can specify probe port under device settings => Services => routeros mangement => Probe Portraffav wrote:
Yes i know but i dont use default winobox port 8291 for security reason it will be very nice to be possible to tell dude on witch winbox port connect
Latest RC versions have improvements for label refresh, when device is not reachable,Lakis wrote:
If Dude lose connection to Some device, device go red - normal but values like cpu, mem are stuck showing last value on device appearance
When device is on-line again, dude ping service is up but other SNMP services are down (timeout). I tried Reprobe - not helping
Only when I reboot Dude Server all service are up again.
It's also possible to disable SNMP under device => General => Snmp Profile => no-snmp, for interface traffic you can use Mastering Type - Routeros9939781 wrote:
my ccr1072 have a lots of ip-mac info.but i not need it.i need dude show ccr1072 interface traffic only.becouse show the ip-mac and the other will use more cpu,and i found ccr1072 one core 100% always.i need dude show interface traffic only,
Latest RC versions have improvements for label refresh, when device is not reachable,Lakis wrote:
If Dude lose connection to Some device, device go red - normal but values like cpu, mem are stuck showing last value on device appearance
When device is on-line again, dude ping service is up but other SNMP services are down (timeout). I tried Reprobe - not helping
Only when I reboot Dude Server all service are up again.
Yes I know it should work like that, as it works in v3.6, ok maybe I am wrong in something I'll rebuild new test map and observe, in meantime if somebody has same experience please inform.
Thanks.
edited: Yes SNMP are working (with big delay) but Functions with ros command's are not, after dude failed to reach device
simple Dude can't get from device ros_command(":put [/system resource get cpu-load]") or ros_command(":put [/system healt get voltage] and etc.
but on map in device RouterOS TAB I can see that dude has access. After reboot dude start to read values using ros_command
can you reproduce this problem?
sorry but i didn't find it or understand wellYou can specify probe port under device settings => Services => routeros mangement => Probe Port
It's also possible to disable SNMP under device => General => Snmp Profile => no-snmp, for interface traffic you can use Mastering Type - Routeros[/quote]9939781 wrote:
my ccr1072 have a lots of ip-mac info.but i not need it.i need dude show ccr1072 interface traffic only.becouse show the ip-mac and the other will use more cpu,and i found ccr1072 one core 100% always.i need dude show interface traffic only,
here tooThe Snmpwalk tool appears to not work with 6.38rc19. I've tried on a number of devices and get a timeout for all of them. All of these devices have various SNMP services working correctly. Snmpwalk was working with 6.37.
There are two opttions available to read RouterOS info:Hello, i still trying to figure out how i can make the dude server to read RouterOS info on a RB device that dont use the default Winbox Port
isn't that visually the same as NOT changing winbox port?2) Make firewall NAT rule on your monitored RouterOS device, to redirect the dude server form default Winbox port to your custom Winbox port.
There are two opttions available to read RouterOS info:Hello, i still trying to figure out how i can make the dude server to read RouterOS info on a RB device that dont use the default Winbox Port
1) Use default Winbox port.
2) Make firewall NAT rule on your monitored RouterOS device, to redirect the dude server form default Winbox port to your custom Winbox port.
I understand then that the labels will become ever more to change color to increase traffic? It was a very useful tool when maps are minimized.Changes since v6.38rc19:
*) Removed - Link label will not change colour on link speed change.
{
'Quick Set': 0,
CAPsMAN: 0,
Wireless: 0,
Interfaces: 0,
PPP: 0,
Bridge: 0,
Mesh: 0,
IP: 0,
MPLS: 0,
Routing: 0,
System: 0,
Queues: 0,
Files: 0,
Log: 0,
Radius: 0,
'New Terminal': 0,
Tools: 0,
Dude: {
Devices: 0,
Functions: 0,
Links: 0,
Mibs: 0,
'Network Maps': {
'Network Map Elements': 0,
Discoveries: 0,
'Network Map': {
'&': { remove: 0, set: 0, name: 'Mapa da Rede:', title: 'Mapas de Rede' },
General: {
'Default Zoom': 0,
Status: 0,
tab: 'Imagem',
Name: { ro: true, name: 'Nome:' }
},
Polling: {
Enabled: 0,
'Probe Interval': 0,
'Probe Timeout': 0,
'Probe Down Count': 0,
'Use Notifications': 0,
Notifications: 0
},
Appearance: {
'Label Refresh Interval': 0,
Background: 0,
Device: 0,
Network: 0,
Submap: 0,
Static: 0,
Link: 0
},
Color: 0,
Image: 0,
Scale: 0,
Tile: 0,
Label: 0,
'Link Color': 0,
'Link Full Color': 0,
'Link Label Color': 0,
Thickness: 0
},
name: 'MAPAS'
},
Networks: 0,
Notifications: 0,
Probes: 0,
'RouterOS Info': 0,
'SNMP Profiles': 0,
'Server Config': 0,
Services: 0,
Settings: 0,
'Syslog Rules': 0,
Tools: 0,
Charts: {
Chart: {
Name: { ro: true }
},
'Chart Line': 0,
'Data Source': 0,
name: 'GRAFICOS'
}
},
'Make Supout.rif': 0,
Undo: 0,
Redo: 0,
'Hide Menu': 0,
'Hide Passwords': 0,
'Safe Mode': 0,
Manual: 0,
License: 0,
Graphs: 0
}
SNMP still doesn't work work for me... i can't get some devices values via snmp
i'm using v6.38rc25
i switch to snmpv2 and i had to restart switch and now it works...thank you,Hi, switch to snmpv2, try it.
Here work when i change
i switch to snmpv2 and i had to restart switch and now it works...thank you,Hi, switch to snmpv2, try it.
Here work when i change
FTP, or WinboxIts not your job, but how did you upload pictures?
Pictures in the dude?Its not your job, but how did you upload pictures?
Thanks, yes I can upload via Winbox or FTP but the problem for example how do I place some picture in dude/files/default/images dir so I can use it in dude clientPictures in the dude?Its not your job, but how did you upload pictures?
Used to upload vía thedude client, but now it's only possible via winbox or ftp... or SMB too
ROS login seems to be working ok with lab devices w/ rc25 server.Hi All,
I upgrade dude to V6.38rc25 and now when i click on devices and select router os, almost all device gives this error " std failure: not allowed (9), next attempt at Nov/10 10:28:56 " and dude cant log in to devices so i cant see the graphs also. what can be the problem ?
x86 /dude/files/ dir it works thanksTry putting the image files in the dude/files/images dir. Mibs go in the dude/files/mibs dir. I found it much easier to use ftp than Winbox.
Hi,ROS login seems to be working ok with lab devices w/ rc25 server.Hi All,
I upgrade dude to V6.38rc25 and now when i click on devices and select router os, almost all device gives this error " std failure: not allowed (9), next attempt at Nov/10 10:28:56 " and dude cant log in to devices so i cant see the graphs also. what can be the problem ?
1. Is login credentials correct in device settings?
2. On monitored device in group policy winbox and dude policies should be makred otherwise server wont be able to access the device
Hi. Email notifications are working fine here. I use rc29. Variables used to be broken en previous rc versions. Since rc20 approx they are working fine.Hello, I've updated The Dude to 6.38rc29 version and the e-mail notification is not working. Any changes with the variables at all?
{ Body: Service [Probe.Name] on [Device.Name] is now [Service.Status] ([Service.ProblemDescription]) }
Starting from 6.38.X link labels will no more change colour. Link itself changes colour depending on the link rate, and actual link traffic.Hello, I upgraded from 6.37.1 to 6.38rc29 and moved from CCR router to vSphere x86 CHR VM because of continuous restarts of Dude caused by CPU and memory exhaustion.
The CPU and memory utilization now seems ok, but I found few annoying bugs:
- color gradation of stressed links and link labels not working
- status flags of network maps in left tree contents panel are missing
- snmp walk tool not working
- drag&drop file transfers between PC and Dude not working in either direction
While upgrading RouterOS to v6.38rc29 I also noticed that SMB server implementation on RouterOS is broken as my automated DudeDB backups started to fail.
What I would also really appreciate in new Dude version:
- ability to filter snmp oid arrays by regular expressions in Dude functions (or at least by substring match)
- support of live db backup (or ability to export Dude configuration with no history data), whithout needing to stop the Dude server
Thank you for explanation.Starting from 6.38.X link labels will no more change colour. Link itself changes colour depending on the link rate, and actual link traffic.
File transfers using dude have been disabled, instead you can use Winbox, Webfig or ftp.
Snmpwalk will be fixed in next rc version.
Can you please specify, what you want to achieve using snmp oid regex filtering ?
Quick tests didn't show any problems with SMB server on the latest RouterOS. Can you please give us more details about this issue ?
Also didn't found problems using email notifications on 6.38rc29
I got the same problem after upgrading to rc31 from rc25.Please, fix dude, i cant connect to dude server since 6.37.
When i connect - it says me "getting stuff" , client rx becomes about 10MBps and then goes to 300-600 kbps and stays on login page. I update to RC 6.38rc31 - same here. Seems you fix autoupdate but still wont show me DUDE. Stuck on login.
What should i do?
I get some workaround and here: i delete dude, delete files. Install clean dude and can connect. So reason - dude db. How we can debug it? May be some files are corrupted or language or encoding? I have dude since 3 version with Russian language.I got the same problem after upgrading to rc31 from rc25.Please, fix dude, i cant connect to dude server since 6.37.
When i connect - it says me "getting stuff" , client rx becomes about 10MBps and then goes to 300-600 kbps and stays on login page. I update to RC 6.38rc31 - same here. Seems you fix autoupdate but still wont show me DUDE. Stuck on login.
What should i do?
i did a snapshot on the VM before but even after reverting back to rc25 i get the same problem. any ide to the problem.
This did not help i also delited all registry entrys left behind but no luck.I get some workaround and here: i delete dude, delete files. Install clean dude and can connect. So reason - dude db. How we can debug it? May be some files are corrupted or language or encoding? I have dude since 3 version with Russian language.I got the same problem after upgrading to rc31 from rc25.Please, fix dude, i cant connect to dude server since 6.37.
When i connect - it says me "getting stuff" , client rx becomes about 10MBps and then goes to 300-600 kbps and stays on login page. I update to RC 6.38rc31 - same here. Seems you fix autoupdate but still wont show me DUDE. Stuck on login.
What should i do?
i did a snapshot on the VM before but even after reverting back to rc25 i get the same problem. any ide to the problem.
Very good, thanks, and can you please clarify, is this problem only in device pop-up window (history graphs), or you also see the same in device > history charts ? Seems like there is issue only if some service is down on monitored device.Thank you for correcting the snmpwalk.
I found other bug in rc31: missing graph captions in device history panel.
This happens to me only in device history charts panel, not in pop-up window. And only sometimes, so it might be related to some device state.Very good, thanks, and can you please clarify, is this problem only in device pop-up window (history graphs), or you also see the same in device > history charts ? Seems like there is issue only if some service is down on monitored device.
Thankyou, sent info.denser and leoktv - Please generate a supout file from the dude server, and send it with description to support@mikrotik.com. We will try to reproduce and fix it.
Sent as requested
denser and leoktv - Please generate a supout file from the dude server, and send it with description to support@mikrotik.com. We will try to reproduce and fix it.
/dude export-db
/dude import-db
which hardware do you use?Another problems with latest RC versions:
I'm using Dude on CHR v6.38rc31 on vSphere server 5.5 right now, because on CCR the stable version 6.37.1 was exhausting memory and CPU.which hardware do you use?Another problems with latest RC versions:
This is where RoMON comes in handy. Configure RoMON on the gateway MikroTik device and set a password. Configure RoMON on the internal MikroTik devices and use the same password. Then in WinBox, select the gateway MikroTik device and choose "Connect to RoMON" and WinBox will connect to the gateway MikroTik device, change the bottom tab to "RoMON Neighbors" and you will see all the devices listed by MAC Address, with their Identities shown.DUDE FEATURE REQUEST:
Ability to specify custom port number for Winbox connections (e.g. to connect to multiple MTiks behind single public IP).
I was thinking about this, but...Currently I solve this issue by putting a static-item inbetween a link.
I have been using it for years also. But it is very poor solution.Currently I solve this issue by putting a static-item inbetween a link.
This allows for
- links with angles
- setting both ends of a link with interface (and stats)
- drawing more than one link between two devices.
So, so yes!!!Guys, if there any ability to do such thing - connect links not in one point but in edge of object? When i want to draw 50 ports it become such a mess.
May be it should be able to make curves or polylines?
+1+1 (for multiple links betwee devices, for example)
also, it would be nice to have a possibility to set Interface for both ends of the link (to see that the link is from port 5 of switch1 to port 7 of switch 2)
6.38rc14 (Release candidate)
my requests
1. all alerts that have occurred in non-active time for such notifications for example between 00:00-08:00, should be added to the queue and be send at the beginning of an active time. If by that time the service started to function, the notification shall be removed from the queue.
alert_email.png
2. If the main map contains several submaps, and added there devices are set depending on (parents), and when the device is not working in the tree above, I should get one notification about device failure which is highest on the tree even if it is on a different submap. Now i have many alerts. Maybe I have problem configuration of the DUDE?
not.pngnot_10.png
Some worksaround. Arial.ttf vanishes when old dude client connects and update itself.... Strange behavior.I put font arial.ttf - its gone. Afetr i connect i see rectangles instead of russian letters. I put it again - wow, russian letters there again. Close Dude for a while. Run again - rectangles again, look into files - arial.ttf gone(whata...) Put it again - works for now.
I confirm this, there is some SSL load problem on x86 OS 6.38rc40, reboot fixed for nowChanges since 6.38rc37
chimaster
Also it would be great if you could provide us with remote access to device with SSL load problem.
support@mikrotik.com
If you can repeat problem, please write to support@mikrotik.com.
I cannot repeat it... It is permanent.. Please test on MMIPS RB750gr3. On RC44 the same problem... The dude directory is read only or something like that... Other directories - OK... Wrote to support..Problem not reproduced. Works with USB/SD card as data storage path, tested with Winbox. FTP.
Make sure you are placing files in dude/file directory.
If you can repeat problem, please write to support@mikrotik.com.
All i want for Christmas is stable dude 6.38i use dude v6.38rc43 on new hex and there is maybe bug with RAM eating.
Hex stay up for 2 and half day and then reboot, for this time hour by hour eating the RAM until device reboot.
On dude i have about 1000 devices, monitoring by ping, some SNMP sonds etc.
It happens on earlier versions too.
Agreed. It would be great if they added HTTP Notification as a notification type with custom parameters.Will the Telegram notification support?
just an ability to make GET/POST HTTP requests. I was surprised when did not found that type of notification in Dude v3Please give us more details what would be the best HTTP Notification method
Calling https url with custom uri part with replaceable variables would be enough for me. And it should be usable in functions.Version 6.38rc51 has been released.
deathmagicmedia -
Please give us more details what would be the best HTTP Notification method
Currently, we use this probe for HTTP and it works great:Calling https url with custom uri part with replaceable variables would be enough for me. And it should be usable in functions.Version 6.38rc51 has been released.
deathmagicmedia -
Please give us more details what would be the best HTTP Notification method
e.g. https://example.com/?api_key=my_api_key&ip=[Device.Address]&service=[Probe.Name]&state=[Service.Status]&another_custom_parameter=hello
PS: enabling/disabling ssl certificate verification would be also useful. Something like CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST in Curl.
But I need to send a notification through http request (service is up, service is down). There is no such type of notification as 'TCP Probe'. And it doesn't allow TLS/SSL connection.Currently, we use this probe for HTTP and it works great:Calling https url with custom uri part with replaceable variables would be enough for me. And it should be usable in functions.Version 6.38rc51 has been released.
deathmagicmedia -
Please give us more details what would be the best HTTP Notification method
e.g. https://example.com/?api_key=my_api_key&ip=[Device.Address]&service=[Probe.Name]&state=[Service.Status]&another_custom_parameter=hello
PS: enabling/disabling ssl certificate verification would be also useful. Something like CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST in Curl.
Probe Type: TCP
Port: 80
Send: Authorization: Basic xxxxxxxxxxxxxt\r\n\r\nGET /state.xml HTTP/1.1\r\n\r\n
Receive: <input1state>0</input1state>
You can replace send with whatever HTTP request you want to send, and figure what you should receive.
You can use packet sniffer to help you find what is needed.
Using dude 6.38 rc 48 and it works good.
Don't know if it can suit for https stuff...
Regards,
Michael
Thanx for expanations.. You should mention that custom files are available for upload to files directory only.. I tried images directory.. It is readonly..Version 6.38rc51 has been released.
maxkrok - we suggest to use only ext3 file system, it's more stable for dude, and more tested. Here only solution seems remote access > support@mikrotik.com
Should be fine to autoupdate from all recent versions, just make sure that you run the Dude as administrator. Does anybody else have seen similar problems recently ?Is the Dude client autoupdate functional? I've tried it with several 6.38rc and it downloads something and then just shutdowns.
%HOMEPATH%\Desktop\winbox.exe doesn't work (Windows 10) in Tools, works in File Explorer. Ordinary users can place files only inside of their windows profile and each profile has its own path based on username.Note that you can still use Winbox in the Dude, by simply adding it as a custom tool:
Didn't work for rc49->rc51 and rc51->rc52 (as Administrator). I had to update it manually. Also would it be possible to allow update without Administrator rights? Many companies doesn't allow to have Administrator rights. And updating it only by company's network admin makes updating to a higher version very problematic.Should be fine to autoupdate from all recent versions, just make sure that you run the Dude as administrator. Does anybody else have seen similar problems recently ?
Another option would be to keep Dude client unchanged if only server is updated.%HOMEPATH%\Desktop\winbox.exe doesn't work (Windows 10) in Tools, works in File Explorer. Ordinary users can place files only inside of their windows profile and each profile has its own path based on username.Note that you can still use Winbox in the Dude, by simply adding it as a custom tool:
Didn't work for rc49->rc51 and rc51->rc52 (as Administrator). I had to update it manually. Also would it be possible to allow update without Administrator rights? Many companies doesn't allow to have Administrator rights. And updating it only by company's network admin makes updating to a higher version very problematic.Should be fine to autoupdate from all recent versions, just make sure that you run the Dude as administrator. Does anybody else have seen similar problems recently ?
its important to find solution for this.%HOMEPATH%\Desktop\winbox.exe doesn't work (Windows 10) in Tools, works in File Explorer. Ordinary users can place files only inside of their windows profile and each profile has its own path based on username.Note that you can still use Winbox in the Dude, by simply adding it as a custom tool:
OMG.. nice solutionVersion 6.38rc52 has been released.
Changes since last version
*) Removed - Since default Winbox used in the Dude wasn't fully compatible with all RouterOS devices, we removed it completely.
*) Fixed - Increased default ping packet size to 54bytes - there was some devices who wasn't able to respond with 32 byte ICMP packets, this caused ping corruption.
Note that you can still use Winbox in the Dude, by simply adding it as a custom tool:
It must be in your Windows PC, not in the router.Is there any chance to locate winbox.exe on router SDcard
1. Please update your Dude server to the latest - 6.38rc versionDevs: thanks for all the work so far, appreciate it! Sorry I didn't reply with update to email notification issue not working. Original email problem (post #104) was resolved. Was originally on CHR. Loaded new x86 VM and email notifications started working so seemed to be something with that specific load of RouterOS.
I can confirm our map background images randomly disappear from disk, too. We are on 6.38rc40 and have had to replace a background image twice and it ultimately disappears from disk. It is missing again now.
In my case works only with this command:%HOMEPATH%\Desktop\winbox.exe [Device.FirstAddress] [Device.UserName] "[Device.Password]"
I confirm this behavior as well. Not just the background image, but also some locally-added device images, such as CCR, RB2011, LHG -- only a few of them, not all of them. They disappear from dude/files/images and have to be re-uploaded. Problem seems to be triggered by release updates, and does not reoccur until next update. Reported this back on October 7.1. Please update your Dude server to the latest - 6.38rc versionI can confirm our map background images randomly disappear from disk, too. We are on 6.38rc40 and have had to replace a background image twice and it ultimately disappears from disk. It is missing again now.
2. If you can reproduce the problem, send mail with description to support@mikrotik.com
macsrwe - thanks for clarifying.I confirm this behavior as well. Not just the background image, but also some locally-added device images, such as CCR, RB2011, LHG -- only a few of them, not all of them. They disappear from dude/files/images and have to be re-uploaded. Problem seems to be triggered by release updates, and does not reoccur until next update. Reported this back on October 7.1. Please update your Dude server to the latest - 6.38rc versionI can confirm our map background images randomly disappear from disk, too. We are on 6.38rc40 and have had to replace a background image twice and it ultimately disappears from disk. It is missing again now.
2. If you can reproduce the problem, send mail with description to support@mikrotik.com
I can also confirm the maddening "auth. failed" problem running bandwidth test in Dude. Reported it November 12, hoped it would be fixed by now. It forces me to turn off authentication on every device before I can run bandwidth test on it.
Thanks, I didn't realize that.Also please make sure, that all custom files are stored in dude/files directory only, as it is stated in the manual:
Your custom uploaded mibs/images/etc need to be stored in: "(data-path)/files/" directory.
http://wiki.mikrotik.com/wiki/Manual:Th ... 37_release
Hello everyone,
I want to report a problem with the upload file function in v6.38RC52 on mmips RB750GR3 - in this version and with this device, traditional "drag and drop" does not work, but there is a new button "upload"
because the device has only 15 megabytes of embedded memory, it should be possible to choose the destination disk (SD card or Pendrive)...