Hi,

YASUOKA Masahiko wrote:
Hi,

On Tue, 07 May 2013 22:38:46 +0100
Joe Holden <[email protected]> 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:

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
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 ACFC message appears when blindly forwarded also, but then the next message is the expected one:

2013-05-08 12:24:04:INFO: ppp id=0 layer=lcp logtype=Opened mru=1400/1480 auth=MS-CHAP-V2 magic=9d8d641c/77831e4b

This is on a test setup currently, but mirrors the behaviour as it
would see on a real network.

If I blindly switch to npppd all is well, I've got l2tp-lcp-reneg
enabled but it doesn't seem to make any difference, likewise with
force.

Is this known behaviour or am I missing something?

Does the config

  l2tp-accept-dialin yes

line in the `tunnel' config?

I've got that in the config yes:

        listen on 0.0.0.0
        tcp-mss-adjust yes
        pipex yes
        authentication-method pap chap mschapv2
        l2tp-lcp-renegotiation yes
        l2tp-force-lcp-renegotiation yes
        l2tp-accept-dialin yes

--yasuoka


Thanks

Reply via email to