RE: Freeradius and Microsoft NPS

2011-04-13 Thread Doty, Seth
@lists.freeradius.org [freeradius-users-bounces+seth.doty=nebraska@lists.freeradius.org] On Behalf Of Phil Mayers [p.may...@imperial.ac.uk] Sent: Tuesday, April 12, 2011 5:07 PM To: freeradius-users@lists.freeradius.org Subject: Re: Freeradius and Microsoft NPS On 04/12/2011 07:32 PM, Doty, Seth wrote

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Alan DeKok
Doty, Seth wrote: ok this should look better See commit 4dbb466b6526c0dacdcf36949bbdaa38416a1be2 on git.freeradius.org. Grab the v2.1.x branch, it should be fixed there. We should release 2.1.11 soon. Alan DeKok. - List info/subscribe/unsubscribe? See

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Phil Mayers
On 13/04/11 14:16, Alan DeKok wrote: Doty, Seth wrote: ok this should look better See commit 4dbb466b6526c0dacdcf36949bbdaa38416a1be2 on git.freeradius.org. Grab the v2.1.x branch, it should be fixed there. Actually, I was just testing this and proxying the inner EAP-MSCHAPv2 as

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Phil Mayers
On 13/04/11 16:01, Phil Mayers wrote: On 13/04/11 14:16, Alan DeKok wrote: Doty, Seth wrote: ok this should look better See commit 4dbb466b6526c0dacdcf36949bbdaa38416a1be2 on git.freeradius.org. Grab the v2.1.x branch, it should be fixed there. Actually, I was just testing this and

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Alan DeKok
Phil Mayers wrote: Sigh. I can't even build old version of the server any more; libtool really is a crock of s**t. I'm looking to get rid of libtool libltdl entirely for 3.0. At this point, every major OS has dlopen(). And libtool is just ridiculous. 99.9% of systems use GCC, so libtool

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Alan DeKok
Phil Mayers wrote: Actually, I was just testing this and proxying the inner EAP-MSCHAPv2 as plain MS-CHAPv2 seems to be broken, at least in my testing. It doesn't crash the server, but equally it doesn't pass the S=XXX success back correctly either, so the client does a PEAP reject. Hmm...

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Phil Mayers
On 13/04/11 16:22, Alan DeKok wrote: Phil Mayers wrote: Actually, I was just testing this and proxying the inner EAP-MSCHAPv2 as plain MS-CHAPv2 seems to be broken, at least in my testing. It doesn't crash the server, but equally it doesn't pass the S=XXX success back correctly either, so the

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Phil Mayers
On 13/04/11 16:32, Phil Mayers wrote: On 13/04/11 16:22, Alan DeKok wrote: Phil Mayers wrote: Actually, I was just testing this and proxying the inner EAP-MSCHAPv2 as plain MS-CHAPv2 seems to be broken, at least in my testing. It doesn't crash the server, but equally it doesn't pass the S=XXX

Re: Freeradius and Microsoft NPS

2011-04-13 Thread Alan DeKok
Phil Mayers wrote: Actually, scratch that. Proxying in those versions doesn't work for me at all: ERROR: Failed to create a new socket for proxying requests. ERROR: Failed inserting request into proxy hash. ERROR: Failed to proxy request 7 ...I'm baffled as to what I'm doing wrong, but

Re: Freeradius and Microsoft NPS

2011-04-12 Thread Phil Mayers
On 12/04/11 16:34, Doty, Seth wrote: I couldn't find anything in the archives with this error and i am fairly new to freeradius config anyway so i thought this would be a good start. We are looking to authenticate wireless users through freeradius and Microsoft NPS. Our outer authentication is

RE: Freeradius and Microsoft NPS

2011-04-12 Thread Doty, Seth
-users-bounces+seth.doty=nebraska@lists.freeradius.org] On Behalf Of Phil Mayers [p.may...@imperial.ac.uk] Sent: Tuesday, April 12, 2011 12:00 PM To: freeradius-users@lists.freeradius.org Subject: Re: Freeradius and Microsoft NPS On 12/04/11 16:34, Doty, Seth wrote: I couldn't find anything

Re: Freeradius and Microsoft NPS

2011-04-12 Thread Phil Mayers
On 04/12/2011 07:32 PM, Doty, Seth wrote: The box is fedora 14 with freeradius from the repos. This the the output of the gdb log flle: Can you install the freeradius-debuginfo RPM and do this again; the backtrace is partial/mangled. It looks like it may be dying in request_free in