Description of problem: Radiusclient use incorrect AccessRequest for mschap and mschap-v2 protocol to authenticate against Radius Server. But old versions working fine. Version-Release number of selected component (if applicable): radiusclient-ng-0.5.2 How reproducible: Cannot use MS-CHAP or MS-CHAP-V2 protocol to authenticate user. Other protocols (PAP and CHAP) working correct. Steps to Reproduce: 1. Try to authenticate with ms-chap protocol Actual results: Dump of packet by freeradius: Packet-Type = Access-Request Service-Type = Framed-User Framed-Protocol = PPP User-Name = "dicr" NAS-IP-Address = 127.0.0.1 NAS-Port = 1 Client-IP-Address = 127.0.0.1 This is incorrect, because there no MS-Chap-Challenge attribute for MS-CHAP request. Expected results: Old version libradiusclient 0.3.1 work fine with the next packet dump: Packet-Type = Access-Request Service-Type = Framed-User Framed-Protocol = PPP User-Name = "dicr" MS-CHAP-Challenge = 0x1e9cc0ca7c6a1e9e4bb40c89fc2142ff MS-CHAP2-Response = 0x3d0092321c3e61197fdc418e730691cc350f0000000000000000ac9d910a28c5b9b839e9afa798919ad3b7d0be59a52e15e8 NAS-IP-Address = 127.0.0.1 NAS-Port = 1 Client-IP-Address = 127.0.0.1 Additional info: With PAP and CHAP protocol it working fine, including UserPassword or ChapChallenge and ChapPassword attributes, but MS-CHAP request is malformed and not correct. Freeradius say "No UserPassword attribute" and refuse authentication, but with old version libradiusclient all working fine..
*** Bug 241294 has been marked as a duplicate of this bug. ***
I've updated the radiusclient-ng packages to 0.5.5.1 plus a couple of patches that were in the upstreams CVS. If the new packages don't fix the problem you'll need to work with the upstream developers to figure out a solution to the problem.
Since I haven't seen a reply I'm going to assume that the problem was fixed and close this bug. Reopen if the bug if you are still having problems.
nothing change after update to 0.5.5.1 bugreport was posted to upstream developers too.
Please put a link to the upstream bugreport in a comment, so that anyone else that encounters this bug can follow the upstream work.
Nevermind, I found the report... http://developer.berlios.de/bugs/?func=detailbug&bug_id=11175&group_id=1208
radiusclient-ng has been at version 0.5.6 for a while, and the upstream bug hasn't been updated. I'm going to close this bug for now until upstream can provide a fix.