Actions
Feature #11577
closed
Syslog should not require binding to interface for remote logging
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Logging
Target version:
-
Start date:
02/28/2021
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
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.
Please do not reject this issue. To reply your previous message
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.
No, it actually binds the server port. You can check it on console by "netstat -na | grep 514". If you set to "any" - it binds to all interfaces. You don't have to bind the server in order to send the traffic to remote, even when the tunnel is up - always the routing rules apply.
Updated by 
Updated by
Actions