Actually I'm using the MaxSession statement to avoid duplicate login to
the network. Unfortunately that means that if a client hangs (so he
doesn't logoff) he cannot re-login until I manually delete the session
from the RadOnline table.
Is it possible to configure Radiator so that the second connection can
get trough but would kill the first connection?
Should I use the afterlogin hook? can I have any hint?
:D
Thanks
- (RADIATOR) Maxsessions Todd Dokey
- Re: (RADIATOR) Maxsessions Hugh Irvine
- (RADIATOR) MaxSessions Robert
- Re: (RADIATOR) MaxSessions Hugh Irvine
- Re: (RADIATOR) MaxSessions Robert
- (RADIATOR) Freaky AuthBy DynAddress Proble... Brian Morris
- Re: (RADIATOR) Freaky AuthBy DynAddres... Hugh Irvine
- Re: (RADIATOR) Freaky AuthBy DynA... Brian Morris
- Re: (RADIATOR) Freaky AuthBy ... Hugh Irvine
- Re: (RADIATOR) MaxSessions Hugh Irvine
- Re: (RADIATOR) MaxSessions Andrea Brancatelli
- Re: (RADIATOR) MaxSessions Hugh Irvine
