[ previous ] [ next ] [ threads ]
 From:  "Jonathan De Graeve" <Jonathan dot DeGraeve at imelda dot be>
 To:  "Peter Boosten" <peter at boosten dot org>, <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall-dev] Suspected bug in captive portal (1.22)
 Date:  Wed, 11 Oct 2006 20:18:55 +0200
> Whenever the session ends by User-Request or Admin-Reset,
> is updated correctly,
> but whenever the session times out (AcctTerminateCause: Idle-Timeout),
> AcctSessionTime holds an
> incorrect value.
> For instance: I had a session of 24 minutes (en seconds) but
> AcctSessionTime would only register
> 510 seconds. This didn't happen in 1.2.

It is designed to work like this. In our opinion (and also the WISP
draft) the user should only be accounted for the time actually being

Assume this situation: users goes online at 00:00 and gets logged-off at
00:30. This would normally be a session-time of 30minutes. BUT if your
idle-timeout is 10minutes and idle-timeout is the cause of the log-off
the NAS will only send 20minutes as session-time. It doesn't take the
hard-timeout,idle-timeout into account.

> Next I noticed that although I use interim updates, AcctSessionTime
> updated, unless the session
> ends. This is also different from version 1.2.
> Has anyone reported this already (didn't find it in the archive)?

I know about this 'issue'. It will be fixed in a next version, no ETA
(it already is in SVN) but I'm currently way to busy at my work with
different stuff.

Kind Regards,


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