Description of problem: NetworkManager should be able to connect to wired and wireless network at the same time (using different metric in route table) How reproducible: Use NetworkManager with both wired and wireless connection, unwanted behavior when switching to wireless. Steps to Reproduce: 1. Start in situation where you are connected to wired network 2. Try to connect to wireless network 3. NetworkManager disables wired network! 4. Asks for key 5. Connects to wireless network 6. If this fails switch back to wired Expected results: 1. Start in situation where you are connected to wired network 2. Try to connect to wireless network 4. Asks for key 5. Connects to wireless network with higher metric value in route table 6. If this fails, do nothing Additional info: When connected to wireless and wired network wired network is preferred. When you unplug wired immediate switch to wireless. The problem now is that when you try to connect to wireless network the wired connection is disabled before the wireless connection is brought up (unwanted). They should be both active, or only disconnect wired when the connection to the wireless network is successful.
I would prefer to see this done at layer 2, so that your SSH terminals don't die. Perhaps this could be achieved with a bridge device, but this is quite hard to pull off given the dangers of network loops. Maybe wait for RSTP to hit the Linux kernel?
*** This bug has been marked as a duplicate of 178276 ***