Comment 5 for bug 1788659

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.