I'm seeing this on a fleet of laptops which all have Fast Ethernet, 802.11a/g/n and GSM HSPA interfaces.
If the WLAN is active and configured as the default route when the GSM HSPA WWAN is activated the default route is changed to be the WWAN. I wonder if NM could accept a user-specified (or automatically assigned) metric for each interface without requiring a static route to be specified? If the user then chooses to disconnect from an existing network or the connection drops through being out of range the next most senior link would be selected. The manual configuration I use for default routes is: $ ip route ls default via 10.254.251.1 dev eth0 proto static metric 1 default via 10.254.251.1 dev wlan0 proto static metric 9 default via 10.50.163.2 dev wwan0 proto static metric 19 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 10.50.163.0/26 dev wwan0 proto kernel scope link src 10.50.163.32 metric 7 10.254.1.0/24 dev virbr0 proto kernel scope link src 10.254.1.1 10.254.251.0/24 dev eth0 proto kernel scope link src 10.254.251.50 metric 1 10.254.251.0/24 dev wlan0 proto kernel scope link src 10.254.251.60 metric 9 Notice how the metric assigned by NM to wwan0's link (7) is more senior than wlan0 (9). I think that could do with changing as a default so that 802.11a/g takes preference behind wired Ethernet. -- 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/802782 Title: Please add NetworkManager option not to auto-enable new network devices Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” source package in Precise: Confirmed Status in “network-manager” source package in Quantal: Confirmed Status in “network-manager” source package in Raring: Confirmed Bug description: This is a feature request. It would be nice if Network Manager could be configured such that it won't automatically attempt to use new network devices attached to the system. Here's the reasoning. My team manages a large fleet of enterprise desktops. We've had a number of cases where a user plugs a USB NIC into their computer, and Network Manager helpfully configures the new network interface and runs dhclient on it. And if the DHCP response is answered, you get a new default route, new resolv.conf, etc. In a couple cases this was caused by plugging in an Android phone that had USB tethering turned on, and I think we even had one case where plugging in a USB GPS did this. None of the cases involved the user actually intending to use the device as a network interface. We could blacklist the usbnet module, but there are legitimate cases where we want to allow USB networking. It would be so much better if we could get Network Manager not to use these new devices that have shown up until the user configures them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/802782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
