in an Ethernet cord and the SSH connection kept going. The WiFi connection has a routing metric of 600 and the Ethernet connection has a routing metric of 100. The domain associated with the WiFi connection is on a static range (controller.lan) while the Ethernet connection is on a dynamic range (dhcp6.lan). The SSH connection was made when the WiFi network was the only network available. It kept going for an hour after that I reckon, and then had to be re-established. I think it now uses the Ethernet connection. Why would the SSH connection not keep on going over the existing WiFi connection? The connection never dropped
FUCKING GONE AGAIN
Switched back to Ethernet as a primary, clearly my software stack in general (*cough* Barrier *cough*) doesn't like WiFi in general
Обсуждают сегодня