Bug #2409
closedipfw - entryzerostats
0%
Description
I apologize for my english...
pfSense 2.0.1
When logging in CaptivePortal (auth Radius, Accounting Updates - Start/Stop)
after RADIUS_ACCOUNTING_STOP traffic counter does not reset.
Code in /etc/inc/captiveportal.inc
...
exec("/sbin/ipfw table 1 entrystats {$cpentry2}");
...
exec("/sbin/ipfw table 1 entryzerostats {$cpentry2}");
...
entrystats working ok.
entryzerostats - an error:
ipfw: getsockopt(IP_FW_TABLE_ZERO_ENTRY_STATS): Bad address
Updated by Vlad Arakin over 12 years ago
in version 2.1.0 (bild 18May2012) an error is confirmed.
Updated by Ermal Luçi about 12 years ago
Is this still the same with latest snaps?
Updated by Ermal Luçi almost 12 years ago
- Status changed from New to Feedback
This should behave even better with latest snapshots.
Updated by Vlad Arakin over 11 years ago
Upgrade to 2.0.3-RELEASE - bug confirmed:
ipfw table 1 entryzerostats 10.0.0.83
ipfw: getsockopt(IP_FW_TABLE_ZERO_ENTRY_STATS): Bad address
check back tomorrow 2.1-RC0...
Updated by Vlad Arakin over 11 years ago
Using latest snaps
when we use Captive portal, RADIUS_ACCOUNTING_STOP packets are not sent to RADIUS server
Updated by Chris Buechler about 11 years ago
- Status changed from Feedback to Resolved