I realized that not all of the devices previously attached to the WiFi had reattached. Specifically, some of the Ring cameras I have scoping the underside of our house had been offline since Halloween afternoon.

I thought it might have been some of the many reboots the router did. It seems the easiest thing to ensure the configuration is applied is to reboot the router after saving information from the web UI. I've gotten too familiar with what just applies to settings and restarts services, and what affects and restarts the whole router.

After restarting the cameras and unsuccessfully trying to reapply the network settings, I sat back at the computer and scoured the web UI for unintended changes.

I noticed immediately that the SSL certificate on the router was wrong. I checked the DHCP settings and found the DNS and range had changed. I poked through these and a few other screens, fixing things that were awry. After a comprehensive review, the cameras reconnected just fine. As did some WiFi-smart outlets and lights.

All the time, the new WAN connection remained, and IPv6 stuck with everything!

I'm going to let it sit for today and start noodling on the multi-home server. Once I figure that out, I need to apply it to the other server.

I may short-circuit the changes, though, and just quick-change to the new ISP, since the static IPs are sticking. This will make the multiple Internet addresses unnecessary, and start making the old WAN connection wane into unused. There are a few WiFi devices that connect to that router, but I've already decided to recreate that wireless network on the other WiFi router (and then remove it from that router...it's been renamed to what it used to be with an older router, anyway), so the devices will switch, and probably shouldn't care.

I've got the websites behind a CDN, so there won't be any propagation to worry about. The CDN also does my DNS, so changes I've made in the past have been instantly (or nearly instantly) recognized.

The mail server isn't behind the CDN, though, and that might have some propagation delay. I might just grin and bear it, letting messages queue on the sending servers and arrive after propagation, which is usually pretty quick anyway.

In my casual tests, the multi-home server is responding to requests to the new IP without difficulty, so maybe I did fix the problem and any trouble I had before was related to other network issues.

Letting the dust settle, and I'll work on that later.