I eventually figured out that's what was happening. However, the connectivity check is not working correctly. In my case, there is indeed ethernet connectivity, despite it thinking that there isn't. It will assign the network "penalty" metric even when ethernet has been connected for 30+ minutes, so something is causing it to incorrectly fail the connectivity check. If I override the metric manually, it works and uses ethernet, so there is not a problem with the connection.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1788659 Title: network manager assigns ethernet default route metric of 20100 Status in network-manager package in Ubuntu: Incomplete Bug description: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
