Help with IPv6 PPPoE SLAAC and DHCP PD
-
Hi,
My ISP is using SLAAC for WAN and DHCP PD for LAN IPv6. However when I choose SLAAC for WAN connection, there is no option to configure DHCP PD for LAN. In addition, I can not configure DHCPv6 server/RA because this option require static IPv6.
-
Choose DHCP6 and configure it for Prefix Delegation only. You will get an IPv6 address for your WAN interface via SLAAC if your ISP supports SLAAC.
If you are using PPPoE for your WAN, you might find the patch I posted yesterday in the IPv6 forum to be helpful.
-
Thank David. IPv6 WAN is up, IPv6 LAN is ok as well. But I notice that Router Advertisement Daemon, OpenVPN servers are down. I already applied your patch.
-
Choose DHCP6 and configure it for Prefix Delegation only. You will get an IPv6 address for your WAN interface via SLAAC if your ISP supports SLAAC.
If you are using PPPoE for your WAN, you might find the patch I posted yesterday in the IPv6 forum to be helpful.
Did you need to use that patch for your Zen connection or is it only a problem with certain ISPs implementations?
I still haven't got mine working for IPv6 although I'm fairly convinced its a problem their-end, as it wont work on their supplied router either.
-
Choose DHCP6 and configure it for Prefix Delegation only. You will get an IPv6 address for your WAN interface via SLAAC if your ISP supports SLAAC.
If you are using PPPoE for your WAN, you might find the patch I posted yesterday in the IPv6 forum to be helpful.
Did you need to use that patch for your Zen connection or is it only a problem with certain ISPs implementations?
That patch addresses two issues in pfSense.
Firstly, the interface ID is usually random on the first connection after boot. When SLAAC is in use, as in Zen's IPv6 implementation, this leads to a random lower 64 bits of the WAN IPv6 address. The patch is imperfect, as it does not result in the same interface identifier following a disconnect and reconnect, though I will address that in time and update the patch.
Secondly, it prevents dhcp6c from being started twice on the same connection, which results in significant brokenness when it occurs. This issue seems to affect a relatively small number of people using 2.2.5 and 2.2.6, but it needed addressing. I haven't personally experienced this issue, but it's something of a show stopper for those affected by it.