NAS is nearly analogous to RADIUS client. basically, it depends on the thing that is talking to Freeradius to say how to configure kicking someone off in real time.
You could stick a script before authentication happens to check whether or not a user has exceeded his bandwidth and then either allow or dont allow them to log on again but that seems like a bad way of doing it. On Mon, Jun 7, 2010 at 4:00 PM, RaidenII <tonytz...@gmail.com> wrote: > > I am not using a NAS actually. It is an ordinary x86 server. > > > Alan DeKok-2 wrote: >> >> That is usually the function of the NAS. >> >> In 2.1.9, you can configure a CoA packet in the server, *if* the NAS >> supports CoA. i.e. check for limit in the "accounting" section, and >> send a CoA packet to disconnect them if so. >> >> See the NAS documentation for how to limit total traffic. It usually >> *isn't* those two attributes. >> >> Alan DeKok. >> - >> List info/subscribe/unsubscribe? See >> http://www.freeradius.org/list/users.html >> >> > > -- > View this message in context: > http://old.nabble.com/How-to-use-Freeradius-with-traffic-limit--tp28809968p28811891.html > Sent from the FreeRadius - User mailing list archive at Nabble.com. > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > -- Random quote of the week/month/whenever i get to updating it: "Quis custodiet ipsos custodes?": "who shall watch the watchers themselves?" - Juvenal - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
