Description of problem: NetworkManager should not automatically disconnect wireless - when wired is connected. This is unacceptable because it will cause existing [ssh] connections to stop working. Perhaps it should prompt the user to make sure this action is acceptable. Version-Release number of selected component (if applicable): NetworkManager-0.5.1-5.1 How reproducible: Steps to Reproduce: 1. connect laptop to wireless 2. Start working [ssh to a different machine] 3. now plug in the laptop to port replicator [which has power-supply & network cable] 4. NM disconnects the wireless and connects the wired automatically. Actual results: Now all my ssh connections are frozen [causing work interruption] Expected results: Wireless should continue to be used when I dock the laptop. Additional info: If the current network gets broken - then its acceptable that NM automatically looks for a working wired/wireless connection. But if the current connection is working - then breaking it is correct behavior. Perhaps it shoud prompt the user to see if this is acceptable [or there should be some menu option to force such a change when user desires it]
Oops "then breaking it is correct behavior." -> "then breaking it is incorrect behavior."
The NetworkManager equivalent on OS X behaves like the RFE here requests, I think, so it is kind of expected. Also it is a nice feature when you're using Connexxion by Boeing and want to transfer files over the wire to your coworker instead of using the wireless network on the airplane ;)
I consider this a bug [not a RFE] - as the normal behavior breaks valid connections. If the prompt to the user is annoying - then there could be a config option user could toggle. 'Prefer Wired Connection' - if enabled - NM will disconnect wireless when wired is plugged in - if disabled - NM will not disconnect wireless - even though wired get active.
These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks
Actually more of an RFE. Having both connections up at the same time was not one of the original design considerations or targets of NM, nor is it possible at this time. As we grow NM out to support more use cases, this will get fixed however.
Actually I had no mention of having both connections up at the same time. The reason its a bug [in protocol or behavior] is - it 'breaks' working connections - when it shouldn't.
If this issue turns out to still be reproduceable in the latest updates for this Fedora Core release, please file a bug report in the Gnome bugzilla located at http://bugzilla.gnome.org in the "NetworkManager" product. Once you've filed your bug report upstream, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Setting status to "NEEDINFO_REPORTER", and awaiting upstream bug report URL for tracking. Thanks in advance.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
I've retried NM with F7. Looks like NM is not automatically changing networks on disconnect/reconnect. so, my wireless remains active when I plugin the network cable [which is the desired behavior.. However in my various attempts at testing this - once NM disconnected the wireless infavour of the wire network.. Mabe this is a fluke.. For now I'll assume this bug is fixed [untill this happens again]. Currently I have other issues with NM - these are preventing me from using it.. Will file another bz entry for it
This happens for me with Fedora 8 I plug in a wired network cable, and it automatically disconnects the wireless. It then turns out it can't get an IP address (because I've just plugged this in to synchronise a laptop) so it leaves my network broken because it zeroconf's it. At the least, it would be nice if NetworkManager waited to get a valid wired connection before disconnecting the wireless.
Multiple active device support is not yet implemented in F8's version of NetworkManager. That will come along later. This is still an RFE really...
Turning this into the multiple active connections tracker bug. This feature will allow devices to be activated and deactivated independently of each other when their underlying connectivity goes up or down.
*** Bug 199536 has been marked as a duplicate of this bug. ***
*** Bug 239190 has been marked as a duplicate of this bug. ***
fixed in rawhide