On 2017-01-29 16:37, James Knott wrote:
On 01/29/2017 09:53 AM, Carlos E. R. wrote:
I just set up a connection to my home network via Ethernet and tethered to my cell phone via WiFi. "ip route show" lists both, with the Ethernet showing a metric of 100 and WiFi, 600. This metric is what is used to give Ethernet priority when both are connections are up.
In Windows 10, I also have both connections up, with metric of 35 for Ethernet and 55 for WiFi.
In general, routers can select a route based on "cost". This cost may include metrics for interface bandwidth, hop count, load and more. It is also possible to assign a cost, so that one interface is always favoured over another. This is why the Ethernet port has a lower metric than WiFi. It's preferred when both are available. Otherwise WiFi is used.
In my case, with both interfaces up (connected to the same router) it doesn't work right. I don't remember now if I get successful connectivity or not. What I remember is that the log fills wit martian packages reports, so things are not right. I have to remember to kill the Wi-Fi with the switch. The other day I configured both interfaces to assume the same IP. After all, I want to access ssh by name to the laptop, regardless of interface, using the same name. This is a recent change, the problem observed in the previous paragraph has been going on for years. My observation on Windows is that the WiFi automatically disconnects (light is up, interface is down in network properties) when I plug in the cable. This is the behaviour I want in Linux. I have no intention to route between interfaces. But this is not the OP problem. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)