[ previous ] [ next ] [ threads ]
 
 From:  "Jonathan De Graeve" <Jonathan dot De dot Graeve at imelda dot be>
 To:  "Jarrod O'Connell" <jarrod at infynite dot com dot au>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: m0n0wall 1.2 & Session-Timeout
 Date:  Tue, 28 Feb 2006 10:18:47 +0100
If you enabled the
'disable mac filtering' session timeout wouldn't work.

I assume you installed 1.21 since the option isn't in 1.2

This bug is fixed in the current repository and will be available in
1.22


J.

> -----Oorspronkelijk bericht-----
> Van: Jarrod O'Connell [mailto:jarrod at infynite dot com dot au]
> Verzonden: dinsdag 28 februari 2006 10:01
> Aan: Jonathan De Graeve
> Onderwerp: m0n0wall 1.2 & Session-Timeout
> 
> Hi Jonathan,
> 
> Firstly I just want to say great work with your improvements to the
> m0n0wall
> project!
> 
> Secondly I have setup m0n0wall 1.2 (currently running from an ISO) and
> have
> it authenticating to Freeradius server using a MySQL database.
Everything
> seems working fine except for the Session-Timeout attribute. I can see
> that
> the Radius server is sending the Session-Timeout parameter but
m0n0wall
> isn't disconnecting the client after the Session-Timout period.
> 
> The option is ticked in the GUI for Session-Timeout attribute.
> 
> Is there anything you can think of that could be stopping this from
> working?
> Is there something else I can check?
> 
> 
> Here is the output from radiusd -X
> 
> <snip>
> 
> Listening on proxy *:1814
> Ready to process requests.
> rad_recv: Access-Request packet from host 192.168.1.1:3310, id=208,
> length=102
>         NAS-Port-Type = Ethernet
>         Service-Type = Login-User
>         User-Name = "jarrod"
>         User-Password = "password"
>         Called-Station-Id = "4c:00:10:60:2c:3d"
>         Calling-Station-Id = "00:00:e2:86:43:7d"
>         NAS-Port = 6
>   Processing the authorize section of radiusd.conf
> modcall: entering group authorize for request 0
>   modcall[authorize]: module "preprocess" returns ok for request 0
>   modcall[authorize]: module "chap" returns noop for request 0
> radius_xlat:  'jarrod'
> rlm_sql (sql): sql_set_user escaped user --> 'jarrod'
> radius_xlat:  'SELECT id,UserName,Attribute,Value,op FROM radcheck
WHERE
> Usernam
> e = 'jarrod' ORDER BY id'
> rlm_sql (sql): Reserving sql socket id: 4
> radius_xlat:  'SELECT
> radgroupcheck.id,radgroupcheck.GroupName,radgroupcheck.Att
> ribute,radgroupcheck.Value,radgroupcheck.op  FROM
radgroupcheck,usergroup
> WHERE
> usergroup.Username = 'jarrod' AND usergroup.GroupName =
> radgroupcheck.GroupName
> ORDER BY radgroupcheck.id'
> radius_xlat:  'SELECT id,UserName,Attribute,Value,op FROM radreply
WHERE
> Usernam
> e = 'jarrod' ORDER BY id'
> radius_xlat:  'SELECT
> radgroupreply.id,radgroupreply.GroupName,radgroupreply.Att
> ribute,radgroupreply.Value,radgroupreply.op  FROM
radgroupreply,usergroup
> WHERE
> usergroup.Username = 'jarrod' AND usergroup.GroupName =
> radgroupreply.GroupName
> ORDER BY radgroupreply.id'
> rlm_sql (sql): Released sql socket id: 4
>   modcall[authorize]: module "sql" returns ok for request 0
> modcall: group authorize returns ok for request 0
> auth: type Local
> auth: user supplied User-Password matches local User-Password
> Sending Access-Accept of id 208 to 192.168.1.1:3310
>         Idle-Timeout = 10
> Finished request 0
> Going to the next request
> 
> </snip>
> 
> 
> I appreciate any assistance you could give me
> 
> Jarrod O'Connell
> 
> 
> ----
> This message has been scanned by BitDefender
> and found to be clean.
> 
>