[ previous ] [ next ] [ threads ]
 
 From:  Paul Taylor <PaulTaylor at winn dash dixie dot com>
 To:  Andrew Hull <list at racc2000 dot com>, m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  RE: [m0n0wall-dev] "Disable Concurrent Logins" action
 Date:  Fri, 2 Dec 2005 11:04:50 -0500
Andrew,

	Actually, I made the decision on how that would work, since I added
the feature.  This is a slightly different situation than for dialup users.
We felt that legitimate users would rather have the ability to easily switch
machines without having to wait for their logon to timeout on the previous
machine.  We don't expect this situation to happen frequently, but we don't
want to get support calls if that comes up.  We don't run the pop-up window
that allows logouts, as most people would probably have pop-up blockers that
would stop it from working anyhow...

How Monowall reacts to this could be made an option, potentially...  

Paul


-----Original Message-----
From: Andrew Hull [mailto:list at racc2000 dot com] 
Sent: Friday, December 02, 2005 10:25 AM
To: m0n0wall dash dev at lists dot m0n0 dot ch
Subject: [m0n0wall-dev] "Disable Concurrent Logins" action

Hello,
In using the new feature in the Captive Portal -- Disable Concurrent 
Logins, I have a question.
 
Normal practice with dial up users is that subsequent logins are 
rejected, not subsequent logins are accepted and a previously active 
session is terminated. Is there are a reason that the second action was 
decided upon instead of the first (which I consider the standard)?
 
If not, is Mono's response to this scenario up for debate?
 
Thanks,
Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch