Hi Guys!!

I have a small problem.

I'm using rb333 (ROS 3.14) with dude server running and monitoring my LAN. When I'm connecting locally (from within my LAN) using winbox or the dude client, everything is ok.

The problem is that when I'm connecting from outside of my LAN (via debian server using NAT) I get very low transfer speed to the dude server (around 25 - 35 kbps max), so as you can imagine, it takes a LONG time (15-20 min) for the dude client to download everyting from dude server.

Of course there is no problem with transfer speed to other devices behind NAT. So I guess the problem is isolated to my rb333.

Anyone seen anything similar?? I'm not sure how to solve this. I tried to set up a vpn connection to rb333, but didn't help much, transfer speed is still very low.

Hello,

I'm facing a problem looking exactly like this. My Dude server resides on PC (Windows XP) and local connections work well, outside connections through forwarded TCP port work unusably slow. The port-forwarding is done by Mikrotik ROS.

Any sugestion? Thx for help!

Direct access to the Dude server on that 333 will be slow. However, I have had good luck with just letting a 333 operate as an agent of a master Dude server. My experience with a 333 class Dude implemention is that it eats the mass storage resource down to about 15% and RAM utilization will peak quite high. That seems to be why it is slow regarding access. Instances of the Dude on Routerboards can be optimized with careful tuning of the 'default' polling intervals. The 'Master Dude'-to-'Agent Dude' connectivity seems to be quite fast, as I can attest to how quickly an alert from a remote network is propagated.

Try these concepts first and see if it accomplishes what you require....