[ previous ] [ next ] [ threads ]
 From:  Jack Pivac <email at delphinus dot co dot nz>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch, m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Captive Portal
 Date:  Fri, 03 Feb 2006 12:29:31 +1300
What about assigning a MAC in the pass thru MAC page to a username as 
well... so when a users pc gets "auto logged in" as such, they also get 
the assigned Bandwidth limit?


Jonathan De Graeve wrote:

>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
>future release.
>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