Project

General

Profile

Actions

Regression #16285

open

syslod no longer respects the configured IP binding

Added by Steve Wheeler 2 days ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
System Logs
Target version:
Start date:
Due date:
% Done:

0%

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

Actions #1

Updated by Steve Wheeler 2 days 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

Actions

Also available in: Atom PDF