Project

General

Profile

Actions

Regression #16127

closed

``syslog`` configuration for ``if_pppoe`` breaks logging for itself and later configuration entries in certain cases

Added by Craig Coonrad 9 days ago. Updated 8 days ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Logging
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
25.03
Release Notes:
Force Exclusion
Affected Version:
Affected Architecture:

Description

pfSense version : 25.03-BETA
platform : QEMU

25.03-BETA appears to partially break remote logging. I'm seeing log messages from apps like unbound, charon, and kea, but no system messages.
To reproduce. Configure logging to remote server, run `logger test message` and nothing arrives on remote server. Rollback to 24.11 and works fine.

Actions #1

Updated by Jim Pingle 9 days ago

  • Project changed from pfSense Plus to pfSense
  • Category changed from Logging to Logging
  • Status changed from New to Confirmed
  • Priority changed from Normal to High
  • Target version changed from 25.03 to 2.8.0
  • Release Notes changed from Default to Force Exclusion
  • Plus Target Version set to 25.03

Looks like this is from something in if_pppoe logging and it's also in CE

When a config has "everything" checked it should end like this:

!*
*.*                                                             @x.x.x.x

But now it ends like this:

!*
:msg, startswith, "if_pppoe: " 
*.*                                                             /var/log/ppp.log!*
*.*                                                             @x.x.x.x

The directive that should be sending all logs to a remote server is missing its "!*" line since it's tacked on the end of the PPPoE line.

Actions #2

Updated by Jim Pingle 9 days ago

  • Status changed from Confirmed to In Progress
  • Assignee set to Jim Pingle
Actions #3

Updated by Jim Pingle 9 days ago

  • Subject changed from Remote logging failure to ``syslog`` configuration for ``if_pppoe`` breaks logging for itself and later configuration entries in certain cases
Actions #4

Updated by Jim Pingle 9 days ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100
Actions #5

Updated by Craig Coonrad 8 days ago

  • Status changed from Feedback to Resolved

Applied commit 063d171d17fbf1c10883bdd25b8de56c33f4454c to System_Patches w/reboot.

Tested/Success. Remote logging working again.

Actions

Also available in: Atom PDF