Use huntgroups. You group users into groups and devices into huntgroups. Ivan Kalik Kalik Informatika ISP Dana 2/10/2008, "super_tomtom" <super_tomtom@hotmail.com> piše:
Ok that brings me back to my initial problem... My first try was to put in the radcheck table a condition like this : NAS-Identifier == LMS2 This works very fine, but limits to only one NAS Identifier. I need to allow some clients to log in from different NAS ids... Is there a way to put multiple conditions in the radcheck table such as (NAS-Identifier == LM1) || (NAS-Identifier == LMS2) ? Thanks
tnt-4 wrote:
So, if I set the NAS-Identifier to "LMS2" (the one used by my chillispot portal), the condition NAS-Identifier == LMS2 matches, so radius puts me
to
the "hotel1" group. If it doesn't match (while using radtest command for example), it continues the login process, but considering that i don't own any group... So in my problem explained before, the user can log in even if he's not recognized as coming from the hotel he was expected to come from... What I would like to find is a way to allow a users to log in, only if they have been attributed to a group...
Ah, failed check in sql groups won't reject the user. It will just cause group info to be ignored. This is to allow the user to be a member of multiple groups - if he doesn't match one, then checks go on to next one with lower priority etc.
Use radcheck for checks that should reject the user.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- View this message in context: http://www.nabble.com/Checking-NAS-Identifier-in-the-radgroupcheck-table-tp1... Sent from the FreeRadius - User mailing list archive at Nabble.com.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html