This should be been mostly fixed in Oneiric now, with the latest revision of NetworkManager and nm-applet.
To clarify, I guess what you mean was that wired would be connected but then no traffic at all would pass unless the connection was re- established? Regardless, I can see it appears to work properly here if I plug in or unplug a wired connection with my laptop. Please, update and try again, and if you're still having issues, reconnect so that your connection works properly and issue the following command in a terminal to attach additional information to this bug report: apport-collect 846320 Additionally, if possible please also comment with the output of the "ip route list" command when wired has just been connected and the "connection doesn't work", so we can verify that routes are being added and handled properly. Thanks in advance! ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/846320 Title: Wired connection does not take preference over wireless (regression 11.10) Status in “network-manager” package in Ubuntu: Incomplete Bug description: When there is an active wireless connection, and the wired connector is connected, network manager is responding by notifying that the wired connection is made and the icon changes from wireless to wired. In ifconfig, a IP-address is bound to ethX. But when trying to do any file operations (or other things), it comes clear that the wired connection is not used, despite the icon and notification. The wired connection can only be activated when the wireless connecttion is forced into disconnect. But then, the wired connection is not becoming active, only after re- connecting the wired connection. Maybe the last problem is related to this bug mentioned. If not, a separate bug should be filed. When pulling the plug from, the wired connection, the wireless connection does not becomes active automatically, like it did prior to 11.10. You have to force the wireless connection to get connected again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/846320/+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