Captive Portal add RADIUS attributes for traffic quotas
|Affected version:||Affected Architecture:|
AFAIK pfsense NAS recognizes the WISPr RADIUS attributes such as
In certain deployments it would be helpful to also have traffic limits.
Could consider adding custom RADIUS attributes, similar to what some other NAS provide e.g.
ChilliSpot-Max-Input-Octets Maximum number of octets the user is allowed to transmit. After this limit has been reached the user will be disconnected.
ChilliSpot-Max-Output-Octets Maximum number of octets the user is allowed to receive. After this limit has been reached the user will be disconnected.
ChilliSpot-Max-Total-Octets Maximum number of octets the user is allowed to transfer (sum of octets transmitted and received). After this limit has been reached the user will be disconnected.
Mikrotik-Recv-Limit - total receive limit in bytes for the client
Mikrotik-Recv-Limit-Gigawords - 4G (2^32) bytes of total receive limit (bits 32..63, when bits 0..31 are delivered in Mikrotik-Recv-Limit)
Mikrotik-Xmit-Limit - total transmit limit in bytes for the client
Mikrotik-Xmit-Limit-Gigawords - 4G (2^32) bytes of total transmit limit (bits 32..63, when bits 0..31 are delivered in Mikrotik-Recv-Limit)
(Note: Various other examples are available in FreeRadius' dictionary directory)
#1 Updated by Josep Pujadas over 1 year ago
CoovaChilli is an open-source software access controller, based on the popular (but now defunct) ChilliSpot project, and is actively maintained by an original ChilliSpot contributor.
It has a FreeBSD port, http://www.freebsd.org/cgi/ports.cgi?query=chilli&stype=all
#2 Updated by Alexander Wilke 11 months ago
CaptivePortal is sending these four attributes:
So it is up to the backend (freeradius and/or (mysql) database) to use these attributes/data in the way you want.
freeradius2 package on pfsense is able to do that. pfsense 2.1 is now sending the correct accounting bytes (2.0.x didn't).