@dsummers Do you have a section in your config for router-advert? I'm still struggling to get my Comcast business connection to delegate me an ipv6 prefix and then to have that be routable (my local interface gets a /63... wtf?!)

Richardpowellus: I may be running into the same issue. What does your
id-assoc pd 2 { } section look like?

I'll be building an image and testing this out today. Thanks Jack!

I've turned off the IPv6 firewall, and run tcpdumps on my LAN and WAN interfaces (eth1 and eth0, respectively). I see loads of tcp retransmissions, and all my icmpv6 requests have an error message of 'no response found!' in the Wireshark output.

Oh, and one final question: you don't have a static IPv4 address, do you? Just trying to sort out any possibilities.

I haven't made any 'Apply changes' to the modem and unfortunately it still won't forward my IPv6 traffic. You don't happen to have a firewall rule handy for being extremely permissive with IPv6 outgoing traffic, do you?

The commit failed and had to be ctrl+C'd. However, delete interfaces ethernet eth1 address dhcpv6; commit; then a second commit making the dhcpv6-pd changes work. So instead of the single step working, it had to be broken into two.

Rebooted the router and configured following your instructions and got assigned an IPv6 address on my LAN interface! I'd never managed to get this far with pfSense (I could only get it to assign me addresses on the external interface) or on EdgeOS (probably over a year ago). Thanks so much!

You wouldn't happen to be on Comcast, would you? The supposed-/56 that's offered when instead it's a /60 is a behavior I'm familiar with on Comcast.

In T421#33183, @gadams wrote:

I've learned a lot about building ISO images over the past couple weeks. I have a first version of my change ready; it's in two commits currently:

https://github.com/gsadams/vyos-1x/commit/9dc320b026d29e1c6e290346b8be53a6f5a74a11
and
https://github.com/gsadams/vyatta-cfg-system/commit/5c1900015fe5f0c65810bdbbefa0c61cd118cc6d

and also likely requires the fix I proposed in T1059 (which appears not to have been merged, yet), depending on your particular configuration.

If you'd like to test it, I have built an image from the latest Crux branch plus those three changes, here: http://www.avernus.com/~gadams/vyos-crux.201902250834.dhcpv6pd-amd64.iso

I'm currently running that image, myself. It'd be nice if anyone who wants to get DHCPv6-PD working could give it a try and let me know whether it works for you, what you think of the config syntax, or anything glaring that it's missing. The configuration syntax is basically what I described up above. You'll need to enable the DHCPv6 client on the appropriate interface (the one connected to your ISP, presumably), and specify how you want the delegated prefix farmed out to other interfaces.

One known limitation is that the DHCPv6-PD configuration can currently only be applied to an ethernet interface. That's not because of any technical limitation; it's just that applying it to other interfaces will require copying a bunch of files, so I thought I'd try to get it right in one place, first.