I bugged this: http://bugs.freeradius.org/show_bug.cgi?id=73.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Segmentation Fault on LDAP Bind
At the moment, I am using freeradius-snapshot-20040516 on Fedora Core 2.
I use freeradius to authenticate and authorize WLAN clients that use
802.1x or WPA. As a result, I have configured freeradius to do PEAP.
With users configured in the users file, everything works
I would love to hear your results.
I have compiled it with both gcc 3.3.3 (gcc version 3.3.3 20040412 (Red
Hat Linux 3.3.3-7)) and gcc 3.4.0 (gcc version 3.4.0 20040519 (Red Hat
Linux 3.4.0-2)). In both cases, I get a segmentation fault.
I spent a little time trying to get it to core dump, but
On Mon, 2004-05-24 at 08:50 -0700, Paul Bender wrote:
I would love to hear your results.
I have compiled it with both gcc 3.3.3 (gcc version 3.3.3 20040412 (Red
Hat Linux 3.3.3-7)) and gcc 3.4.0 (gcc version 3.4.0 20040519 (Red Hat
Linux 3.4.0-2)). In both cases, I get a segmentation
]
Subject: Re: Freeradius Segmentation Fault on LDAP Bind
I would love to hear your results.
I have compiled it with both gcc 3.3.3 (gcc version 3.3.3 20040412 (Red
Hat Linux 3.3.3-7)) and gcc 3.4.0 (gcc version 3.4.0 20040519 (Red Hat
Linux 3.4.0-2)). In both cases, I get a segmentation fault.
I spent
Message-
From: Paul Bender [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 4:17 PM
To: [EMAIL PROTECTED]
Subject: Re: Freeradius Segmentation Fault on LDAP Bind
Thanks for the info.
Do you know what interaction between FreeRADIUS and OpenLDAP is
triggering this problem? I ask because Red
Alan DeKok wrote:
Paul Bender [EMAIL PROTECTED] wrote:
I do not believe I am using TLS (or SSL) to connect to the LDAP server,
since I have set start_tls=0 in my ldap module configuration and since
freeradius is attempting to connect to the ldap (not the ldaps) port.
See doc/bugs for details
Paul Bender [EMAIL PROTECTED] wrote:
I do not believe I am using TLS (or SSL) to connect to the LDAP server,
since I have set start_tls=0 in my ldap module configuration and since
freeradius is attempting to connect to the ldap (not the ldaps) port.
See doc/bugs for details on more
Paul Bender [EMAIL PROTECTED] wrote:
However, I use OpenLDAP as a central store for account information for
all other services (unix, samba, email, etc). Therefore, I would like
freeradius to get account information from the LDAP server as well.
However, when I configure freeradius to use
Alan DeKok wrote:
Paul Bender [EMAIL PROTECTED] wrote:
However, I use OpenLDAP as a central store for account information for
all other services (unix, samba, email, etc). Therefore, I would like
freeradius to get account information from the LDAP server as well.
However, when I configure
At the moment, I am using freeradius-snapshot-20040516 on Fedora Core 2.
I use freeradius to authenticate and authorize WLAN clients that use
802.1x or WPA. As a result, I have configured freeradius to do PEAP.
With users configured in the users file, everything works fine.
However, I use
While attempting to do an ldap bind FreeRadius seg faulted.
Can anyone help ? Has anyone else seen this ?
Thanks,
Ron.
modcall[authorize]: module backslash returns
noop for request 5
rlm_realm: Request already proxied.
Ignoring.
modcall[authorize]: module realmpercent
Looks like its a problem when FR
tries to talk on port 636 SSL to an ldap server.
-Original Message-
From: Ron Wahler
Sent: Friday, March 05, 2004 11:50
AM
To:
[EMAIL PROTECTED]
Subject: Snapshot 226 of
FreeRadius - Segmentation fault on ldap bind
While attempting
13 matches
Mail list logo
