Josh Howlett wrote:

...

>> Sending Access-Challenge of id 3 to x.x.x.x port 1812

>> MS-CHAP2-Success =

...

>> EAP-Message =

...

> That looks like a bug to me. It's a violation of RFC2548:

No. The bug is different: EAP-MSCHAPv2 is *not* MS-CHAPv2.

The MS-CHAP2-Success attribute has no business being in *any* packet that also contains EAP.

I've committed a fix for that to CVS head.

>>How and when do I get this fix

>> Also does thi fix the reply as type Access-Accept instead of Access-challenge

Alan DeKok.

List info/subscribe/unsubscribe? See