Red Hat Bugzilla – Bug 1473915
nmcli/nm-applet unresponsive with external usb wifi adapter
Last modified: 2017-07-31 15:19:10 EDT
i have an external usb wifi adapter which was (and still is) working properly regarding detection/drivers/firmware etc in fedora24 and very early fedora25. I did not use it until recently and things have changed considerably like so:
I am using a lenovo laptop with built-in wifi (model t440 and t420, different hw, same behavior) und use a realtek based usb wifi stick with an external antenna for better coverage.
- after plugging in the stick, the usb wifi is recognized (dmesg saying no problems)
- the plasma5 taskbar nm-applet ('networks') is opening as normal, but clicking on the 'configure network connections' icon is opening the connections/system settings module only with a very long delay!
- the command 'nmcli device status' is also slow as hell, e.g. even commandline completion 'nmcli device show <tab>' is taking verly long to display the internal wifi and the usb/external device name as completion suggestion
besides this slowness, i cannot force fedora to use the usb adapter exclusively for a specific wlan (and ignore the internal wifi adapter)
-- the nm-applet cannot choose which adapter to use
-- the 'connections/system settings module' seems to ignore settings on the tab 'wifi' / "restrict to device", even though choosing my two devices is possible
-- this could(!) be related to a authorization problem, because i am running this 'connections/system settings module' as a normal user (not root). what makes me think so is the following: Instead of this tool i was also using nm-connection-editor' to change the settings - here, i am asked for the root password before any changes in devices is possible...(!)
- why is there this considerable delay when using bot adapters in nmcli/nm-applet?
- how can i simply disable the internal wifi for testing with the usb-wifi stick exclusively? Switching off (on the t420 i have a hardware switch for wifi/bluetooth) does also lead to fedora not recognizing the usb-wifi stick at all as a usable networking device!
As far as i remember, this was all working quite smoothly previously, switching devices was a breeze...
Any idea about what logs i can provide to solve this problem?
For now, usb-wifi is simply not possible, i am not even sure if the scanning of networks is really using the usb-wifi stick or simply sticks to the internal wifi...
Thanks for your help
forgot to mention:
- kernel 4.11.11
- fedora25 kde spin, plasma5 latest updates
Can you please do the following:
# (as root):
nmcli general logging level TRACE
# then plug in the stick
# wait 20 seconds
nmcli device status > nmcli-device.txt
journalctl -u NetworkManager --since "2 minutes ago" > log.txt
dmesg > dmesg.txt
and attach the 3 log files? Thanks!
please find the attached files to this report...
Created attachment 1304383 [details]
logfiles and stuff
It seems the wifi driver is buggy and doesn't accept a MAC address change. This causes a retry-loop for each wifi scan, which slows down NetworkManager.
Can you please try adding a new /etc/NetworkManager/conf.d/10-wifi-scan-mac.conf with the following content:
Then restart NM with: systemctl restart NetworkManager
Thanks a lot - your suggestion did the trick!!!
Now, i can see in plasma/network applet the wifi ESSIDs and the corresponding device, so choosing the right device is easy (and possible!) again.
nmcli and iwlist work as expected
Any idea if having this setting (in conf.d) as a default is considered a problem?
And, what can we do to fix the driver itself (the firmware wasn't updated for some time, at least here i am at the 'current' release... the driver comes with the kernel itself?)
Anyway, thanks for your help!!!
(In reply to slartibart70 from comment #6)
> Thanks a lot - your suggestion did the trick!!!
> Now, i can see in plasma/network applet the wifi ESSIDs and the
> corresponding device, so choosing the right device is easy (and possible!)
> nmcli and iwlist work as expected
> Any idea if having this setting (in conf.d) as a default is considered a
No, the only effect is that MAC address randomization during wifi scans will be disabled; it's enabled by default to improve privacy, as it prevents possible tracking of your MAC address.
> And, what can we do to fix the driver itself (the firmware wasn't updated
> for some time, at least here i am at the 'current' release... the driver
> comes with the kernel itself?)
Yes, please report it upstream or file a bug for the 'kernel' component.