Home > Network Manager > NetworkManager… Where is the prefered WiFi list?

NetworkManager… Where is the prefered WiFi list?

I know somewhere there has to be a file that retains information on the wireless access points (WAP) that you connect to using Network Manager. Anyone know the name of that file?

Amanda was visiting a friend up in Cleveland a while back and connected to her friend’s WAP (named linksys). Now every time she gets near a “linksys” WAP her computer will jump to it. That includes being at home a mere twenty feet from our own WAP (not named “linksys”). Not only is it very annoying to her but it also poses a security risk to her data and could possibly be illegal.

I haven’t had a chance to really investigate this problem, either, as she is always using her computer for school. Maybe I can steal it away at 5 in the morning to take a closer look at the issue.

Categories: Network Manager
  1. J5
    2008-03-24 at 15:37 EDT

    There is no preferred wireless list. That is to say it is up to the client to tell NM what to connect to. In gnome nm-applet keeps a list of access points you have connected to in gconf(/system/networking/wireless/networks/). I think it connects to the first one it sees that is in your list. From my experience I usually connect to the correct access point and what you may be seeing is a side effect of how certain access points announce themselves. It is hard to choose from a preferred list when access point links come in asynchronously.BTW I believe it makes connections based off of MAC addresses not the AP name so at some point your GF must have connected to the linksys manually. You can use gconf-editor to remove the reference to that access point.

  2. J5
    2008-03-24 at 15:42 EDT

    Oh and if you are using KDE’s NM frontend it may have different logic for determining which AP to connect to.

  3. 2008-03-25 at 00:46 EDT

    You bring up one of the big drawbacks as NM stands now. I do believe that a connection manager is coming in Fedora 9 that will help you to delete networks you don’t want to connect to any more.In the meantime I made a quick “one liner” to clean up my own connections.for connection in `gconftool-2 –all-dirs /system/networking/connections`; do gconftool-2 -g $connection/connection/id | grep -q linksys && gconftool-2 –recursive-unset $connection ; done

  4. J5
    2008-03-25 at 13:36 EDT

    I was wrong about the mac address part. That is only used for hidden networks but in the case of broadcast network sometimes there are more than one access point with the same ssid so that computers can roam from area to area (for example at conferences or a large office building).As for the connection editor F-8 has it but it is not exposed in the UI like it will be in F-9. In F-8 I found out you can run /usr/bin/nm-connection-editor. Cheers.

  5. 2008-03-26 at 06:02 EDT

    Nobody is using KNetworkManager in F8 or F9 unless they build the experimental NM 0.7 port from source.In F8, knetworkmanager is a dummy package which Requires NetworkManager-gnome and takes care of starting up gnome-keyring-daemon. In F9, there is no knetworkmanager package at all, the dummy package turned out not to be that great an idea (the idea was to provide an upgrade path to the real KNetworkManager, but it also prevents pushing snapshots as a non-default option without causing regressions) and gnome-keyring-daemon is now started through D-Bus activation anyway.We’re looking into making KNetworkManager 0.7 snapshots available for testing at some later point, but right now it’s just not working well enough.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s