Hello,
I have multiple Routers, some of with have port forwaridng to internal RB433 and I was wondering how to specify on which port Dude connects to RouterOS via Winbox.
Others have non standard WInbox port (for securty reasons).
Is there something like SNMP Agents which can be added (ie. UDP 162, 163…) also for Winbox port?
Sincerly
Huntah
in the IP services menu:
Does that mean that Dude check IP Services and according to that uses this port?.
But in my scenario I have an network diagram consisting of main Router connected to internet and several internal one. To this internal ones I have port forwarding for SNMP (UDP 162 → internal IP >UDP 161 and Winbox TCP 8000 → internal IP → TCP 8291).
The Dude works with SNMP with no problem (just added agent to read from 162) but if I connect to Winbox (from The DUde) it always connect to 8291 (external Router). I would like to specify in The DUde on which port (ie 8000) the dude connects to internal RB433s.
If I use classic Winbox it works as i t should (exmaple: ExternalIP:8000).
Regards Huntah
Sorry but I misunderstood your initial question. Currently Dude can only use the default port, but it’s in our feature list, so we will make it sometime.
Thany Normis for Quick Reply…
I am looking forward to this feature.
Sincerly
Huntah
is there any way to define an alternative port for this yet?
I have a few customers with multiple mikrotiks natt’d behind a single IP across various port ranges, being able to set this in the dude software would make managing them so much easier !
not yet as far as I know.. But this would realy be a great feature since many one us have similar setups and managing them is not as easy (manual Winbox plus port).
Luckily we can add multiple SNMP agents (different ports) so we can se if it is online, traffic and all other SNMP settings
Why not setup a VPN between the Dude and the distant devices, then you have direct local access and no firewalls in the way? I had the same problem. But gave up waiting for this ‘feature’. 
You can also just make a nat rule to forward the traffic to your winbox port.
chain=dst-nat, src-address=, dst-address=, Proto=tcp, dst-port=8291 → action=dst-nat, to-ports=
This is done already..
It is from the dude monitoring software that you cannot set the alterantive port to connect to the device behind NAT (multiple MK behind same NAT)
Make tunnels between the networks and then you can access everything directly without natting or port forwarding.