Package Details: networkmanager-noscan 1.8.4-1

Git Clone URL: (read-only)
Package Base: networkmanager-noscan
Description: Network Management daemon with Wi-Fi scanning disabled when already connected (improves reliability of the connection in several Wireless cards)
Upstream URL:
Licenses: GPL2, LGPL2.1
Conflicts: networkmanager
Provides: networkmanager
Replaces: networkmanager
Submitter: alejandro.perez
Maintainer: alejandro.perez
Last Packager: alejandro.perez
Votes: 24
Popularity: 2.693274
First Submitted: 2015-02-09 09:22
Last Updated: 2017-09-25 06:46

Dependencies (45)

Required by (116)

Sources (4)

Latest Comments

alejandro.perez commented on 2017-10-15 12:11

Oh, I see. No, Enterprise wifi is how you authenticate (i.e. EAP and RADIUS).
You can roam even in your house (many people does) if you have two access points, with different BSSID and the same WPA password. When you move, NM alleguedly will see that BSSID1 is getting weaker while BSSID2 is getting stronger and, since both have the same ESSID, it will roam from one to the other seamlessly.

It does not really have to do with how you authenticate with your AP. Enterprise (.1x) only means that the AP is delegating that responsibility to a third party element (the RADIUS server). If you have a RADIUS servers of different organizations interconnected, you have a federation(such as eduroam).

JackuellnHdyde commented on 2017-10-15 12:05


No, your patched version is totally fine. I just wanted to point out, that the disabled background-scan needs to be an option for every type of Wifi. Maybe _I'm_ confused now, but I thought Enterprise-Wifi is used for roaming?! Probably I don't know as much as you about Wifi, but I never saw any Wifi-Setup where you could roam and use WEP/WPA instead of EAP/... (user + password [+ cert]).

alejandro.perez commented on 2017-10-15 11:54

I'm a bit confused now. Isn't my patch working for your 802.1x connection? Technologically speaking, 802.1x is not different than 802.11. Indeed, if I'm not wrong they merged a few years ago, since .1x describes how to authenticate while .11 describes the connection technology itself (you can se .1x as a subsection of .11).

In other words, if you edit a Wifi connection with "nm-connection-editor", you have a "Wi-Fi" tab, where my suggested option would be, and you have a "Wi-Fi security" which describes whether you use WPA or WPA enterprise (aka .1x)

JackuellnHdyde commented on 2017-10-15 11:48

Thanks for your response and your addition to the bug-tracker. Could you please add, that the background-scan has to be disabled for all kind of networks, including Enterprise Wifi (802.11x) if needed?

I can explain why: My provider is spreading free Wifi (802.11x) for its customers in Germany, which helps reducing your traffic on mobile devices. Lately I moved on to another appartment and had to wait for weeks to get an internet-cable for my appartment. I was using the free Wifi of my provider, which was okay for some time, but also noticed the horrible background-scans while playing some game. Again, the trick with the static BSSID didn't worked for me back then.

Maybe it is a bug of the cinnamon nm-applet I'm using, but a simple option, like you described in your bug-report, would avoid such behaviour easily. If there would be a description like "Disable background-scan (for high-bandwidth streaming, lessen lag-spikes)" some more users would figure it out easily and avoid googleing for hours, what is causing this behaviour.


Edit:PS: Lag-Spikes got fixed now with disabled background-scans. :)

alejandro.perez commented on 2017-10-15 11:00

It took me a while to figure out where the problem was, so I'm possitive many users would have the same problem as us, but they are either not realizing it (it only becomes really noticeable with long high bandwidth transfers, and not every one does that) or they are just blaming router/ISP or whatever.

I have refreshed the upstream bug I created: Please, feel free to contribute there if you feel like it.


JackuellnHdyde commented on 2017-10-15 10:47

Just wanted to let you guys know, that you're not alone with this problem. I already had problems with these background-scans before in Linux Mint and manually applied this patch here. Some months ago I moved on to ArchLinux and got the same problems. For quite some time I was using connman and yes ... you know ... it is also scanning in the background and there seems to be no way to turn it off easily. (main-config isn't in the /etc/-folder and config doesn't gets applied) So I went back to NetworkManager now, since it has more options and the GUI is more reliable. Hope this finally fixes the lag spikes when streaming games to my laptop. And more hopefully I would like the Dev to not be like "but muh roaming". The trick with the static BSSID never worked for me in any version of network-manager and this way it wouldn't be an easy solution to me. An option and implementation to disable background-scanning via GUI would be appreciated. BONUS: An option to set disabled BackgroundScanning as start parameter.

alejandro.perez commented on 2017-09-21 05:45

Yep, at least there are 19 of us that have been able to detect this problem and use this workaround, and that's only in Arch.

I hope NM developers will take us into account... but they won't.
In a few months from now I will have a new laptop and maybe my problems will be solved.

phil.dubois commented on 2017-09-20 18:23

This solved my wifi connectivity problems on my Surface Book. I had to remove Bluetooth software first though (bluez, blueberry).


alejandro.perez commented on 2017-09-05 14:38

Updated to 1.8.3dev as in the official repositories

nathancatlow commented on 2017-07-07 10:44

Thankyou for the update, this is still a problem here, your patch fixes it.

Dell Precision 5510 (Skylake)

02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

All comments