|
||||||||
RADIUS Idle-Timeout is now also supported (since 1.21b3-unofficial) If Idle-Timeout == 0 it is assumed that user has no idle-timeout. If none is specified with radius the default of the system is taken. I will have a look at the different Acct-Terminate-Cause options... J. -- Jonathan De Graeve Network/System Administrator Imelda vzw Informatica Dienst 015/50.52.98 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 --------- -----Oorspronkelijk bericht----- Van: Stuwart Jos [mailto:stuwart dot jos at gmail dot com] Verzonden: donderdag 15 december 2005 19:59 Aan: m0n0wall at lists dot m0n0 dot ch Onderwerp: [m0n0wall] Radius Idle-Timout and Acct-Terminate-Cause Hello ! Is there any way that I can make captive portal to disconnect user according to the idle-timeout setting in Radius instead of m0n0wall configuration? I've tried the version from inf.imelda.be and it could correctly disconnect user according to the session-timout setting in Radius, so I'm wondering it could also accept the idle-timeout setting from Radius.... Another issue is the acct-terminate-cause issued from m0n0wall when disconnect user, it always sent "User-Request" no matter it's because user logout, idle-timeout or session-timeout, how could I make it sent out the correct reason of disconnection ? Thanks a lot !! Stanley |