It seems there is no UI way to get the IPv6 routing to work, but I can add a route if I SSH and hit a command line just right.

I'm using a tunnel from tunnelbroker.net to poke around with some IPv6 stuff. Not playing on the dark web or anything, but getting things working the way they could (maybe should?) be.

I've got a /48 from tunnelbroker.net, and planned to route a /64 through my WiFi router, leaving the rest of the /48 on the WAN router's LAN side. Maybe in the future I could leverage other /64 networks for other reasons, like putting web hosting in Docker containers.

I don't know if it'll stick, but I added a script to the router's supposed custom scripts directory. I've found and thought I used the correct names, and they work on the other router, but I can't get them to fire automatically on the WAN router. I am able to trigger them directly, so I suppose I can always run the script again if the IPv6 on the WiFi LAN stop working.

In my investigations, I did find that my WAN router is now EOL by the manufacturer, and isn't going to be supported by the third-party firmware I use. I guess that's the risk of using the previous new thing, after replacing it with the newer new thing. The WiFi router is newer enough that it's still near the top of the heap of WiFi 6 routers (at least from the manufacturer).

I'm disappointed in the little TP-Link router I bought to do this job, after finding that it's basically a NAT-only router, and doesn't seem to do proper routing when the NAT is disabled.

I still haven't been poking too much into getting the new network behaving on the servers. The (test) one is multi-homed, and I've set up a couple of the less-used backup domains (think misspellings) with the server IP from the new range, but while the traffic can reach, and the routing tables seem correct, no responses.

In the little poking I did find a fun little tool that'll use a number of servers from around the world to test connectivity or visibility from a number of places around the world. Hitting https://check-host.net/check-ping?host=jekewa.com will test for this blog's host (or more accurately, the CDN in front of it). Changing the host to an IP works. I did find that using the server's public IP did show that some of their servers can't reach, which aligns with my IP rules! They don't support IPv6, though.