Setting different IDLE-TIMEOUTS based on IP Address
john.giordano at ttmi.us
Wed Apr 17 20:01:47 CEST 2013
Ok... I feel as though I am trying to solve a riddle here.
I thought that may be the case but!
I removed the IDLE-TIMEOUT entry from my user stanza and the NAS then rejected me.... I think that was because no IDLE-TIMEOUT was being sent at all from the server to the client....
From: freeradius-users-bounces+john.giordano=ttmi.us at lists.freeradius.org [mailto:freeradius-users-bounces+john.giordano=ttmi.us at lists.freeradius.org] On Behalf Of A.L.M.Buxey at lboro.ac.uk
Sent: Wednesday, April 17, 2013 10:49 AM
To: FreeRadius users mailing list
Subject: Re: Setting different IDLE-TIMEOUTS based on IP Address
> STDOUT shows that I am being handed the IDLE-TIMEOUT of 1800 even
> though I am coming from the LAB Node with IP of 192.168.0.15 The user (me) does have an IDLE-TIMEOUT set in my user section of 1800 but I thought the above lines would set it and because the IDLE-TIMEOUT in my user section is using the = operator.
yes...AFTER the huntgroup stuff you've added..as you say, you added that new stuff at the top of the users file... what comes later overrides
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users