Written by Kosimo the 10 May 08 at 13:16.

Ubuntu Brainstorm was updated in January 2009. Since the idea #8326 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #8326 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by nick.colgan the 29 Jan 09 at 03:51.

Add a "scan wireless networks" option to right click context menu of nm-applet.

Add a "scan wireless networks" option to right click context menu of nm-applet.

Written by anabelle the 29 Jan 09 at 15:01.

Since you click to see if you are connected or to connect to a new network it could work similar to OSX.

Once you click it scans for networks and include new results in the lists... no right clicking or anything.

Since you click to see if you are connected or to connect to a new network it could work similar to OSX. Once you click it scans for networks and include new results in the lists... no right clicking or anything.

Written by elbel86 the 1 Feb 09 at 04:19.

wicd is a great alternative to network manager and offers many more options in its gui, including a refresh button. Of course, wicd isn't even in the repos yet, so it could take some time to get it in.

wicd is a great alternative to network manager and offers many more options in its gui, including a refresh button. Of course, wicd isn't even in the repos yet, so it could take some time to get it in.

Written by Endolith the 2 Feb 09 at 07:47.

If there is a problem with Network Manager not showing new networks when they have changed, then fix that problem.

We should not be adding "Refresh" buttons to things that should always be up-to-date. When would you *not* want the list refreshed? Never. If Network Manager were functioning optimally, the button would serve no purpose, so there is no reason to add it.

Let's make things function correctly instead of adding poor workarounds.

If there is a problem with Network Manager not showing new networks when they have changed, then fix that problem. We should not be adding "Refresh" buttons to things that should always be up-to-date. When would you *not* want the list refreshed? Never. If Network Manager were functioning optimally, the button would serve no purpose, so there is no reason to add it. Let's make things function correctly instead of adding poor workarounds.

Written by tchalvakspam the 18 Feb 09 at 20:04.

I'm paraphrasing the solution that one of the developers has implemented (I believe in a version slightly after 0.7) for the purpose of clarifying the brainstorm understanding of what the developers have done to solve the problem.

One of the developers has said that more recent patches to NetworkManager will result in the following behavior:

- When a user interacts with the applet, a rescan will occur immediately if one hasn't within the last 20 seconds. For two minutes thereafter, it will do 20 second interval rescans, then drop to 120 second scans.

- When the applet starts up or the wireless card is re-enabled after being disabled, NetworkManager will do 20 second interval scans for two minutes, and drop back down to 120 second interval scans after that.

So by NetworkManager version 0.7.1 or 0.7.3 or so, any other behavior that doesn't get a rescan as fast as that should be some kind of bug.

I'm paraphrasing the solution that one of the developers has implemented (I believe in a version slightly after 0.7) for the purpose of clarifying the brainstorm understanding of what the developers have done to solve the problem. One of the developers has said that more recent patches to NetworkManager will result in the following behavior: - When a user interacts with the applet, a rescan will occur immediately if one hasn't within the last 20 seconds. For two minutes thereafter, it will do 20 second interval rescans, then drop to 120 second scans. - When the applet starts up or the wireless card is re-enabled after being disabled, NetworkManager will do 20 second interval scans for two minutes, and drop back down to 120 second interval scans after that. So by NetworkManager version 0.7.1 or 0.7.3 or so, any other behavior that doesn't get a rescan as fast as that should be some kind of bug.

Written by hemanth.hm the 8 Mar 09 at 18:27.

WiFi Radar is a Python/PyGTK2 utility for managing WiFi profiles.It enables you to scan for available networks and create profiles for your preferred networks. At boot time, running WiFi Radar will automatically scan for an available preferred network and connect to it. You can drag and drop your preferred networks to arrange the profile priority.

WiFi Radar is a Python/PyGTK2 utility for managing WiFi profiles.It enables you to scan for available networks and create profiles for your preferred networks. At boot time, running WiFi Radar will automatically scan for an available preferred network and connect to it. You can drag and drop your preferred networks to arrange the profile priority.

Written by korin43 the 28 Oct 09 at 19:43.

#6 is nice, but it leaves users feeling like NetworkManager isn't rescanning at all. It would be better if it had some sort of feedback like "Scanning for Networks".

#6 is nice, but it leaves users feeling like NetworkManager isn't rescanning at all. It would be better if it had some sort of feedback like "Scanning for Networks".

Written by tz the 4 Dec 09 at 17:27.

20 seconds is longer than it takes to load most complex web pages, yet that is what everyone is stuck with, but it might actually be 2 minutes.

I would like the option to scan every X seconds when the applet is active, and Y seconds when it is in background. If you constantly change APs, the current settings are too long, but if you are always using the same one they are too short.

Some hardware does bad things (e.g. can't receive or transmit) when you initiate a scan, so you might not want it more frequently, but if I have a good adapter I should be able to unlimit it.

20 seconds is longer than it takes to load most complex web pages, yet that is what everyone is stuck with, but it might actually be 2 minutes. I would like the option to scan every X seconds when the applet is active, and Y seconds when it is in background. If you constantly change APs, the current settings are too long, but if you are always using the same one they are too short. Some hardware does bad things (e.g. can't receive or transmit) when you initiate a scan, so you might not want it more frequently, but if I have a good adapter I should be able to unlimit it.

Written by tz the 4 Dec 09 at 17:48.

Most wireless cards can receive beacons without a scan and most APs ("visible") send them a few times per second. The list returned by the scan includes these - but I think there is a call which returns the result WITHOUT DOING AN ACTUAL SCAN (sending query packets, etc.).

For wireless cards which support this feature, the display list should be updated every second from the list of visible beacons without doing any explicit scan.

Most wireless cards can receive beacons without a scan and most APs ("visible") send them a few times per second. The list returned by the scan includes these - but I think there is a call which returns the result WITHOUT DOING AN ACTUAL SCAN (sending query packets, etc.). For wireless cards which support this feature, the display list should be updated every second from the list of visible beacons without doing any explicit scan.

Written by kuluizemp.openconscience the 1 Dec 10 at 13:05.

we should have a simple and easy way of enable just one wireless network to prevent unwanted mistaken wireless connections and also perhabes a cheak list where you check and uncheck on the wireless connections menu what connections a user want to allow

we should have a simple and easy way of enable just one wireless network to prevent unwanted mistaken wireless connections and also perhabes a cheak list where you check and uncheck on the wireless connections menu what connections a user want to allow

Written by dendron the 28 Feb 09 at 21:10.

The main purpose of NM is to enable mobile users easily connect to mobile networks. There are a number of alternative configuration tools which provide this functionality (I recommend RutilIT).

For wired connections gnome-network-admin is enough, as they usually are not changed very often.

The main purpose of NM is to enable mobile users easily connect to mobile networks. There are a number of alternative configuration tools which provide this functionality (I recommend RutilIT). For wired connections gnome-network-admin is enough, as they usually are not changed very often.

Written by codeslicer the 1 Mar 09 at 15:35.

Instead of using a "non-native" network manager by default, more people should work and improve NM. Canonical should temporary use more resources on NM until most bugs are fixed.

Instead of using a "non-native" network manager by default, more people should work and improve NM. Canonical should temporary use more resources on NM until most bugs are fixed.

Written by urandom the 1 Mar 09 at 17:37.

While Intel's connection manager is currently lacking some features of NM, its design allows it to be quite extensible. This allows for easier additions of new features and easier maintainability.

URL: http://moblin.org/projects/connection-manager

note: Jaunty's repository contains Intel's connection manager under the name 'connman' for anyone who wants to test it right now.

While Intel's connection manager is currently lacking some features of NM, its design allows it to be quite extensible. This allows for easier additions of new features and easier maintainability. URL: http://moblin.org/projects/connection-manager note: Jaunty's repository contains Intel's connection manager under the name 'connman' for anyone who wants to test it right now.

Written by Brayan Habid the 4 Mar 09 at 21:31.

This tool has been the solution for many ubuntu users with internet connection problems. Wicd detects all cable and wifi connections, and avoids the NM problem in ubuntu 8.10

This tool has been the solution for many ubuntu users with internet connection problems. Wicd detects all cable and wifi connections, and avoids the NM problem in ubuntu 8.10

Written by jamesmcm the 16 Mar 09 at 08:35.

It shouldn't be too difficult to build a GTK interface which pipes to one of the CLI tools mentioned. I'd try myself but I don't use a wireless connection and so have never had this problem, so have no idea what CLI tools and what functionality is required.

It shouldn't be too difficult to build a GTK interface which pipes to one of the CLI tools mentioned. I'd try myself but I don't use a wireless connection and so have never had this problem, so have no idea what CLI tools and what functionality is required.

Written by lemmyg the 17 Aug 09 at 08:32.

By default, the value of connect automatically to a network should be disabled, so if you want to automatically connect to a network enable the option manually for each network.

By default, the value of connect automatically to a network should be disabled, so if you want to automatically connect to a network enable the option manually for each network.

Written by Darwin Survivor the 17 Aug 09 at 16:59.

Instead of simply connecting to ANY network with a matching name, the BSSID filter should be enabled by default.

Instead of simply connecting to ANY network with a matching name, the BSSID filter should be enabled by default.

Written by Aielyn the 8 Sep 09 at 12:22.

Either default to "connect automatically", have it off by default, or produce a message with the option upon a successful connection. "Do you wish to connect to this network automatically? Yes/No."

Either default to "connect automatically", have it off by default, or produce a message with the option upon a successful connection. "Do you wish to connect to this network automatically? Yes/No."