High bandwidth usage with dude 3.0beta 4

Hi,

I’m running dude 3.0beta 4 since a week an i have noticed that the new dude use a lot of bandwidth (0.75mbps downlink and uplink all the time)

What can explain this high bandwidth usage?

Is there something that i can do to get back to a more normal bandwidth usage?

I think that with dude 2.2, with the same maps an items, the bandwidth usage was around 50kbps in and out…

Regards

We also tried beta 3.04 and found the same thing. Network traffic goes up by a factor of 5-10 times. Downgraded back to v2.2 immediately.

Hi,

We also tried Dude Beta 3.04.
CPU usage on monitored switches or routers has increased by 6 % immediately after starting monitoring. We monitor only ping service and operational status from one or two interfaces per device. After downgrading to Dude 2.2 the load on devices is normal again.

The new Beta 3.05 has the same bug.
Any idea what causes this permanent high load?

Regards
Enrico

Note that after server startup dude server uses more bandwidth than during
normal operation (after some minutes). In version 3 additional bandwidth is
used for populating mac-mapping table. You can try to increase the refresh
interval (default 5 minutes) in ‘Server Configuration’ → Misc tab → ‘Mac
Mapping Refresh Interval’. Then your traffic should be back to normal.

Please report back if that helps or not. Ideally provide us with capture file
and/or your configuration export to help us look for potential problems.

Thank you

I have change the “Mac Mapping Refresh Interval” to 1 hour and it didn’t change anything.

Dude still use between .5Mbps and .75Mbps simultaneous uplink and downlink all the time.

I have not seen any cpu load increase in my network with dude 3 but i’m monitoring equipements with a lot of horsepower (7606,4507R,7206VXR…)

Should i use support@mikrotik.com to provide my configuration file?
Do you want an ethereal capture too?

Let me know…

Regards

Yes, please send configuration and ethereal capture with dudes traffic to
support@mikrotik.com. Thank you.

Thank you for report. We have found and fixed a bug. Next versions bandwidth
usage will be back to normal.