Regression #14120
closed
``syslogd`` tries to bind interfaces with no IP address
100%
Description
In 23.01 syslogd will try to bind to an interface that has no IP resulting in the service failing to start.
This is not the behaviour implied on the syslog settings page:
NOTE: If an IP address cannot be located on the chosen interface, the daemon will bind to all addresses.
It also does this even if no remote syslog server is set and Remote Logging is disabled. That also means the bad setting is not shown in the gui when checking the settings.
It should not be possible to select as Source Address an interface that does not have a valid IP address.
An existing config that has such an interface set should beignored if remote logging is disabled.
Tested: 23.01-REL amd64
Updated by Jim Pingle over 1 year ago
- Subject changed from Syslog tries to bind to interfaces with no IP to ``syslogd`` tries to bind interfaces with no IP address
- Assignee set to Jim Pingle
Did this happen on previous versions or just on 23.01 and after?
EDIT: Nevermind, it probably did based on the code. But I've got a fix in.
Updated by Jim Pingle over 1 year ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 7e7910fded01a44a7ab1014e95bbfb0fbae709a8.
Updated by Danilo Zrenjanin over 1 year ago
- Status changed from Feedback to Resolved
The patch fixes this behavior.
The syslogd starts even if there is no IP on the defined source interface. In that case it binds to all interfaces:
udp4 0 0 *.514 *.* udp6 0 0 *.514 *.*
Tested against:
23.01-RELEASE (amd64) built on Fri Feb 10 20:06:33 UTC 2023 FreeBSD 14.0-CURRENT
I am marking this ticket resolved.