On Wed 26 Sep 2007, Alan DeKok wrote:
> Jorgen Lundman wrote:
> > Would those be appreciated, or just end up in-house?
>
> If the patch is against CVS head, it's likely to be accepted.
Yep. I think this would be a usefull option and would be happy to help with
patch testing if you do the writin
Turbo Fredriksson wrote:
> Isn't this 'radiusClientIPAddress' (RADIUS attribute 'Client-IP-Address')?
>
> 'Client-IP-Address. Matches the IP address of the client in the request.'
No. That *matches* the client address. It's a comparison for
policies. It does NOT define a client.
Real clie
>>>>> "Alan" == Alan DeKok <[EMAIL PROTECTED]> writes:
Alan> Jorgen Lundman wrote:
>> Is it possible to also store the NAS IPs in LDAP, so changes
>> can be done centrally?
Alan> Not without source code patches.
Isn't thi
Jorgen Lundman wrote:
>
> Would those be appreciated, or just end up in-house?
If the patch is against CVS head, it's likely to be accepted.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Would those be appreciated, or just end up in-house?
Lund
Alan DeKok wrote:
Jorgen Lundman wrote:
Is it possible to also store the NAS IPs in LDAP, so changes can be done
centrally?
Not without source code patches.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http
Jorgen Lundman wrote:
> Is it possible to also store the NAS IPs in LDAP, so changes can be done
> centrally?
Not without source code patches.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
list of NAS IPs
that is allowed to talk to us, and for which services. Plus this need to
be synchronised with all Radius servers.
Is it possible to also store the NAS IPs in LDAP, so changes can be done
centrally? At the moment they are listed clients.conf.
Lund
--
Jorgen Lundman
7 matches
Mail list logo