[ previous ] [ next ] [ threads ]
 From:  "Jessica Aguilar" <jaguilar at skyriver dot net>
 To:  "YvesDM" <ydmlog at gmail dot com>, <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Captive portal problems
 Date:  Mon, 23 Mar 2009 13:21:10 -0700
Hello All,

Thanks for your suggestions, however Problem is when they tried to login
again immediately. Once they login one time and didn't log out or meet
the time out requirements then they are not able to browse they get the
page cannot be display.

I can force them to log out everybody after 2 or 3 hours problem is that
if somebody is in the middle of something so they will have to re login
which creates another complain about intermmitant connection.

The way I am doing this is log them out manually or bypassing the
captive portal but what is the purpose of having the captive protal

Anybody experience this problem and find a way to work it around? 


-----Original Message-----
From: YvesDM [mailto:ydmlog at gmail dot com] 
Sent: Friday, March 20, 2009 8:45 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Captive portal problems

On Fri, Mar 20, 2009 at 7:58 PM, Jessica Aguilar
<jaguilar at skyriver dot net>wrote:

> Hello All,
> I am having some problems with captive portal
> 1.- User login the first time to captive portal fine  no problem.   I
> can see the user log in on captive portal status.
> 2.- If the user didn't log out or wait enough time to time out and
> to access the internet then it goes to page cannot be display. I did
> some work around and what I currently do  is I log out manually by
> into the captive portal status.

Hi jessica,

This is very strange, I never saw this behavior.
What version are you using and which client browser?
Is their maybe a proxy set in the browser settings? (just guessing)

> Is there anyway I can do this automatically.

Not that I know of, but normally you won't need that too

> The other problem I have is users start complaining that they need to
> keep re authenticate  every certain time . I tried to play with the
> time out but did get a solution.

You don't need to play with idle timeout, but with session time-out.
Idle timeout means a user get logged out after x seconds when there is
activity or any traffic sent.
If you for example set session time-out to 86400 (== 1 day in seconds)
users will only have to login once every 24 hours.

 Kind regards,