sql is not something we have a lot of expertise in so was hoping there is some
other way to be able to get this to work. Can I use unlang in some way to
support the users with multiple group names?
--
Walt Reynolds
Principal Systems Security Development Engineer Information Technology Central
I am trying to find a good way to limit who is able to login at specific NAS's.
I know I could add all the allowed user names to the Huntgroups file, but this
can get tedious as I must do it for each NAS. So I figured the best way was to
use groups. The users are not account holders on the
Huntgroup-Name == wilab2, Etc-Group-Name == wilab2
Fall-Through = yes
DEFAULT Huntgroup-Name == nolab, Etc-Group-Name == nolab
Fall-Through = yes
Ivan Kalik
Kalik Informatika ISP
Dana 4/11/2008, Reynolds, Walter [EMAIL PROTECTED] pi?e:
I am trying to find
I am having a problem that I am not sure where to look for a solution.
I install Freeradius via src with the straight 'configure', 'make' and
'make install'.
No real problems show up during the install that are obvious so I
configure and run the server with a local account. All good and fine
Message: 9
Date: Wed, 12 Dec 2007 22:41:54 +0100
From: [EMAIL PROTECTED]
Subject: RE: Example listed in huntgroup file does not work
To: FreeRadius users mailing list
freeradius-users@lists.freeradius.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-2
I am looking at that option, but I should not have to. Per the
huntgroups file:
# This file can also be used to define restricted access
# to certain huntgroups. The second and following lines
# define the access restrictions (based on username and
#
as is.
Normally, you would add those users to a group and use Huntgroup-Name
check in radgroupcheck.
But this uses SQL which we are not using and would prefer not to.
Ivan Kalik
Kalik Informatika ISP
Dana 11/12/2007, Reynolds, Walter [EMAIL PROTECTED] pi?e:
I have tried to set up
In looking at the list and several examples from various places I
noticed that Fall-Through = xxx has been listed in different ways. I
have seen Yes yes and 1
What are the options and where would I have been able to find the logic
in the src so I could have looked myself? Thanks.
---
Walt
You can also use the huntgroups file
For example:
LimitedAccess NAS-IP-Address == 191.168.1.53
User-Name == firstuser,
User-Name == aaa,
User-Name == bbb,
User-Name
=ISO-8859-1
Reynolds, Walter wrote:
...
DEFAULT Freeradius-Proxied-To == 127.0.0.1
Fall-Through = Yes
That entry does nothing.
I agree it does nothing for authentication, but this will be part of
the solution to get accounting records based on the inner
--
Walt Reynolds
Principle Systems Security Development Engineer
Information Technology Central Services
University of Michigan
(734) 615-9438
-Original Message-
Message: 5
Date: Fri, 12 Oct 2007 10:45:11 +0200
From: Alan DeKok [EMAIL PROTECTED]
Subject: Re: 802.1x
We also have this working with the below settings. However in running
ver 1.1.6 (maybe others) we have found that there is some sort of
problem that will cause the Freeradius server to crash. This seems to
be tied to request with incorrect passwords as notated by the following
in the log:
Thu
-
From: Reynolds, Walter
Sent: Friday, September 21, 2007 10:37 AM
To: 'freeradius-users@lists.freeradius.org'
Subject: Unresponsive Child Crashing Server 1.1.6
I am having a problem where my Freeradius service is crashing several
times a day. It will follow an alert in the log
I am having a problem where my Freeradius service is crashing several
times a day. It will follow an alert in the log with Unresponsive Child
which I know is usually doe to a slow back end authentication method
(usually SQL). Well I am using Kerberos as the back end and every time
I debug the
14 matches
Mail list logo
