Feature #11562
closed
Syslog should not require binding to interface for remote logging
0%
Description
As of now, it is not possible to log to remote server without binding syslog to local interface. This shouldn't be required - for log forwarding syslog acts only as a client, not a server. Now it is not possible to set syslog-ng daemon from package to bind on port 514 and at the same time have log fowarding enabled.
Updated by Jim Pingle about 4 years ago
- Status changed from New to Rejected
It's to set the source address of the syslog traffic, not to bind the server. It's necessary for things like tunnel mode IPsec where otherwise the syslog traffic will never enter the tunnel.
You can set it to "Default (any)" and it doesn't bind to a specific interface.
Updated by Ter Ted about 4 years ago
Jim Pingle wrote:
It's to set the source address of the syslog traffic, not to bind the server. It's necessary for things like tunnel mode IPsec where otherwise the syslog traffic will never enter the tunnel.
You can set it to "Default (any)" and it doesn't bind to a specific interface.
This is not true, please have a look at reopened issue for details https://redmine.pfsense.org/issues/11577
Updated by Jim Pingle about 4 years ago
It is true as worded ("Any" is not "a specific interface").