Description of problem: I recently plugged in an usb wifi receiver with usb extension cable because I had a bad reception due to my laptop positioning with the internal pci wifi. When I checked the gnome user menu, everything seemed fine: both were there, and the pci wifi was still connected to the network and the new usb wifi was available and waiting for instructions. So to use the external one, I turned off the pci one and attempted to then connect the usb wifi one... (see screenshot 1) well except that turning off one wifi card apparently turns off ALL wifi. (see surprising screenshot 2) Since this seemed to be the most obvious way on how to force a certain network card to be used, I'm now stumped on how to do this. Also, please consider a fix for this. Version-Release number of selected component (if applicable): GNOME Shell 3.10.2.1 How reproducible: 100% Steps to Reproduce: 1. Add second wifi card to computer 2. Attempt to turn one off to force it to use the other through the gnome shell user menu 3. See how it turns off both instead of just the one you chose Reproducible: Steps to Reproduce:
Created attachment 5123 [details] Screenshot 1 (turn off attempt)
Created attachment 5124 [details] Screenshot 2 (result: both are disabled although I just clicked "turn off" for the other)
Forcing one card down with ifconfig wlan0 down will just confuse NetworkManager to no end and disable internet although the other one with good reception is still happily connected. How am I supposed to do this properly? The one card NetworkManager picks automatically really has bad reception, so how can I educate it to use what I want and not whatever it randomly decides to pick?
Ah, I simply need to disable auto connect on the one I don't want. Still, simply disabling the one I don't want to use seems the first obvious thing to try..
Keywords: (none) => UPSTREAM
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD