3.5 Syslog stop working?

Just updated to 3.5 Dude on my 4.4 RB1000… Im not getting the syslog activity from the 50ish vpn endpoints like I was right up until I upgraded it… Anyone else?

OK, i just downgraded to 3.4 and it still wont log. What could have happened? The RB1000 is set to log to itself at 127.0.0.1 w/ source of 127.0.0.1. The remote routers are set to log to the point-to-point address of their openvpn link. This worked before and it doesnt now. I dont understand…

Any pointers?

I completely uninstalled dude off my router, formatted the CF card, re-installed it.

Syslog still isnt working… What gives? Is there some super secret hidden setting somewhere? Its like it is jammed off.

Is there data comming to the syslogd? setup a firewall rule to log data on port 123, and see if data is comming to it.
Or if the data is lost another place.

I didnt go so far to create a firewall rule to log it, but there were a couple dozen connections on port 514 to the router.

ohh yeah… port 514 and not 123 :laughing:
How is your Dude set up, to recive the remote logs?

What do you mean how is it setup? I enabled syslog in settings. LOL!

The router was up in production for 20 days and it worked that whole time on Dude 3.4 w 4.4 ROS. The first time I rebooted it, I installed 3.5 Dude and syslog stopped working. I downgraded to 3.4, it still didnt work, I completely removed dude and formatted the CF card, then re-installed 3.5 dude and it still doesnt work.

So I dunno…

Hi roadracer96

Were you able to fix this?

Regards