1. (Winbox) In CapsMan REGISTRATION TABLE add column with client IP and Active Host Name like in dhcp server lease section!!

2. (Winbox) In DHCP Lease section when pressed right mouse button on client add Torch and Ping option!!

Dear all, I've a problem with dude tools security. When create a tool, for example for winbox and has a problem with the file, winbox.exe, for any reason, in the alert message you can see in plain text the password of the device, that is a big security problem :-S. Any suggestion for solve it? The error windows is: "Execute failed (command: C:\winbox.exe 192.168.0.1. admin "thepasswordinplaintext". The system...." Thanks.

Dear all, I've a problem with dude tools security. When create a tool, for example for winbox and has a problem with the file, winbox.exe, for any reason, in the alert message you can see in plain text the password of the device, that is a big security problem :-S. Any suggestion for solve it? The error windows is: "Execute failed (command: C:\winbox.exe 192.168.0.1. admin "thepasswordinplaintext". The system...." Thanks.

it's not a big problem. just copy your device to Clipboard and paste to Notepad - here's the password even without calling WinBox

Sorry to ask, but have need to upgrade a bunch of core CCR1072 units and CRS units.

When do you think v6.39 final will be available?

It's been since Dec 30 on 6.38 when I upgraded everything and then right after they had a lot of STP/RSTP stuff happen...

it's not a big problem. just copy your device to Clipboard and paste to Notepad - here's the password even without calling WinBox

Unbelievable.

After updrade to 6.39rc68 (hex r3) I lost all the files on the usb drive, and in the FILE a nwe folder appeared disk2, I also have disk1 (both empty).
Guess where i kept the backup ...
On Friday I added 100+ test devices to check the stability on hex r3 ...
Thx mikrotik ..

Hello everyone - that's my first post although adventure with mikrotik started many years ago

I have a problem with 64-bit counters. In changelog v6.36: Fixed - diff64 function broken.
I installed dude on mmips (RB750Gr3) - but for this platform dude is available from 6.37.5 version - maybe fix is not implemented for this platform?
I need simple function: diff64(oid_raw("1.3.6.1.2.1.31.1.1.1.10.436400128")) - oid_raw return correct value but diff64 from oid_raw value return "0". On 4.0beta3 its ok
Additionally there is some problem with reading 64 bit count. If interface speed is more than 1Gb build-in function e.g. Interface.InBitRate looks like reading 32-bit count because value which show is not correct - much lower. I set on link snmp-type and speed (10g ethernet) but there is no difference. On label visible max speed is 4.29Gbps. I tried a few different version - the same problem.

Hello everyone - that's my first post although adventure with mikrotik started many years ago

I have a problem with 64-bit counters. In changelog v6.36: Fixed - diff64 function broken.
I installed dude on mmips (RB750Gr3) - but for this platform dude is available from 6.37.5 version - maybe fix is not implemented for this platform?
I need simple function: diff64(oid_raw("1.3.6.1.2.1.31.1.1.1.10.436400128")) - oid_raw return correct value but diff64 from oid_raw value return "0". On 4.0beta3 its ok
Additionally there is some problem with reading 64 bit count. If interface speed is more than 1Gb build-in function e.g. Interface.InBitRate looks like reading 32-bit count because value which show is not correct - much lower. I set on link snmp-type and speed (10g ethernet) but there is no difference. On label visible max speed is 4.29Gbps. I tried a few different version - the same problem.

It's actually broken on 4.0beta3 as well. While it will take a 64 bit counter as an input, it is a 32 bit signed output. I haven't tried it since it was pronounced fixed.

it's not a big problem. just copy your device to Clipboard and paste to Notepad - here's the password even without calling WinBox

Unbelievable.

There are two aspects to this: 1. It's too easy to for any user without advanced credentials to get any password through this or a similar (CSV) hack; and 2. There's no supported provision for a user having advanced credentials to recover a password. My point here is that I pray that MikroTik does not close loophole one without providing feature two first.


Sent from my iPhone using Tapatalk

Changes in v6.39rc17:
macsrwe - If you can repeat the problem in rc17, please write to support@mikrotik.com

Reset all the "wrong challenge" units yesterday by manually Reconnecting. Upgraded to rc17 last night. Tonight, I see I have two CPEs again stuck in the "wrong challenge (not requested)(4)" state. I'll send in an error report.

It also would be nice to know what that error message is supposed to mean.

Not only has this problem not been addressed, but yesterday the Windows 10 machine that runs our Dude client did an automatic OS update and an automatic reboot, and failed to restart the client. When I got back to it, there was a (truncated) error message saying something to the effect of the server had refused connection frim the client(!) because of the wrong challenge. I stopped and restarted the client, and it came up, but whatever this wrong challenge thing is, it really needs to get fixed.

Good day,can anyone have experienced the problem: use 6.39 Dude,the map added about 1000 of switches that are polled via SNMP when you open the card device is a large delay of about 8-10 seconds,while the server is not overloaded and CPU usage does not exceed 20%,this problem is present? on Dude 4 this problem was not observed

Hello!

Please add a possibility to add multiple "To" in Email notification. Something like: user@domain.com, user2@domain.com

And it seems that Dude and Winbox shows different Server address:
Dude
Server Dns Name: smtp.gmail.com

Winbox
Server: 0.0.0.0

Thank you!

Upgraded to 6.39.1 and lost the history graphs and nothing in the outage. Running it on CHR. Anyone else facing this issue.

Upgraded to 6.39.1 and lost the history graphs and nothing in the outage. Running it on CHR. Anyone else facing this issue.

rebooted the CHR and now everything is back.

Hi, i have a problem with the dude 6.39rc80 and TP-Link TL-SG105E. When i create a new device for TL-SG105E ping probe return ok(corrupted), and i already checked with normal ping command it returns normal when pinged.

Any plans to enable drag & drop of devices into a subnet map?

no more updates?

I was running both The Dude 6.39 and The Dude 6.40rc21 and I am getting:

std failure: not allowed (9)

This affects only RoS Devices, for The Dude trying to log in using winbox. It seems sometimes it works, other times it does not !

any ideas as to why this happening ?

I'd like to see link downs being able to be monitored and logged on RoS devices. Right now there is none

No changes in 6.40?

joanllopart - I'm not sure about Cacti, but in RouterOS - graph is made from 5 min average data rate. What is polling interval in your Dude graph ?

We imported from 4.0beta3 where graphs has been working fine. I noticed issues with graphs maybe at 6.38. Now graphs ara wrong, specially when they are over 1Gbps, and doesn't get SNMP info from devices like Ubiquiti EdgeSwitch (different models). If you look at my previous post graphs, you'll see how Dude's graphs fail when we have more traffic.

Polling interval 1 minute
Polling timeout 10 seconds

We relay on dude to graph most of our network links, it's quite important they work as expected.

I have reported a similar issue under my previous account from my last job

http://forum.mikrotik.com/viewtopic.php ... 14#p519591

The issue got better once we backed our dude database with a flash array instead of spinning disks and seems to be better in recent builds, it is not entirely gone, a cursory glance shows some graph drops that don't correspond to any other drops upstream or downstream from the link as I would expect if it was real packet loss. I'm getting these issues from a variety of devices, none of the ubnt. I've even had it happen on MTik devices. I will gladly give any and all info required to help solve this issue but it is something that needs to be solved.

Graph isues are with any kind of device link, not just Ubnt. We are somehow used to those spikes. The problem we have with last versions is that it fails to graph properly when traffic is over 1Gbps. An example with two graphs on same interface, secod graph is the one that shows real traffic:

Graphed by Dude, SNMP polling on CCR1072:



Graphed by CCR1072:

Are you sure you using 64bit counters. that looks very much like wrapping numbers!?

when will the new versions?
There is no improvement for a long time

6.39 === the latest version
https://wiki.mikrotik.com/wiki/Manual:T ... _changelog