Project

General

Profile

Actions

Bug #11431

closed

WAN IPv6 via Prefix Delegation over PPPoE

Added by Jost Schoenleben about 3 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv6)
Target version:
-
Start date:
02/17/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:
All

Description

Hello,

the following wan setup is working with my provider.
WAN:
  • IPv4 Configuration Type PPPoE
  • IPv6 Configuration Type DHCP6
  • Request a IPv6 Prefix through the ipv6 connectivity link
  • Only request an IPv6 prefix, do not request an IPv6 address
    LAN:
  • LAN IPv6 Configuration Type Track Interface (WAN)
    I get a prefix and the pfsense generates a suitable LAN IP.

My provider only supports ia_pd and not ia_na for DHCP6. So i do not have an IPv6 WAN IP.
Cisco, OneAccess or AVM Fritzbox routers can also generate a IPv6 WAN IP from the delegated prefix.
On pfsense it does not work. I guess it tries to generate an IPv6 address using the mac address (hwaddr), but that does not exist on the pppoe0 interface.

[2.4.5-RELEASE][]/var/etc: ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 90:1b:0e:14:ec:c6
hwaddr 90:1b:0e:14:ec:c6
inet6 fe80::921b:eff:fe14:ecc6%em0 prefixlen 64 scopeid 0x1
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
ether 50:3e:aa:16:2c:b5
hwaddr 50:3e:aa:16:2c:b5
inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::1:1%re0 prefixlen 64 scopeid 0x2
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
enc0: flags=0<> metric 0 mtu 1536
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: enc
pfsync0: flags=0<> metric 0 mtu 1500
groups: pfsync
pflog0: flags=100<PROMISC> metric 0 mtu 33160
groups: pflog
pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492
inet 80.81.2.247 --> 82.135.16.28 netmask 0xffffffff
inet6 fe80::921b:eff:fe14:ecc6%pppoe0 prefixlen 64 scopeid 0x7
inet6 fe80::523e:aaff:fe16:2cb5%pppoe0 prefixlen 64 scopeid 0x7
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>

[2.4.5-RELEASE][]/var/etc: cat dhcp6c_wan.conf
interface pppoe0 {
send ia-pd 0;
request domain-name-servers;
request domain-name;
script "/var/etc/dhcp6c_wan_script.sh";
};
id-assoc pd 0 {
prefix-interface pppoe0 {
sla-id 0;
sla-len 16;
};
};

[2.4.5-RELEASE][]/var/etc: clog /var/log/dhcpd.log | grep dhcp6c | tail -n6
Feb 17 14:47:25 pfSense dhcp6c56807: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Feb 17 14:47:25 pfSense dhcp6c56807: failed initialize control message authentication
Feb 17 14:47:25 pfSense dhcp6c56807: skip opening control port
Feb 17 14:47:25 pfSense dhcp6c56807: link layer address is too short (pppoe0)
Feb 17 14:47:25 pfSense dhcp6c56807: failed to get default IF ID for pppoe0
Feb 17 14:47:25 pfSense dhcp6c56807: failed to parse configuration file

If it is not possible to have a hwaddr on pppoe0, then maybe it would be possible to manually set an ipv6 interface identifier.
This is would also be a cool feature for the LAN interface.

Cisco also supports this:
interface Vlan1
ipv6 address prefix-from-provider ::1:0:0:0:1/64
Or like this:
interface Vlan1
ipv6 address prefix-from-provider ::1/64

https://www.cisco.com/c/de_de/support/docs/ip/ip-version-6-ipv6/113141-DHCPv6-00.html

Kind regards,
Jost

Actions #1

Updated by Jim Pingle about 3 years ago

  • Status changed from New to Rejected

There were numerous improvements in IPv6 on PPPoE in 2.5.0 which was just released. If you can still replicate this problem there, open a new issue with a more specific focus on exactly what change is needed. It's difficult to tell from this exactly what you are proposing other than maybe a manual ID (which is buried way at the end).

Actions

Also available in: Atom PDF