Actions
Regression #16285
closed
``syslogd`` does not respect the configured IP address binding
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
25.07
Release Notes:
Default
Affected Version:
2.8.0
Affected Architecture:
All
Description
When configuring remote a syslog server syslogd is invoked with the user selected interface binding if selected:
/usr/sbin/syslogd -O rfc3164 -s -c -c -l /var/dhcpd/var/run/log -P /var/run/syslog.pid -f /etc/syslog.conf -b 192.168.25.1
<syslog>
<filterdescriptions>1</filterdescriptions>
<nentries>500</nentries>
<logcompressiontype>none</logcompressiontype>
<format>rfc3164</format>
<rotatecount></rotatecount>
<remoteserver>172.21.16.13:5140</remoteserver>
<remoteserver2></remoteserver2>
<remoteserver3></remoteserver3>
<sourceip>lan</sourceip>
<ipproto>ipv4</ipproto>
<logall></logall>
<logconfigchanges>enabled</logconfigchanges>
<enable></enable>
</syslog>
However in pfSense 2.8 that setting is ignored and the logically closest IP address is used as source instead:
WAN udp 172.21.16.32:37402 -> 172.21.16.13:5140 SINGLE:NO_TRAFFIC 865 / 0 173 KiB / 0 B
This is a regression since 2.7.2
Updated by Steve Wheeler 4 months ago
- Plus Target Version set to 25.07
Also broken in 25.03/25.07
However works as expected in dev builds because of a newer upstream patch:
https://github.com/pfsense/FreeBSD-src/commit/ae4f708f0b383277505daa191e21db399b558839
Updated by Jim Pingle 4 months ago
- Plus Target Version changed from 25.07 to 25.11
Updated by Jim Pingle 3 months ago
- Subject changed from syslod no longer respects the configured IP binding to ``syslogd`` does not respect the configured IP address binding
- Status changed from New to Feedback
- Target version changed from CE-Next to 2.8.1
- % Done changed from 0 to 100
- Plus Target Version changed from 25.11 to 25.07
The commit that fixes this is in the Plus 25.07 and CE 2.8.1 branches, so it should be ready for testing.
Updated by
Actions