SYSLOG via Specific Interface

[callaman]

Hi all.
Wanted to setup syslog out of one interface to talk to a management network but all syslog traffic appears to want to route out of the WAN.
There are lots of guides that offer info on how to configure the logging target etc in the user interface but nothing about telling it to go via a nominated interface to reach the target.
Any ideas?


Thanks

[bartjsmit]

Have you set a static route? System: Routes: Configuration

[callaman]

Hi and, apologies for a delayed response.
Yes, there is a static route. (It did occur to me to mention this while writing up the descritpion of the issue).

[Patrick M. Hausen]

Please post the output of

Code: [Select]

netstat -rn and tell us the IP address of your syslog server.

[callaman]

Hi there.

Omitted external IP addresses, for obvious reasons.


172.16.8.0/24      link#2             U          vmx1    <<<< SYSLOG SERVER RESIDES IN THIS NETWORK
172.16.8.16        link#2             UHS         lo0
172.16.12.0/24     link#3             U          vmx2
172.16.12.16       link#3             UHS         lo0
172.16.15.0/24     link#12            U          vmx6
172.16.15.16       link#12            UHS         lo0
172.16.18.0/24     link#4             U          vmx3
172.16.18.16       link#4             UHS         lo0
172.16.21.0/24     link#11            U          vmx5
172.16.21.16       link#11            UHS         lo0
172.16.24.0/24     link#13            U          vmx7
172.16.24.16       link#13            UHS         lo0
172.16.98.0/24     link#10            U          vmx4
172.16.98.16       link#10            UHS         lo0

[Patrick M. Hausen]

And you do not have an explicit gateway set for this directly connected network? Nor do you have any firewall rule with an explicit gateway setting?

If you just let the routing table do it's magic, you should be able to ping the syslog server, and of course also log, with all packets leaving through the vmx1 interface. There must be some explicit configuration changing that.