ROS 3.23 and syslog

RouterOS General
1

Greets All,

I seem to be having a problem with 3.23 in that it doesn’t want to export syslog data to an external server running SolarWinds NPM. Everything else that does syslog is working fine with the SolarWinds machine, except for 3.23. Is this something that got broken in this release?

On the other hand, since upgrading to 3.23 I no longer have the lockups that occasionally happened with 3.22 and prior wherein the DNS cache would get too many 0.0.0.0’s and lock up the machine (running on a 4 CPU server). I get the occasional error from hell in the web cache, but it no longer crashes the server.

Any advice on the syslog scenario would be appreciated. The syslog functions of 3.23 are configured correctly. It was working with 3.22 and prior.

Thanks!

2

can you run packet sniffer on udp/514 from the router and see if its generating them?

3

Thanks for the reply and the advice. I ran packet sniffer and did about 20 bad logins, sniffing port 514 between the Mikrotik and server addresses and nothing was generated, even though critical errors are to go to the syslog.

Everything is setup the same as previous: remote IP is the server, port 514 and origin is the Mikrotik. Warnings, critical, and errors are to go to syslog and the server.

Nothing is being sent according to the sniffer. I think there may be a problem. Can anyone else verify this issue with 3.23? Thanks.

4

Ive the same problem guys…