linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-ppp@vger.kernel.org
Subject: Re: IPv6 with pppd
Date: Wed, 26 Jun 2019 15:28:20 +0000	[thread overview]
Message-ID: <9745.1561562900@localhost> (raw)
In-Reply-To: <CACwWb3B6v7ayhoDpE-GAA8qKgbh=EM95eq9hHxHcZtusAaQqcw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2420 bytes --]


Levente <leventelist@gmail.com> wrote:
    > I am struggling with IPv6 over PPP on Linux. The situation is that I
    > have a 3G modem, when I plug it in to the USB on my Debian box,
    > everything works as expected, I have IPv6 address from the provider,
    > and I am happy. But how?

...

    > Please note that in the logs, I can't see that global scope address,
    > and I don't know how the IPv6CP assigns this address to the interface.
    > How is this done?

IPv6CP does not.
The major difference between IPCP and IPv6CP is that it was realized that in
IPv4, the IPCP people were having to repeat all the DHCPv4 work again in
IPCP, and why not just run DHCP?

So in IPv6CP, *ALL* IPv6CP does it assign the LL address (which are either
made up randomly, or come from an IID/EUI/OUI of a physical interface).

Then, an IPv6 RS/RA occurs, which MAY assign an address (M=0), or MAY
suggest using DHCPv6 (M=1).  My experience is that many devices do both,
and one winds up with two addresses.

If DHCPv6-PD also occurs (O=1), then there is actually no reason to even
number the PPP link with a GUA, as one can just use a GUA from an downstream
interface.

In my copious spare time, I hope to write an RFC updating 7084 that provides
a way for the ISP to understand what the CPE device would like, such that the
ISP does not have to deal with all the situations of single-device-with-/64,
single-device-that-may-tether-with-/64, WAN-link-numbered+PD, or
WAN-link-unnumbered+PD.  There are scaling efficiencies for the ISP in the size of
it's access network routing table if each customer costs a single TCAM slot
rather than two, sometimes three.

    > And when I plug the same modem to an OpenWRT box, I don't get the
    > global scope address, only the link-local address. Is this some PPP
    > specific problem, or there might be some IPv6 autoconfiguration magic
    > happening in the background? I don't think so, because that address
    > corresponds to a statically allocated address of the provider.

I assume PPPoE, and modem is DSL or CableModem (not dialup).
What version of OpenWRT?  18.06 just works!

Feel free to unicast me your /etc/config/network

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      parent reply	other threads:[~2019-06-26 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 11:30 Levente
2019-06-26 12:45 ` James Carlson
2019-06-26 14:43 ` Levente
2019-06-26 15:28 ` Michael Richardson [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=9745.1561562900@localhost \
    --to=mcr@sandelman.ca \
    --cc=linux-ppp@vger.kernel.org \
    --subject='Re: IPv6 with pppd' \
    /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).