Bug #4983: ipguard - unable to read its own configuration with PBI -> users locked out - pfSense Packages - pfSense bugtracker

Actions

Copy link

Bug #4983

closed

ipguard - unable to read its own configuration with PBI -> users locked out

Added by Kill Bill almost 10 years ago. Updated over 9 years ago.

Status:

Resolved

Priority:

High

Assignee:

Category:

Target version:

Start date:

08/18/2015

Due date:

% Done:

Estimated time:

Plus Target Version:

Affected Version:

2.2.x

Affected Plus Version:

Affected Architecture:

All

Description

Filing this here for reference. Issue as per subject and log below.

Forum thread: https://forum.pfsense.org/index.php?topic=98138.0

Aug 17 16:02:10 warring fopen(/usr/local/etc/ipguard_lan.conf): No such file or directory
Aug 17 16:02:10 notice em1 00:07:e9:5d:bc:ac 192.168.4.1 (1 pairs) fake de:ad:d:fc:09:ee
Aug 17 16:02:10 warning stat(/usr/local/etc/ipguard_lan.conf): No such file or directory
Aug 17 16:02:59 notice xxxx: e8:9a:8f:bb:d0:8f 192.168.4.10 192.168.4.1

The file of course exists, but ipguard won't see it due to PBI screwing things badly yet again. This results in everyone getting locked out as soon as you enable ipguard on the interface. (I'd also assume the daemon to bail out on similar fatal errors, instead of logging a "warning", but sadly that doesn't happen either.)

Fix: https://github.com/pfsense/pfsense-packages/pull/1008