After about 18-24 hours of operating, my RB532 seems to go away - at least part of it. The main router still is functioning and traffic flows, but...

DHCP stops working
Ros stops responding to telnet, winbox, ssh, web, etc.

I did notice this afternoon before I upgraded that the free memory was about 1/2 of what is normal after a boot (6MB vs 12MB free after boot).

I have just upgraded to rc5 and will post the results.

The router appears to have dumped a support file, so I am posting here as well.

Brian

OK, almost 24hrs and memory is holding. rc5 may have fixed the problem.
Brian

Still having the same problem in RC5.

The router becomes unavailable and stops service DHCP, the rest continues to run. Requires a power cycle to make it work again.

Brian

For now going to use a little script to reboot the router for me. I arbitrarily chose 7mb because the router seems to start having problems after that.

maybe you know what kind of traffic does that?
could you redownload that support output file from router - we can't open it? Send it to support@mikrotik.com

I did mail a couple support files to support yesteday.

This router and another lost their interfaces couldn't enumerate lists, etc. and other things. I was experimenting with EoIP and IPIP tunnels. Couldn't get EoIP to work at all, but IPIP did - then the routers stopped responding to winbox. I was able to get in through the terminal interface, rebooting didn't help so I did a system reset on one and restored from backup, the other was able to just restore from backup.

Brian

Turned off SNMP and Graphing in the router and it may have solved the problem. This router has been crashing dailying sincing installing RC4 and RC5, now I have just over a day of runtime.

Do you use dude or another snmp related program???

Also I suggest you to check incoming packets against outgoing packets - usually they must be the same, but if they differs several times you might be under DOS attack for example on SNMP port (161 TCP)

Yes, I use The Dude. This is only one router in a small (8 routers) mikrotik network and the only one I have this problem with. I suspended use until I can get this router under control.

This router has The Dude server on the ether1 network, so it could have been getting a bunch of extra traffic from The Dude.

I will keep an eye on the traffic patterns (in/out) on the router.

Currently at 1 day and 18 hours of uptime - this is a record!!!!

Thanks,
Brian