[ previous ] [ next ] [ threads ]
 
 From:  "Jonathan De Graeve" <Jonathan dot DeGraeve at imelda dot be>
 To:  "Andrew Hull" <list at racc2000 dot com>, "Mono Wall list" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Issues with the Captive Portal
 Date:  Wed, 27 Sep 2006 18:24:03 +0200
Logs taken from with parts obfuscated:

Version 1.23b3_r168 
built on Tue Aug 29 11:46:59 CEST 2006  


Sep 27 18:14:17 TIMEOUT: 00:xx, 00:xx, 192.168.2.x
Sep 27 18:02:10 MACHINE LOGIN: 00:xx, 00:xx, 192.168.2.x
Sep 27 17:49:16 TIMEOUT: userx, 00:xx, 192.168.3.x
Sep 27 17:22:05 USER LOGIN: userx, 00:xx, 192.168.3.x
Sep 27 17:06:11 TIMEOUT: usery, 00:xx, 192.168.3.x

--
Jonathan De Graeve
Network/System Engineer
Imelda vzw
Informatica Dienst
015/50.52.98
Jonathan dot de dot graeve at imelda dot be 

> -----Oorspronkelijk bericht-----
> Van: Andrew Hull [mailto:list at racc2000 dot com]
> Verzonden: woensdag 27 september 2006 16:21
> Aan: Jonathan De Graeve; Mono Wall list
> Onderwerp: Re: [m0n0wall] Issues with the Captive Portal
> 
> Jonathan De Graeve wrote:
> > I tried exactly the same thing on my production and test with
generic-pc
> and it did what it had todo: log out users.
> >
> > This is a strange issue :(
> >
> > ________________________________
> >
> > Van: Andrew Hull [mailto:list at racc2000 dot com]
> > Verzonden: wo 27/09/2006 15:48
> > Aan: Mono Wall list
> > Onderwerp: Re: [m0n0wall] Issues with the Captive Portal
> >
> >
> >
> > Jonathan De Graeve wrote:
> >> So now it is confirmed by 2 different people.
> >>
> >> The difficult part is to run into the same issue in our test
> environment
> >> to identify the issue. Currently I haven't run into this issue yet
> which
> >> makes it a lot more difficult to solve it off course.
> >>
> >> J.
> >>
> >> --
> >> Jonathan De Graeve
> >> Network/System Engineer
> >> Imelda vzw
> >> Informatica Dienst
> >> 015/50.52.98
> >> Jonathan dot de dot graeve at imelda dot be
> >
> > Good morning,
> >
> > After reading this thread I did some quick testing on my Mono. I can
> > confirm the timeout issue as well.
> >
> > My captive portal idle timeout is set to 5 min. Fired up my laptop,
> > connected it to the 802.11 AP that the CP interface on Mono is
connected
> > to, authenticate on the CP, double check Internet connectivity with
> > google, and then disable the wireless interface on the test laptop.
> >
> > In the CP status page of the web gui, Session start reads 09/27/2006
> > 09:17:36, Last activity reads 09/27/2006 09:17:58. At 09/27/2006
> > 09:22:58 the last activity field had not changed but the test
username
> > was not disconnected.
> >
> > I'd be happy to be as much of a help as I can.
> >
> > Andrew
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> >
> >
> >
> >
> >
> >
> 
> Jonathan,
> 
> I'm using the 1.22 net48xx image on a Soekris net4801. Could that
> difference have any bearing?
> 
> Andy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> 
>