Proxying PEAP/MSCHAPv2 to NPS errors

[Seth Lampman]

It's a VM and my third one I have created so I am not sure it would be the
memory?  I am currently using Ubuntu would trying another OS be of any help?

I don't always get the mutex, 99% of the time I get segmentation fault.

Where do I find docs/bugs?  Forgive the noob question but I have looked all
over and cant seem to find anything

-----Original Message-----
From: freeradius-users-bounces+sethklampman=gmail.com at lists.freeradius.org
[mailto:freeradius-users-bounces+sethklampman=gmail.com at lists.freeradius.org
] On Behalf Of Alan DeKok
Sent: Monday, November 19, 2012 11:30 AM
To: FreeRadius users mailing list
Subject: Re: Proxying PEAP/MSCHAPv2 to NPS errors

Seth Lampman wrote:
> I am trying to take an PEAP/MSCHAPv2 tunnel terminate it at 172.16.0.9 
> and then proxy it as MSCHAPv2 to an NPS server at 172.16.0.15.  This 
> is for a token server that does not allow PEAP.  Everything works (I 
> get an ACCEPT from 172.16.0.15) but then freeradius crashes.  I have 
> searched the forumns and it looks like others have had this issue but 
> I can seem to find a resolution.  Sometimes I get the mutex lock and 
> sometimes I get a segmentation fault.

  See doc/bugs

> freeradius: pthread_mutex_lock.c:321: __pthread_mutex_lock_full:
> Assertion `robust || (oldval & 0x40000000) == 0' failed.

  That's... bad.  Mutexes dying are very bad.  At least it's not in the
FreeRADIUS code.

  I'd suggest running a memory checker on the machine.  Odds are that the
memory is bad.

  Alan DeKok.
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html