For the original request about a fleet of machines, the facility to disable this is already there:
1) set no-auto-default=* in /etc/NetworkManager/NetworkManager.conf 2) preconfigure a wired connection for the existing wired interface, locked on MAC address future versions of NetworkManager will allow you to lock on interface name, but be aware that the interface won't always be 'eth0' so some amount of machine-specific configuration will always be required here. If #1 and #2 are done, then no other device will get the automatic DHCP connection. In the case of all other USB ethernet devices (including android devices) there's simply no way to distinguish between an Android device and an actual usb-ethernet device with an RJ-45 connector on the end. You can either go about tagging every single Android device into a blacklist for this. Or we could start a whitelist of usb-ethernet kernel drivers or something. That would include asix, rndis, catc, etc. Half of drivers/net/usb/ is a candidate for whitelisting. The big question: are there any/many usb-ethernet dongles that use plain cdc-ether ? -- 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
