I got IPv6 working on the WAN router, then tried a few different things before getting it to work on the WiFi router.

Getting the tunnelbroker.net 6in4 tunnel to work was pretty straightforward. The router software supports it directly, so configuration was a matter of copying values from the HE website for my configured tunnel. The router reset, and hesitated to reconnect to the WAN, but eventually the dust settled and it worked again.

I connected to the WiFi on the WAN router and was awarded some IPv6 addresses off the boot. A quick hit on test-ipv6.com confirmed my address.

I started in on the configuration on the WiFi router. I started with a Static IP configuration, because that seemed to work before. The router reset, but while the addresses were assigned, I wasn’t able to SSH or use the web UI. A couple quick pokes and it seems that the IPv4 configuration was mostly reset. The router’s IP and the DHCP pool were wrong, but the reservations remained. I adjusted those incorrect values and restarted the router again. It was better.

On my workstation I was able to see that I’d been given an address from the /64 I configured on the WiFi router. But hitting test-ipv6.com failed to detect my IPv6 address. I poked in the settings for both of the routers and could see that both of the networks were configured, and the WAN router could see the assigned static IP of the WiFi router, but there was no routing established between the two. I poked a bit looking for a place to enter the static route of the /64 in the WAN configuration, but couldn’t find one. Having poked in the SSH tables for the last few days, I’m sure I can add one via the command line, but I want to make sure I do it in a resilient way.

I switched the WiFi router to use the Passthrough configuration. Upon rebooting (not entirely sure why it needs to completely restart with some of these changes…maybe it’s being overly cautious), my WiFi-connected node was awarded an address from the /48 of the WAN router. Checking in both router interfaces showed the assignment on both. Hitting test-ipv6.com confirmed the address, too.

That’s now three of the four things I need to get done.

I can connect a node to the WAN router and get to the Internet with a public IP.

I can connect a node to the WiFi router and get through to the Internet via its NAT.

IPv6 works on both of those networks.

I still need to get the server working with its multiple networks, each going to the Internet.

I had poked at it a bit, and I can get the server to reach out correctly with multiple gateways defined, but it doesn’t entirely behave as expected. It has trouble correctly discerning which gateway to use when it originates traffic, even when specifying the interface to use.

I’m close, but not there yet.

Putting that off until tomorrow or the weekend. I’m going to let the dust settle.