Interim update for anyone else with the issue (I hit my post limiter, else would have updated sooner):
End of first day, the HA Blue is still not showing up on my network. Despite very good efforts of @cogneato, it still doesn’t take an IP address or show any connection in the router software. We’ve tried setting manual ipv4 addresses, gateways, dns servers, and no dice.
We have uncovered some uncertainty around the interplay of the velop mesh and the router, where the former manages DHCP services and the latter is an ISP provided router physically patched to the first mesh tower. I hadn’t realised that might be problematic, because although its not necessarily common, everything I’ve ever plugged into any of the mesh towers has just picked up an IP address from it and been immediately connectable. Taking the same port on the tower, the same patch lead, and plugging in a game console has revealed working autodetected settings for ip range, gateway and dns server, and yet copying those into blue then reattaching it to the same port and lead did not show any presence when rebooted.
None of which takes away from the efforts of cogneato. We did go to Discord, and we tried to set up a new network profile. The system default one we’d expected to find in /mnt/overlay/etc/NetworkManager/system-connections/*
was identical to the one we were using, and we’ve not yet found a way to get back to a clean start.
I’ve factory reset the mesh and started anew with that. No change on blue. Still doesn’t appear on the network. Velop now putting out addresses in the 10.13.1.x/24
range, so I’ve tried that too.
We’ve also tried to get the connection back to its auto state, but as we were unable to make the connection on blue save after set ipv4.mode auto (as removed the addresses, but then wouldn’t save without them) To attempt a workaround on that I’ve also run set ipv4.dns with no value and set ipv4.gateway with no value. print ipv4 now shows no addresses and saves with auto enabled, but on restart nmcli just shows no ip address and says its getting ip configuration.
I was glad to have a tv with an hdmi lead on it near the mesh tower, as we are mostly iMac and laptop here. Screens and keyboards are not an easy find, and I’d naively thought I’d just be able to plug it in and go from the web UI. Much poring over console output. Thank goodness for HDTV sets, but I dread to think how this would have worked if I didn’t have a TV near a network port.
We’ll get there. Just not yet. If we find a solution, I’ll post it here as I’d hate for anyone to read this lot, say “Gosh! That’s me too!” and not know how we solved it in the end.
Presently, I’ve gone back to set ipv4.mode manual
and given it a dns via set ipv4.dns 8.8.8.8
and the gateway set ipv4.gateway 10.13.1.1
and the address set ipv4.address 10.13.1.200/24
I’ve also realised I can remove ipv4 addresses via:
nmcli con mod "Wired connection 1" -ipv4.addresses "10.13.1.200/32"
which is easier than resetting to auto when I forget the subnet.
Restart shows me a green connection, but http://10.13.1.200:8123/ doesn’t take me anywhere. So, learning lots but going nowhere thus far