[ previous ] [ next ] [ threads ]
 
 From:  "Doug Tebbit" <d dot tebbit at gmail dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Captive Portal sessions not being shut down after the users idle timeout period expires
 Date:  Mon, 25 Sep 2006 10:58:16 +0800
I have noticed some intermittent issues with the Captive Portal, previously
I was using v1.22 but changed to v1.23b1 to see if these problems were
resolved.

While v1.23b1 seems quite stable, I note there are still some issues with
Captive Portal sessions not being shut down after the users idle timeout
period expires. Also the Captive Portal status page does not always show all
the active sessions.

Mostly it works really well, these are intermittent issues.

This is what I noted yesterday:

(1) Logged in to Captive Portal at 10:21 from 172.22.10.108 (Portal is set
to disconnect after 10 min inactivity, Logout box not used). All worked as
expected.

(2) Shut down Laptop at 10:33

(3) Started same test laptop at 16:30

(4) No Portal page appeared and I could get to Google without
authenticating.

My user details and IP are NOT listed in "Status>Captive Portal" and when I
check logs there is no "TIMEOUT: Username, , 172.22.10.108" message in the
logs (I use a log server).

When I checked status.php I can see a rule for my test IP (which I assume
was created when I connected at 10:21AM

10031     661      86046 skipto 50000 ip from 172.22.10.108 to any in
10031     651     542130 skipto 50000 ip from any to 172.22.10.108 out

Thanks