linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Humfrey <njh@aelius.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Configuring pppd to accept link-local IPv6 interface id from remote peer
Date: Sat, 20 Feb 2021 01:13:02 +0000	[thread overview]
Message-ID: <28d6f815-4e98-a4c4-ec53-55803669d7a7@aelius.com> (raw)
In-Reply-To: <d529e496-ac5f-9498-0e3d-1fa1ec2c4750@aelius.com>


>> Looking at the git master branch, it looks like Pali Rohár is actively
>> working in this space:
>>
>> https://github.com/paulusmack/ppp/commits/master
> Well, I'll give a look to find what's wrong.


Just a quick follow up to say that it is all working fine after I 
upgraded to version 2.4.9 of pppd.

I had initially been using version 2.4.7, that came with Raspberry Pi OS 
(buster).
I had also been testing using git master of the ppp repo on the 'client'.

But I hadn't tried upgrading the 'server' (the peer configured with the 
interface identifiers).
After upgrading to 2.4.9 on the 'server' it works perfectly - even with 
an older version of pppd on the 'client'.
I haven't tracked down the commit that fixed it but I guess it was 
something to do with failing to Nack the random interface identifier 
sent by the peer.

Thank you for your help and thoughts on the issue.


nick.


|pppd file ./ppp-options ipv6cp-accept-local /dev/ttyAMA0 115200 using 
channel 368 Using interface ppp0 Connect: ppp0 <--> /dev/ttyAMA0 sent 
[LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x7f793cbe>] rcvd [LCP ConfReq 
id=0xb <asyncmap 0x0> <magic 0xecde7250>] sent [LCP ConfAck id=0xb 
<asyncmap 0x0> <magic 0xecde7250>] rcvd [LCP ConfReq id=0xb <asyncmap 
0x0> <magic 0xecde7250>] sent [LCP ConfAck id=0xb <asyncmap 0x0> <magic 
0xecde7250>] rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x7f793cbe>] 
sent [LCP EchoReq id=0x0 magic=0x7f793cbe] sent [IPV6CP ConfReq id=0x1 
<addr fe80::0dfd:3c3b:e130:91ce>] rcvd [LCP EchoReq id=0x0 
magic=0xecde7250] sent [LCP EchoRep id=0x0 magic=0x7f793cbe] rcvd [LCP 
EchoRep id=0x0 magic=0xecde7250] rcvd [IPV6CP ConfReq id=0xb <addr 
fe80::0000:0000:0000:0001>] sent [IPV6CP ConfAck id=0xb <addr 
fe80::0000:0000:0000:0001>] rcvd [IPV6CP ConfNak id=0x1 <addr 
fe80::0000:0000:0000:0002>] sent [IPV6CP ConfReq id=0x2 <addr 
fe80::0000:0000:0000:0002>] rcvd [IPV6CP ConfAck id=0x2 <addr 
fe80::0000:0000:0000:0002>] local LL address fe80::0000:0000:0000:0002 
remote LL address fe80::0000:0000:0000:0001 Script /etc/ppp/ipv6-up 
started (pid 7049) Script /etc/ppp/ipv6-up finished (pid 7049), status = 
0x0 |


      parent reply	other threads:[~2021-02-20  1:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14  1:03 Nicholas Humfrey
2021-02-14  1:57 ` Michael Richardson
2021-02-14 13:42 ` Nicholas Humfrey
2021-02-14 16:23 ` James Carlson
2021-02-14 17:07 ` Kurt Van Dijck
2021-02-14 17:50 ` James Carlson
2021-02-14 21:24 ` Benjamin Cama
2021-02-14 22:46 ` James Carlson
2021-02-14 23:15 ` Benjamin Cama
2021-02-16  0:10 ` Nicholas Humfrey
2021-02-16 10:04 ` Benjamin Cama
2021-02-18  0:18 ` Nicholas Humfrey
2021-02-20  1:13 ` Nicholas Humfrey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28d6f815-4e98-a4c4-ec53-55803669d7a7@aelius.com \
    --to=njh@aelius.com \
    --cc=linux-ppp@vger.kernel.org \
    --subject='Re: Configuring pppd to accept link-local IPv6 interface id from remote peer' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).