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: Sunday
Last Packager: Sunday
Votes: 25
Popularity: 0.21
First Submitted: 2015-02-09 09:22
Last Updated: 2019-11-02 15:52

Dependencies (50)

Required by (129)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

alejandro.perez commented on 2016-12-20 18:01

Updated to version 1.4.4

alejandro.perez commented on 2016-08-08 18:53

updated to version 1.2.4. Please report any issue.

shijtin commented on 2016-07-15 13:14

Yep, just like the blog post says, it is not good for roaming. Unfortunately.

alejandro.perez commented on 2016-07-15 12:03

I didn't know about that solution. It is a good solution for home, but it is unconvenient for many other situations. E.g. I work at the University, and we have eduroam-based connection. That means that we have tens of APs with the same SSID. I want that when I'm sit on my desk scanning is not working. But I also want that when I move to a different room, the computer associates with a different BBSID, and still does not scan :)

You can find similar situations in public transports, city-wide connections, and hotels!

shijtin commented on 2016-07-15 11:56

I don't know if it is less or more convenient than this package depending on the situation, but there is an official way to prevent NM from scanning every 2 minutes once a particular WIFI connection is established.

You have to set the BSSID of the access point in the connection settings.

alejandro.perez commented on 2016-04-30 06:44

I had the hope that since they claim scanning has changed in this version, our problem was fixed in 1.2, but no :(.

Please, report any problem.

rhssk commented on 2016-03-06 07:25

Couldn't get it to work when trying what you suggested, so I just went with this:
I was sort of using this before, but without NM controlling the connection. That ended up sometimes messing up with my boot/shutdown times because the connection wasn't terminated properly. The above solution works well and it is my home PC anyways, so I don't mind setting it up for specific connection name.

alejandro.perez commented on 2016-03-04 21:07

I just checked and it works with VPNC. I'm sorry I'm not sure why it is failing to you. It should not fail, as I told you I didn't change anything relevant. you could try the following and see if it works.

yaourt -G network-manager (this is vanilla version)
cd network-manager
makepkg -o
browse the files and apply my patch
makepkg -e
pacman -U package

This will assure you are using all from the vanilla version, with the mini-change to avoid re-scanning.

Good luck!

rhssk commented on 2016-03-04 20:54

Yes, I am 100% sure about vanilla NM. Recorded output from journalctl when connecting to VPN here:

alejandro.perez commented on 2016-03-04 10:15

Umm, I don't recall having any problem using VPNC. The patch is a simplistic 3 lines change to avoid scanning when connected, it should not interfere with IP assignation. But I might have missed a configuration option of the official package (I typically just take the same PKGBUILD and add my patch, so I shouldn't).

Are you sure that vanilla NM has no problems? I will check with my laptop and vpnc (that's the only VPN server I have) and see if it works.