https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162021-02-27T15:05:06ZpfSense bugtrackerpfSense - Feature #11562: Syslog should not require binding to interface for remote logginghttps://redmine.pfsense.org/issues/11562?journal_id=517162021-02-27T15:05:06ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>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.</p>
<p>You can set it to "Default (any)" and it doesn't bind to a specific interface.</p> pfSense - Feature #11562: Syslog should not require binding to interface for remote logginghttps://redmine.pfsense.org/issues/11562?journal_id=517442021-03-01T00:02:37ZTer Ted
<ul></ul><p>Jim Pingle wrote:</p>
<blockquote>
<p>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.</p>
<p>You can set it to "Default (any)" and it doesn't bind to a specific interface.</p>
</blockquote>
<p>This is not true, please have a look at reopened issue for details <a class="external" href="https://redmine.pfsense.org/issues/11577">https://redmine.pfsense.org/issues/11577</a></p> pfSense - Feature #11562: Syslog should not require binding to interface for remote logginghttps://redmine.pfsense.org/issues/11562?journal_id=517552021-03-01T07:41:16ZJim Pingle
<ul></ul><p>It is true as worded ("Any" is not "a specific interface").</p>