Hi all. I am new to the list and m0n0wall so tell me to shut up if this has
already been solved.
Back on My 28th Peter Curran posted about his work on the RADIUS feature added
to the captive portal. I am very interested in helping with this venture. I
fixed the RADIUS support in NoCat as well as wrote the RADIUS accounting for
it. I am more impressed with m0n0wall at this point and want to see those
same features make their way into this project.
There was a question about "hard timeouts" in the original post. I assume
this means a maximum time that the user can be logged in for any given
session right? If so there is already an attribute for the response packet
that handles this, Session-Timeout. Unlike the name might suggest it isn't a
"timeout" but more a time limit. This Session-Timeout value can always
return some number of minutes, say 60, for each session or it can be
calculated by your RADIUS server to provide for a some many minutes per
day/month/year solution. The RADIUS session must terminate when
Session-Timeout expires, whish is what I think you guys are looking for. I
implemented this feature in NoCat and it works great. We can now produce
"calling cards" for our hotspots that only have 60 minutes for life on them.
We can also create plans that have 4 hours week max.
I haven't looked closely but it sounds like you have implemented the
Idle-Timeout attribute. If you haven't that would be a good one to do as
well. I never go around to finishing that for NoCat unfortunately. Users
that are on a minute/period plan might want shorter timeouts than someone
that is on an unlimited plan. Being able to adjust the timeout per user is
Anyway, like I said, I really want to help out with the captive portal and
RADIUS integration. Would those involved in that feature please contact me
so I can get up to speed.
Jacob S. Barrett
Chief Technology Officer
email: jbarrett at pogozone dot com
address: 114 W. Magnolia Street Suite 417
Bellingham, Washington 98225