You have to find the attribute used by opnsense and
change OPENWISP_RADIUS_TRAFFIC_COUNTER_REPLY_NAME accordingly.
OpenWISP is clearly returning it in the RADIUS packet which then is shown
in the freeradius debug output, so if the NAS does not respect the
attribute, it's either not an attribute it
Hi Federico,
Thank you for your response.
1. I am using OPNsense as a captive portal. I tested logged in using a test
user with 5 MB limit, use all the limit and but it does not disconnected
for about 30 mins or so.
I can see the accounting is running but there is no action from radius to
disc
Hi,
1. Whether the user is disconnected or not depends on the NAS and what
attribute it uses. What NAS are you using? Coova-chilli, Pfsesne, Hostapd
(WPA Enterprise) a PPPoE server, or what else?
What I have seen with popular open source captive portals is that users are
disconnected close to the
Hello,
I have configured a captive portal with openwisp-radius (running on
virtualenv locally) with free radius. I am able to use it to authenticate
and accounting + basic function to create user through GUI, etc. also ok.
I do have some question below about the 'users' group
The default group
