fix handling of previously created ad-hoc networks

[Jack Lecou]

Use case:

I use a proxy server running on an iphone to get mobile internet. This requires creating an ad-hoc network on my laptop, then joining the iphone to it. I'd like to easily connect/recreate this network whenever no other known networks are available.

The problem:

Once created, if I leave the new ad hoc network as "connect automatically", network manager sometimes uses it even when [preferred] regular networks are in range.

If I turn off "connect automatically", there doesn't appear to be a way to easily recreate the network: it doesn't seem to reliably show up in the menu of available networks, and although the connection is selectable under the dropdown in the "Create New Wireless Network" dialog, if anything other then "New..." is selected there, the "Create" button remains inactive.

How it should work:

Previously created ad-hoc networks should always be available in the connection menu, either included with the scan results, or at the bottom of the menu (maybe replace the "Create New Wireless Network..." item with a "Create a Network >" submenu containing previously configured networks along with a "new..." item.)

Alternatively (or additionally) there ought to be a way to prioritize the list of known/previously-used networks, so that network manager would never attempt to use the "iphone" network unless NO other [known] networks were available.

[Jack Lecou (jackl)]

As an experiment, I've left the ad hoc network I created last week in its default state (i.e., "automatically connect", etc.).

Despite regularly being in locations where known infrastructure networks are available, network manager so far ALWAYS goes with the ad hoc network after resuming from suspend. I have to manually select the infrastructure network every time. (Annoyingly, scan results and reconnecting seems to be extra slow and glitchy after the ad hoc network has been activated. But that's a different bug. Maybe in the driver.)

Network manager certainly ought to have enough data at this point to keep track of my manual corrections and build up a priority list. Perhaps the trouble is that ad hoc networks are by definition always available, so network manager sees this and connects instantly after resume, before external scan results have even had a chance to filter in?