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 this 'radiusClientIPAddress' (RADIUS attribute 'Client-IP-Address')?
Quoting Turbo Fredriksson [EMAIL PROTECTED]:
Is there any documentation of the attributes in the LDAP
schema?
I'm trying to write a GUI manager for RADIUS (actually a
'plugin' to my http://phpQLAdmin.com) but I don't know
how to write the lead text to the form...
Cross referencing
Is there any documentation of the attributes in the LDAP
schema?
I'm trying to write a GUI manager for RADIUS (actually a
'plugin' to my http://phpQLAdmin.com) but I don't know
how to write the lead text to the form...
I took a look at the schema in 1.1.7, but that don't
have any comments or
Quoting Rakesh Jha [EMAIL PROTECTED]:
Using ntlm_auth I can test user authentication.
Are you saying that ntlm_auth tests work?
When I do following -
radtest ActDirectUser ActDirectUserPassword 127.0.0.1 1812 testing123
As said before, output from 'freeradius -X' is necessary for
anyone
Quoting [EMAIL PROTECTED] [EMAIL PROTECTED]:
can any one please tell me where can i get radius client for radius server
suitable to Red Hat Enterprise Linux ES 3.
Try searching for one at http://freshmeat.net/. Looking there myself, shows
12 projects (at least two of them are clients).
Also
Quoting Rakesh Jha [EMAIL PROTECTED]:
I'm far from an expert in FreeRADIUS (so take what I say with a
grane of salt), but I instantly noticed this.
tls: private_key_file = /usr/local/etc/raddb/certs/cert-srv.pem
tls: certificate_file = /usr/local/etc/raddb/certs/cert-srv.pem
tls: CA_file =
Quoting Phil Mayers [EMAIL PROTECTED]:
2) INNER Auth part ensures that the ldap module is only called for the
INNER part of the check...not for everything else. also very very useful
as it stops outer ID junk and debris from being checked.
What IS 'the INNER part' (may depend on the
Quoting Phil Mayers [EMAIL PROTECTED]:
DEFAULT FreeRadius-Proxied-To == 127.0.0.1, Autz-Type := INNER
1) proxy part makes sure that only INNER is called when its proxied to
127.0.0.1
Ok, think I got this. Does it matter WHERE in the file this DEFAULT is?
And is the keyword 'INNER'
I'm working on fine tuning my radiusd.conf file, and found that
I get 13 authorize request to the LDAP server for one XXX (client,
request, logon?!).
I have 802.1x (RADIUS) enabled on my WiFi router, and when requesting
a network on my client, there's 13 authorize requests... Using multilog
which
Quoting Phil Mayers [EMAIL PROTECTED]:
On Wed, 2007-08-22 at 19:29 +0200, Turbo Fredriksson wrote:
I'm working on fine tuning my radiusd.conf file, and found that
I get 13 authorize request to the LDAP server for one XXX (client,
request, logon?!).
You can reduce this somewhat by doing
[EMAIL PROTECTED] writes:
If I understand you well, passwords in LDAP are encrypted, so
PEAP won't work. And you want to keep them that way. Your only
option is to use SecureW2 and EAP-TTLS-PAP.
Or do as I managed to get it working yesterday - put a Samba server
in between.
11 matches
Mail list logo