RE: Example listed in huntgroup file does not work
Message: 9 Date: Wed, 12 Dec 2007 22:41:54 +0100 From: <tnt@kalik.co.yu> Subject: RE: Example listed in huntgroup file does not work To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Message-ID: <MmeHNnnk.1197495714.6796440.tnt@kalik.co.yu> Content-Type: text/plain; charset=ISO-8859-2
But I guess here is my problem. How do you assign more than one NAS to a huntgroup?
The way it is shown in the huntgroups file.
I did, but the user list is not being recognized by more than one. How can I get that user list to be used for all NAS that are in that huntgroup? Or is this a bug?
But this uses SQL which we are not using and would prefer not to.
Use LDAP then. Or feel free to list (same) users for every huntgroup entry.
I should say that I do not want to use an external solution. Creating a huntgroup for each NAS with the exact same user list does work, but then if I have to change a user I would then have to modify what could be over 100 groups.
Ivan Kalik Kalik Informatika ISP
--- Walt Reynolds Principal Systems Security Development Engineer Information Technology Central Services University of Michigan (734) 615-9438
Hi,
I should say that I do not want to use an external solution. Creating a huntgroup for each NAS with the exact same user list does work, but then if I have to change a user I would then have to modify what could be over 100 groups.
i think, therein, lies your problem - you havent looked at the whole logical design - and are fixated on the singular huntgroups file. if you want to control users, in groups, with huntgroups etc then you should be using the huntgroup file to define NAS in groups, and then another config file eg users to tie users to those huntgroups. alan
I did, but the user list is not being recognized by more than one. How can I get that user list to be used for all NAS that are in that huntgroup? Or is this a bug?
No, it's not a bug. It's a flat file entry. Every entry is matched separately. i.e. one entry doesn't "know" what's listed under another.
I should say that I do not want to use an external solution. Creating a huntgroup for each NAS with the exact same user list does work, but then if I have to change a user I would then have to modify what could be over 100 groups.
So, there is a very good case to use database in this case, then? Single entry vs. "over 100" of them to administrate? And why would the database be an "external solution"? Freeradius integrates very well and quite easily with several database servers. And you can leave your passwords where they are and use database just for group creation. Ivan Kalik Kalik Informatika ISP
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Reynolds, Walter -
tnt＠kalik.co.yu