Package Details: networkmanager-noscan 1.20.4-1

Git Clone URL: (read-only, click to copy)
Package Base: networkmanager-noscan
Description: Network connection manager and user applications
Upstream URL:
Licenses: GPL2, LGPL2.1
Groups: gnome
Conflicts: networkmanager
Provides: networkmanager
Replaces: networkmanager
Submitter: alejandro.perez
Maintainer: None
Last Packager: Sunday
Votes: 25
Popularity: 0.000013
First Submitted: 2015-02-09 09:22
Last Updated: 2019-11-02 15:52

Dependencies (50)

Required by (159)

Sources (1)

Latest Comments

1 2 3 4 5 Next › Last »

alejandro.perez commented on 2018-11-05 08:27

I no longer have a failing card, so I'm disowning this package in case anyone wants to take care of it.

alejandro.perez commented on 2018-01-27 17:36

Hi all,

I've tested upstream, and something has improved (either NM or the kernel driver). Now I don't see any performance drops in the long term. I have tried several times with LAN transfers of 4GB, and they seem pretty stable.

My card is: Centrino Advanced-N 6235.

It seems to have been the kernel driver, as now executing "iwlist scan" no longer genererates drops as it used to do.

I recommend you to test this. Using the mate-system-monitor/gnome-system-monitor or any similar tool you can see a graph of the network transfers. Just make a LAN copy of something and see whether there still are periodic drops.

alejandro.perez commented on 2017-11-23 16:05

Upgraded to 1.10.

Probably you are right. I've just updated the package, let's see if anyone can test upstream. I will be far away from the router today, so won't be able to do it myself.

xsmile commented on 2017-11-23 15:03


After reading the relevant part of the source modified by the patch and some bug reports I found on this page, I believe background scanning is deactivated only if a specific BSSID is pre-set, see [1]. Otherwise, which probably applies to most use cases, it is still active.


alejandro.perez commented on 2017-11-23 07:47

Hi xsmile,

there seems to be new code upstream to prevent background scanning. Has anyone tried if it solves the issues? Maybe we don't need this patch any longer.
I remember that plain wpa_supplicant worked well, so maybe the supplicant would be less disruptive.

I'll try to test it later today. If it still fails, I'll generate a new package.

Thanks for the patch BTW!

xsmile commented on 2017-11-23 05:46

Updated the patch for 1.10:

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. :)