Hi
I am attempting a rather unique home setup where I have a device on my home network act as IPv6 router and then pushes packets to the BT hub LAN Link Local IPv6 address and they go on to the internet from there.
To achieve this I have a Linux box set up with ISC running DHCPv4 Bind running DNS and RADV and RDNSS set up sending RA's advertising the /64. Once this was running I set the BT Hubs IPv6 address allocation to none. My understanding is that you cannot have 2 devices on the same network sending out RA's
This worked for an hour or 2 then after a while I lost IPv6 connectivity.
Going back to the Hub I noted that the LAN side GUA was ::
Previously it was a GUA in the hubs /64 with the same host part address as the link local
i.e.
Link Local: fe80::c6e5:32ff:fe36:4d36/64
GUA: 2a00:xxxx:xxxx:xxxx:c6e5:32ff:fe36:4d36/64
This meant that packets lo longer had a clear IPv6 path to and from the internet AFAICT.
Turning Allocation to stateless and back to none restored the LAN side address until the address lifetime presumably given by the BT hub expires and then returns back to ::
My question is - is this by design?
I understand the possibility of the /56 and consequently the /64 changing down the line however should that happen my network will still retain IPv4 capability. However conceptually what I had set up WAS working until the hubs IPv6 LAN address vanished.
I would have hoped that the LAN side would have picked up the RA's from my linux box and configured the LAN IP using the advertised /64 or at the very least have an autoconfigured static address.
Thoughts would be welcomed here.
Thanks in advance.
