error of segmentation during the implementation of eap2

arnauld ndefo ndefo2002 at
Wed Sep 19 01:11:22 CEST 2012

We dont know how to use the git pull command that you have sent to us. Then to fix the error of segmentation, we have just removed in the authorize section of the default and innet-tunnel file the part eap2 { ok=return}. We have not used the patch that you have recommand.

We have done in the freeradius-server directory the command git pull / git repository   and we have got nothing. 

I you have some suggestion to know how to Confirm that your git repository head is at commit 02567cf3c5aa758d7153c0bd7020e27a5067f7c3 (git pull), please tell us.
Thank you

 De : Arran Cudbard-Bell <a.cudbardb at>
À : arnauld ndefo <ndefo2002 at> 
Cc : FreeRadius users mailing list <freeradius-users at> 
Envoyé le : Mercredi 19 septembre 2012 0h06
Objet : Re: error of segmentation during the implementation of eap2

As Alan B just said, radtest does not send EAP packets, no matter where you send the RADIUS packets, to the inner tunnel or the outer tunnel, radtest doesn't send EAP-Message.

You have hardcoded auth-type eap2 in your users file, so when the request enters the authenticate section, the eap2 module is called instead of the PAP module.

The EAP module says, WTH dude why am I being called when there's no EAP-message, and the server sends back a reject.

I can't remember if the eap2 module has the code to check for eap-message and set the appropriate Auth-Type, and i'm not going to check, because you still haven't confirmed whether that patch fixed the segfault or not. Grrr.

Instead of the users file entry, do something like

authorize {
if (EAP-Message) {
>update control {
>Auth-Type := eap2

And please stop CCing everyone, mailman is smart enough not to send send duplicates, but it's still annoying.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Freeradius-Users mailing list