Brad McAllister wrote:
G'day mate, thanks for the quick reply. I already have this in my
radiusd.conf:
realm suffix {
format = suffix
delimiter = @
ignore_default = no
ignore_null = no
}
Have you got suffix in
Yes, the suffix is in the authorize { } section as well. I was just
following the examples with the Auth-Type, I removed them from the
DB, but end up with the same results.
--
Brad McAllister
DLS Internet Services
p. 847.854.4799 x.232
[EMAIL PROTECTED]
On Oct 9, 2006, at 5:26 AM, James
I got it working! I had to put suffix before preprocess in the
authorize { } section
--
Brad McAllister
DLS Internet Services
p. 847.854.4799 x.232
[EMAIL PROTECTED]
On Oct 9, 2006, at 9:18 AM, Brad McAllister wrote:
Yes, the suffix is in the authorize { } section as well. I was
just
G'day mate, thanks for the quick reply. I already have this in my
radiusd.conf:
realm suffix {
format = suffix
delimiter = @
ignore_default = no
ignore_null = no
}
The huntgroups file looks like this:
wireless
Sorry if this has already been addressed. I has been searching all
day and haven't found the solution to my problem. I am attempting to
setup multiple huntgroups to limit the types of connections that
clients can make. Along with this I have a list of realms that are
authenticated locally
Brad McAllister wrote:
If I removed the huntgroups out of the picture, is works fine. The
problem seems to be that the realm is not being stripped off of the
username when it checks it against the usergroup table. If more
information is needed, please let me know. I would really like to get
Hi,
I want to restrict access for particular access points based on a user name.
So a particular user can be authenticated on several access points (through a
single freeRadius server) but should be denied access on others.
I have been reading around, and I think that the way to approach this
[EMAIL PROTECTED] wrote:
I set up an entry in the huntgroups file something like this:
groupname1NAS-IP-Address == 192.168.2.3
Group = firstgroup
No. The Group atribute does Unix group checking. You do NOT want
to use it.
I want to restrict access for particular
[EMAIL PROTECTED] wrote:
I set up an entry in the huntgroups file something like this:
groupname1NAS-IP-Address == 192.168.2.3
Group = firstgroup
Close, I think you want SQL-Group instead of Group.
Then, in my database, I would need the following entries
9 matches
Mail list logo
