Alan DeKok <aland@deployingradius.com> wrote Wed, 22 Oct 2014 10:43:04 -0400: | When radsecproxy sends a CHAP-Password, it should check for the | existence of a CHAP-Challenge attribute. If that attribute doesn't | exist, it should create a CHAP-Challenge attribute, and copy the | Authenticator field from the input packet into the attribute. This has been fixed in upcoming radsecproxy-1.6.6. Thank you Alan for the analysis and for making me aware of the issue. Thank you anoop for testing radsecproxy.