I tried to work around this problem by means of the "metric" option in /etc/network/interfaces but I did not succeed. The smallest value allowed is 1 whereas the metric assigned by NM to the route to the default gateway via wlan0 is 0.
I suggest that NM assign a value higher than 0 to the route so that it's possible to use the "metric" option in /e/n/i to give a lower metric to a route via another interface. The value 100 (ifup's default) might be a good choice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/47379 Title: NM assigns a lower metric to the default route over wlan than ifup assigns to the default route over eth. Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager Dapper RC, IBM Thinkpad T41p: when booted while connected to my wired network, the network-manager also detects a nearby open access point and establishes a connection there as well. Despite specifying eth0 as the default gateway in the networking applet, default routes are installed for both networks, with the wireless route listed first by "netstat -nr", and traceroute shows all network access tries to use the wireless route. To use my wired network, I have to manually deactivate the wireless interface. It was my understanding that the newly added network-manager in Dapper automated this, preferring wired over wireless when both were available. Even if this is not the case, selecting the wired network as the default gateway in the networking applet should work, and remove the default route to the wireless interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/47379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
