Project

General

Profile

Actions
Copy link

Regression #14120

closed

``syslogd`` tries to bind interfaces with no IP address

Added by Steve Wheeler about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
System Logs
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.05
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
All

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

Actions
Copy link

Also available in: Atom PDF