On Wed, 08 May 2013 12:32:16 +0100 Joe Holden <li...@rewt.org.uk> wrote: > YASUOKA Masahiko wrote: >> On Tue, 07 May 2013 22:38:46 +0100 >> Joe Holden <li...@rewt.org.uk> wrote: >>> I'm testing out npppd as a termination device which is being fed from >>> existing LACs (in this particular setup, mpd on FreeBSD) - if the LAC >>> begins LCP to challenge the client for it's username in order to >>> lookup the destination LNS, npppd just repeats the following until it >>> gives up:
In this case, npppd assumes the LAC is using "Proxy LCP and Authentication" AVP in RFC 2661. >>> 2013-05-07 22:29:03:INFO: ppp id=1 layer=chap proto=unknown Received >>> chap packet. But chap is not started >>> 2013-05-07 22:29:05:INFO: ppp id=1 layer=chap proto=unknown Received >>> chap packet. But chap is not started >> Do you have the "dialin-proxy" message before these messages? If you >> have, I would like to see it. >> > The only message ppp related prior to those is: > > 2013-05-08 12:21:07:INFO: l2tpd ctrl=1 call=3490 RecvICCN > session_id=5644 calling_number= tx_conn_speed=10000000 framing=sync > 2013-05-08 12:21:07:NOTICE: l2tpd ctrl=1 call=3490 logtype=PPPBind > ppp=0 Those AVPs don't seem to be requested by the LAC. > 2013-05-08 12:21:07:INFO: ppp id=0 layer=base logtype=Started > tunnel=L2TP_ipv4(172.16.10.57:54189) > 2013-05-08 12:21:07:INFO: l2tpd ctrl=1 call=3490 SendZLB > 2013-05-08 12:21:08:INFO: ppp id=0 layer=base ppp_recv_packet: Rcvd > broken frame. ACFC is not accepted, but received ppp frame that has > no address. > 2013-05-08 12:21:08:INFO: ppp id=0 layer=chap proto=unknown Received > chap packet. But chap is not started The LAC seems to be starting CHAP without LCP. The problem seems to be come from the LAC. If mpd has settings about "proxy LCP and authentication", I would like you to try them. --yasuoka
