Hi dear,
i will try to manage my mikrotik device via “The Dude v6.39.3” . during my network discover i have edited the probe “routeros management” changin it with the my default winbox port “20891” and not “8291”. All the device are collected, but i can’t accesso on it via Dude…
How i can change the default RouterOS port on Dude Device?
Hello, m4t7e0!
All the device are collected, but i can’t accesso on it via Dude…
What device and how do you trying to access it?
May you please explain more detailed what do you trying to do?
How i can change the default RouterOS port on Dude Device?
Dude device is Dude server?
Thank you!
Ok, so i will explain the problem:
i have 500 mikrotik device (varius type without dude server installed on it) connected via VPN to one Mirkotik CCR where is installed the dude server.
Actually the 500 mikoritk are manageble via ssh, telnet, api, winbox, but with different ports.
When i try to add it on the dude i can’t access via dude on the RouterOS Tab, because it try to connect to default port (i have tryed to se the default port on one device, and it works).. but i can’t change the default port an all the devices.
i hope i had a full explained of the problem.
m4t7e0, thank you for explanation!
Why you can’t change Winbox port for all of the devices, which issue is in your case?
In my test environment I had recently an issue with ROS devices with non-default Winbox port and reported it to the support:
[Ticket#2018010322001999] RE: Dude v6 - ROS with custom Winbox port - Dude hangs issue
https://www.youtube.com/watch?v=fWp1eH9CU2s
https://www.youtube.com/watch?v=_coYAsJlIPU
[Ticket#2018010322002603] RE: Dude v6 - ROS device with custom Winbox port - Connection issue
https://www.youtube.com/watch?v=WrNOou0js7s
Support replied that on RB hardware it working fine and service may be added. I can’t verify it because have only CHRs on Virtual machines.
If you experience similar issue - please report it to the support in order to help them to solve it.
Re-verified now and see that service status is up (green) but: RouterOS Status: connect failed: Connection refused(111) (6), next attempt at 11:23:57
Thank you!
Yes, i have the same problem explained on https://www.youtube.com/watch?v=_coYAsJlIPU .
For company needing i can’t change it… i can only making a fake firewall rules for changing the port request… but is not compliant…
m4t7e0, on which platform your Dude server is running and who are clients?
If you can, please provide some models of the Routerboards and their installed ROS versions.
As you described in the first post you currently on the ‘Bug fix only’ channel and use latest channel version. Anyway I see the issue in the Dude v6.42rc9.
Thank you!
The Dude Server si running on CCR1036-12G-4S 6.39.3 the device that i want to reach via dude monitorig is RB951 - 952 - Groove - CRS etc etc .. all these device have the same “port configuration”.
Acctually i can’t use the current version i prefer the bugfix version.
m4t7e0, thank you!
This topic was reported to the support in one of the the initial request. Hope they will be able to fix the issue. Don’t know when as Dude development is frozen/slowed.
Thank you!
Thanks you too… I actually want to forward the port request via Nat rules .. I hope this can solve temporany the issue.
any update here?
My winbox port is now 28291, I cant connecte the dude to routerOS service.
Actually from me, no news about it! 
Hi, I have the same problem.
The Dude server can not add the routeros port.
This is a very big problem and I do not understand why the Mikrotik company will not add such a simple function as the port entered after the IP address (192.168.1.1:23456)
Hi guys
What I did was to add a new tool under the tools menu of my dude server. let’s say “Winbox alt port”. with the following Command:
%HOMEPATH%\Desktop\winbox.exe [Device.FirstAddress]:8891 [Device.UserName] [Device.Password]
this is for port 8891
I have the same problem with 6.42.6. I set a new “routeros management 2” service with the port:33333 but it didn´t work.
I must to change the winbox port of dude server to 8291 again
I have the same problem with 6.43.4. Unfortunately, I can’t even use port redirection (NAT rule) on RBs, because the main ISP here is blocking default WinBox port (8291)
Same here!
we have 2019 and still problem exist:(
Actually seems to be a problem indeed, but I’ve worked around with a custom NAT rule where I dst-nat requests from my specific dude server to my specific RouterOS router, so if it wants standard port, the target device dst-nats these requests to my non-standard port, and it finally resolved as “RouterOS Status: ok” !
/ip firewall nat add chain=dstnat action=dst-nat to-addresses=<IP-of-my-remote-Mikrotik> to-ports=<non-standard-Winbox-port-of-my-remote-Mikrotik> protocol=tcp src-address=<IP-of-my-dude-server-I-scan-from> dst-address=<IP-of-my-remote-Mikrotik> dst-port=8291
This is a nice solution, but it cannot work when port 8291 is blocked by a provider. And that’s exactly my problem…
Perfect!!! #Genius !!!
[quote=katsuy post_id=664792 time=1527532286 user_id=122089]
I had the same problem here, since I don’t use default port on our mikrotik devices.
What I did to solve my problem was a simple NAT rule on the devices I wanted to use the RouterOS tab from The Dude, as follows:
</s># Enable Dude - RouterOS Access
/ip firewall nat
add action=redirect chain=dstnat comment="Accepts connections via RouterOS - Dude" \
dst-port=8291 protocol=tcp src-address=THE_DUDE_SERVER_IP to-ports=WHATEVER_PORT_YOU_DEFINED
/ip firewall nat move [find comment="Accepts connections via RouterOS - Dude"] 0<e>
It simply monitors the input connections from The Dude server, and if any match the default port for Winbox (which is the one used by The Dude to connect to the ROS) it redirects it to the right port.
I have about 200 devices working just fine like this.
http://prntscr.com/jnq0n9
[/quote]