2019-02-22, 05:47 AM
I've been fiddling with network modes here in the marina for the past couple of days. Like many marinas, it has WiFi that is keyed to a specific hardware address, so my normal process is to use my OpenPlotter system as a hotspot for the boat. In this case, I chose RPI3+ AP + Client.
I'm finding that just connecting the client wireless node to the marina gives two default routes - one via 10.10.10.1 (wlan1) and the other via the marina system, in this case 10.10.1.1.
If I just do the connection, routing doesn't happen. DNS lookups fail and even pings to straight IP addresses, like 8.8.8.8, don't work. I find what I need to do is open a terminal session and type "sudo route del default wlan1" to drop the internal default route and force traffic via the marina system.
Is anyone else having this issue? Is it possible that as a normal process the default route via 10.10.10.1 should be dropped when a connection is made to an external AP?
I'm finding that just connecting the client wireless node to the marina gives two default routes - one via 10.10.10.1 (wlan1) and the other via the marina system, in this case 10.10.1.1.
If I just do the connection, routing doesn't happen. DNS lookups fail and even pings to straight IP addresses, like 8.8.8.8, don't work. I find what I need to do is open a terminal session and type "sudo route del default wlan1" to drop the internal default route and force traffic via the marina system.
Is anyone else having this issue? Is it possible that as a normal process the default route via 10.10.10.1 should be dropped when a connection is made to an external AP?