So, I spent a little time setting up wireguard, following this guide:
Unfortunately, while that guide was helpful in getting NATed IPv4 working, it doesn't really talk about IPv6.
I didn't want to do NAT'ed IPv6 (part of the point of IPv6, being, after all, having real, route-able addresses).
I tried assigning the Wireguard 'interface' to use a static ipv6 address from the same subnet that is assigned to my bridged lan+wlan, but, and also the other wireguard device to have a static ipv6 in that same subnet. However, once I brought up the Wireguard interface, IPv6 stopped working on my lan+wlan.
I'm thinking maybe to get routing working between wireguard endpoints and the internet, they would need to be on a separate subnet? That assigning an address in that subnet to the wireguard interface is changing the routing tables in the kernel such that it thinks all traffic to and from that /64 has to go to wireguard, essentially stealing that subnet away from the lan/wlan interface.
So, here's the thing, I think my ISP (Spectrum) only assigns me a /64? Is there some way to get OpenWRT to request a /48 instead of a /64?
Also, that /64 prefix is dynamically assigned, and could change in the future. So, preferably, whether I can get a /48, or only a /64, if I'm going to get this working, I'd rather not use statically assigned addresses in Wireguard, because that means when my prefix changes, wireguard will break. Is there some syntax to allow me to pass through the dynamic prefix, and just assign a static host address? Or even a randomly generated host address?
So far, I've not identified much in the way of features like that with the Wireguard interface. I also thought about trying to bridge it with the lan+wlan, so it could share the /64, but the option to bridge the interface doesn't seem to be supported by the wireguard interface (at least, not in Luci).