How I broke and fixed my hub mesh

I have two networks, home and remote (in another state) connected by an IPSec tunnel between routers. I have a C8 Pro here at home and a C7 in the remote location with hub mesh enabled and it's working great. But earlier this week it broke and it took me a bit to figure out why.

I was adding a matter device to my C8 (which is ethernet connected normally) so I had to setup and connect the WIFI to add the matter device. Turns out that broke my hub mesh having that on. I could get updates to devices from the C7 to the C8 but changing a linked switch on the C8 didn't transfer to the C7. Turning off the WIFI so only the configured ethernet address was on, on the C8 resolved the issue.

Now my setup is a little unusual. Since I'm using the two hubs across an IPSec tunnel they are on different subnets 10.6.0.0/24 <> 10.6.1.0/24 the hub addresses had to be manually configured on each side. If both of your hubs are on the same subnet I'm not sure if hub mesh will react that same way or not.

Just goes to show that sometimes changes can have unexpected results. :smiley:

Well.. for me, as I read your story, I did expect that result. :smiley: :smiley: :smiley: I've built thousands of IPSec VPNs and Routing has bit me more than a few times. :slight_smile:

Well I'm not sure it's the routing that is the issue. Since I was getting updates from the remote to home, but the other way, I suspect updates from the C8 were sent to the C7 via the C8's WIFI ip address and the C7 was only configured for the ethernet address in the mesh setup and that was causing the failure. As the reason the c7 is 700 miles away ends in two weeks so I'm not going to mess with it but I suspect if I add the WIFI IP address to the C7 mesh configuration it might work.