Bug #16406
openNo logfile for captive portal auth
0%
Description
Hi PFSense-Team!
We run PFSense at around 200 locations and we are using voucher and captive portal intensively. All locations do remote syslog of its voucher auths.
We upgraded two locations to 2.8.0 (APU HW from PC Engines).
After the upgrade, logging has stopped working. No local file, no remote syslog.
Page: ip_address/status_logs.php?logfile=portalauth
(Asked the community on forum.netgate.com but got no replies)
Files
Updated by Kris Phillips 25 days ago
- Status changed from New to Incomplete
Testing this on 2.8.1. I'm unable to recreate this bug report. When connecting, I get an authentication message, as expected.
Sep 6 20:53:43 logportalauth 423 Zone: testzone - ACCEPT: testuser, 52:54:00:a2:67:79, 192.168.1.100
Updated by Volker Werbus 25 days ago
- File fursty3.jpg fursty3.jpg added
- File fursty2.jpg fursty2.jpg added
- File fursty1.jpg fursty1.jpg added
Hi Kris,
just upgraded two systems from 2.8.0 to 2.8.1: Same result, no captive portal authentication logs ... see attachments.
However, even with 2.8.0 when you turn off authentication, logs are recorded (fursty4.jpg). When you turn back to local database (=voucher), no records at all ...
Best,
Volker
Updated by aleksei prokofiev 18 days ago
Tested on 2.8.1 and unable reproduce, please provide exact steps to reproduce the issue.
Updated by Volker Werbus 18 days ago
Aleksei,
here is what we did (on two different plattforms: APU 1D4 (PC Engines) and Futro S720 (Fujitsu). Both equipped with 8GB SSDs, both running fine with 2.7.2 before. Did an update to 2.8.0 (and later 2.8.1) using option 13 on the console.
We are extensively using voucher codes, usually we have 3-4 rolls active, 65500 codes each. When we turn off authentication (option "authenticaton methode: None, don't authenticate users"), the logging works. It shows "unauthenticated" entries in portalauth.log. Once authentication method is set to local database, no logging at all anymore.
I can provide you with the config.xml if you like.
Another observation: From time to time, unfortunately not reproducable, the db-file for used vouchers gets modified and marks vouchers used which are definetly not used. I reported this with earlier releases, but it couldn't be fixed as it was not reproducable.
Best,
Volker