This might be SRUable, is it worth spending time on this bug to provide a patch in 12.04, given that the patch itself is pretty small and only affects ifnet/biosdevname? By this I mean, will you have time to test the resulting package in your use case, so that it can land in -updates?
My main issue with fixing this as a stable update (it *will* land in quantal regardless) is that there are very few users at the intersection of using biosdevname, and using NetworkManager -- I want to make sure we only ship a fix to a stable release for this if it can be properly tested, not just sit around in -proposed for a few months. :) If you think it's useful as a stable update, please follow http://wiki.ubuntu.com/StableReleaseUpdates#Procedure to update this bug's description with how to test, etc. Thanks in advance! -- 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/962587 Title: When using ifnet plugin and biosdevname is enabled, NetworkManager may treat wired interfaces as wireless interfaces Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Triaged Bug description: From the source for network-manager-0.9.3.995+git201203152001.04b2a74, I see that NM would treat any NIC names resulting from having biosdevname enabled (of the form em* and p*p*) as wireless interfaces. This is apparent from src/settings/plugins/ifnet/net_parser.c and src/settings/plugins/ifnet/connection_parser.c. init_block_by_line in src/settings/plugins/ifnet/net_parser.c: if ((conn = get_connection_config (pos)) == NULL) { if (g_ascii_strncasecmp (pos, "eth", 3) == 0 && strlen (pos) == 4) /* wired connection */ conn = add_new_connection_config ("wired", pos); else if (g_ascii_strncasecmp (pos, "ppp", 3) == 0 && strlen (pos) == 4) /* pppoe connection */ conn = add_new_connection_config ("ppp", pos); else if (ignore_connection_name (pos)) { /* ignored connection */ conn = add_new_connection_config ("ignore", pos); } else /* wireless connection */ conn = add_new_connection_config ("wireless", pos); } get_wired_name in src/settings/plugins/ifnet/connection_parser.c: gchar *conn_name = g_strdup_printf ("eth%d", i); It is not clear to me if any wireless interfaces would be named of the forms em* or p*p*, so I do not know if it would be sufficient to check the name of an interface to determine what type it is. However, it at least would usually be incorrect to label an interface called, say, em1 as a wireless interface. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/962587/+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
