General Questions

So from what I can see, when captive portal does it's every minute reauthentication check's with radius, this is just a simple, accept/reject query.   It doesnt update any other information.   such as, I'm sending WISPr attributes for bandwidth.   Essentially, what I've done, is worked out a nifty solution for monitoring accounting info on my database/per user, and I can update their bandwidth allocation based upon how much they have downloaded.  so essentially, if user A, downloads to much, their bandwidth gets cut to almost nill, or nothing.   Only problem is. it doesnt work.  evertything works fine from the database/radius end.   but M0n0wall, only checks the accept/reject status, 


note: it works fine, if user logs out, and logs back in, their status is updated, with a "penalty" WISPr attribute......but there is no update on WISPr during their session


so can this be hacked, in m0n0wall, so that it also re-checks the WISPr attribute upon reauthentication every minute.   

Thanks for any help guys

From what I can tell from my own testing, you are right, just checks to make sure the username is valid.

There is a workaround I guess, have your software set their password wrong, maybe add a random 4 character string in front of the password. Then the auth will fail (thus logging them out), afterwards, have it set the password back to normal.  They login, and have less bandwidth.

Basically you want to stop bandwidth hogs, this will work short of cutting out access for them, which if you set the bandwidth to zero, would cause to happen anyway?