It has already been one month after releasing the 1.21 m0n0wall version
with the new radius framework and a captive portal code cleanup.
However the framework introduced was only related to the authentication
part, some few changes were also been made to the accounting part but it
still doesn't use the new framework.
Since we didn't got any reports of failure for the authentication part,
I assume that all went well and the coding seems to be (very) stable.
I will introduce the new framework also for the accounting part for the
Furthermore, the captive portal roadmap:
User based bandwidth limitation (speed, not volume) (going further on
the work by Rob Parker)
User volume limitation (session based) since so much people seems to
have big problems configuring the radius server todo this
About the bandwidth limitation, I'm thinking about a dynamic
reconfiguration feature. If radius reauthentication is done, and when
this option is set its possible to dynamically change the users speed
during the session based on the radius response putting the user on
smallband during its session when he exceeded lets say a certain volume
Any more feature requests/ideas can always be mailed back to the list
Jonathan De Graeve
jonathan dot de dot graeve at imelda dot be
Always read the manual for the correct way to do things because the
number of incorrect ways to do things is almost infinite