Eugene Grosbein

So unless the client accepts our use of pap/chap at the lcp layer, then it wont make it to generating a radius request? It depends. Do you try to make split LAC/LNS configuration or mpd5 needs to serve users all by itself?

This log indicates exactly same problem: a client rejects to authorize itself with MS-CHAPv2. The client must be reconfigured to use MS-CHAPv2.

This log indicates extactly same problem: a client reject to authorize itself with MS-CHAPv2. The client must be reconfigured to use MS-CHAPv2.

Please do not cut the logs. We need full session log. Also, replace your "log +ALL -EVENTS -FRAME -ECHO +RADIUS +RADIUS2" with something like the following: log +auth +bund +iface +iface2 +ipcp +ipcp2 +link +lcp +lcp2 +rep

The log shows that client was not configured to use MS-CHAPv2 and rejected to used it while mpd5 server was configured to require MS-CHAPv2 (not PAP).

util.c: avoid usage of unneeded struct sockaddr_inarp

changes.sgml: elaborate latest change and move to Changes section

radius.c: cut all null bytes at start of RAD_MICROSOFT_MS_CHAP_ERROR msg