Does anyone happen to have a working configuration using Debian pppd to connect to Zen Internet in the UK with working IPv6? It looks like IPv6 is expected to run over the IPv4 PPPoE connection. IPv4 is all working fine.
I added:
+ipv6 ipv6cp-use-ipaddr
to the provider file in /etc/ppp/peers and the pppd output looks promising:
Apr 1 13:33:27 deneb pppd[117669]: rcvd [IPV6CP ConfReq id=0x1a <addr fe80::827f:f8ff:fe74:b4f3>]
Apr 1 13:33:27 deneb pppd[117669]: sent [IPV6CP ConfAck id=0x1a <addr fe80::827f:f8ff:fe74:b4f3>]
[...]
Apr 1 13:33:27 deneb pppd[117669]: rcvd [IPV6CP ConfAck id=0x1 <addr fe80::4147:9ae5:df4d:be66>]
Apr 1 13:33:27 deneb pppd[117669]: local LL address fe80::4147:9ae5:df4d:be66
Apr 1 13:33:27 deneb pppd[117669]: remote LL address fe80::827f:f8ff:fe74:b4f3
and I can ping the remote link-local address successfully. I see occasional router advertisements, but they have a reachable time of 0ms.
If I drop the "ipv6cp-use-ipaddr" then I get different link-local addresses for both the local and remote, but the router advertisements from the new remote still have a reachability time of 0ms.
I tried manually assigning an address from the WAN /64 that Zen gave me to the ppp interface and setting the default route to the remote link-local address, but I never got any responses from anything out on the real IPv6 Internet.
I'm starting to wonder whether Zen really did turn on IPv6 support on my
line correctly since I couldn't make it work with the router they sent me either.
Mike Crowe <mac@mcrowe.com> writes:
Does anyone happen to have a working configuration using Debian pppd to connect to Zen Internet in the UK with working IPv6? It looks like IPv6 is expected to run over the IPv4 PPPoE connection. IPv4 is all working fine.
The other end could be expecting you to use the negotiated interface-id
with that prefix. But I believe it's more likely that they expect you
to use DHCPv6 for address configuration. Did you try that? It's quite possible that they support DHCPv6-PD, assigning you a larger prefix.
8--
Finding good DHCPv6 clients with PPP support used to be difficult (the
one from ISC only worked on ethernet). I don't know the current status.
One would hope that modern network managers like systemd-networkd or NetworkManager just works...
On Saturday 01 April 2023 at 16:18:43 +0200, Bjørn Mork wrote:
Finding good DHCPv6 clients with PPP support used to be difficult (the
one from ISC only worked on ethernet). I don't know the current status. One would hope that modern network managers like systemd-networkd or NetworkManager just works...
I did try running ISC dhclient and that would explain my lack of success. I found mention of wide-dhcpv6-client, which appears to be in Debian, so I'll have a look at that and also maybe dhcpcd which seems to be rather better
in my experience.
Does anyone happen to have a working configuration using Debian pppd
to connect to Zen Internet in the UK with working IPv6? It looks like
IPv6 is expected to run over the IPv4 PPPoE connection. IPv4 is all
working fine.
Apr 1 13:33:27 deneb pppd[117669]: rcvd [IPV6CP ConfReq id=0x1a
<addr fe80::827f:f8ff:fe74:b4f3>] Apr 1 13:33:27 deneb pppd[117669]:
sent [IPV6CP ConfAck id=0x1a <addr fe80::827f:f8ff:fe74:b4f3>] [...]
Apr 1 13:33:27 deneb pppd[117669]: rcvd [IPV6CP ConfAck id=0x1 <addr fe80::4147:9ae5:df4d:be66>] Apr 1 13:33:27 deneb pppd[117669]: local
LL address fe80::4147:9ae5:df4d:be66 Apr 1 13:33:27 deneb
pppd[117669]: remote LL address fe80::827f:f8ff:fe74:b4f3
and I can ping the remote link-local address successfully. I see
occasional router advertisements, but they have a reachable time of
0ms.
Am 01.04.2023 um 15:38:59 Uhr schrieb Mike Crowe:
It looks like they use DHCPv6 to delegate the LAN prefix(es), but I'd (possibly incorrectly assumed) that this sentence from their email:
DHCPv6 prefix delegation is the next step, you need to configure the transport network first.
meant that I should expect to receive a RA with a /64 prefix for the
WAN interface address. (Earlier in the email is a /64 described as
the "ND prefix" along with a /48 described as the "delegation
prefix".)
That sounds common.
If they expected me to use DHCPv6 for this wouldn't they have set the
M bit in the RA?
True, does it appear?
Is the RA you received like they described it?
8--
You can use rdisc6 to manually send a solicitation to receive it.
8--
8--(I now notice that the sla-len is wrong, but I doubt that matters yet.)
Rather strangely, running rdisc6 does cause router solicitations to be
sent as would be expected, but they don't seem to provoke any
response.
Am 01.04.2023 um 19:45:03 Uhr schrieb Mike Crowe:
Rather strangely, running rdisc6 does cause router solicitations to be
sent as would be expected, but they don't seem to provoke any
response.
This is a fault. Tell that your ISP.
Judging by the ping time the Juniper router sending the router
advertisements is at the ISP rather than wherever the fibre terminates locally, so it's strange that this problem isn't affecting others.
Am 01.04.2023 um 19:45:03 Uhr schrieb Mike Crowe:
Rather strangely, running rdisc6 does cause router solicitations to be
sent as would be expected, but they don't seem to provoke any
response.
This is a fault. Tell that your ISP.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 299 |
Nodes: | 16 (2 / 14) |
Uptime: | 62:34:12 |
Calls: | 6,690 |
Files: | 12,226 |
Messages: | 5,345,580 |