Cox → Re: Needing info to enable native IPv6

My thanks to both of you . I had it working at one point ( native IPv6 that is ) , but broke it , and didn't have a backup of the config , and now I can't remember how I did it for the life of me. I do believe I was pulling a /56 and had a /64 assigned to the wan interface and a /64 assigned to the bridge interface . I'm learning a little bit more every day . Thanks again to you both !

You probably should have a /128 assigned to the WAN interface, from my router:

IPv6 Link Local fe80::208:a2ff:fe0a:xxx
IPv6 Address 2600:8800:ff06:c00:xxxx
Subnet mask IPv6 128
Gateway IPv6 fe80::212:d9ff:xxxx

Strictly speaking, that's not necessary. It's usually done, makes the setup resemble IPv4, but it's not required. It will route traffic just fine using the link local address and can be reached with the ::1 address from a /64 if needed.

I don't know if it is necessary or not, it is just what Cox sets when I get address from them.

It's not Cox; it's whatever your router is requesting via DHCPv6.

I use this DHCPv6 client and have it configured it get the /60 prefix delegation then assign /64s to my two LAN interfaces. No /128 for the WAN interface. If I need to remotely access my router I just use the ::1 address assigned to a LAN interface.

I could get a /128, either a DHCPv6 normal or temporary address, Cox will hand them out, but for my particular setup it didn't add any benefit. Default gateways in the IPv6 world frequently use the link-local address; it's not necessary to have a globally valid address for your upstream router in IPv6, nor is it necessary for your WAN interface to have one:

# ip -6 route show default
default via fe80::6273:5cff:fe72:23d9 dev eth1 proto ra metric 1024  expires 1799sec hoplimit 64 pref medium