Skribent: Simon Hobson Dato: Til: dng Emne: Re: [DNG] netman: support for wlan1, wlan2, ... and eth1, eth2,
.... and new systemd's naming scheme
tilt! <tilt@???> wrote:
> I think the entire issue "how do i scan for available networks" is badly implemented in wicd *and* in Windows WiFi Connections (which are two WiFi connection assistants i know from practice).
For completeness, this is how OS X (version 10.8) does it.
If using the WiFi icon on the menubar (the quickest and easiest way to do it), the menu has (from the top) :
- WiFI: On, which periodically changes to WiFi: Looking for networks...
- Turn WiFi Off
---
Then a list of visible WiFi SSIDs which updates dynamically. Each entry has a "padlock" icon if secured, and a signal strength icon. If already connected to a network, there's a "tick" icon before it's name.
---
- Join Other Network... which goes to a dialog where you can type in an SSID and select security options (and which has a "Show Networks" button which brings up another dialog with a list of SSIDs.
- Create Network... which allows the creation of an ad-hoc network
- Open Network Preferences which does just that.
If doing it though the preferences panel, there a panel with status at the top (shows connected network, IP address, and a button to turn WiFi off (or on if it's off). Below that is a drop down menu of SSID which more or less mirrors the menu bar menu.
An Advanced button brings up a dialog that (amongst other things) shows a list of all remembered networks, which can be ordered to set the priorities for which network to join if there is more than one visible.
Something to be aware of.
Over on another forum (IIRC) there was a discussion related to viewing networks. The person concerned lives in Singapore and their housing density is such that the list can be hundreds of networks long - in fact, so long that before it's finished displaying and the user has chance to select their network, it's started scanning again !
Worst I've personally experienced was when sent to Monaco (really, really not as glamorous as it sounds !), where I could see something like 40 SSIDs - and of course, a handful of them were on "wrong" channels so as to maximise interference to other networks (eg on Ch3 so it overlaps Ch1 and Ch6).
So whatever system is built, it needs to allow for those unfortunate people with massive SSID lists to deal with.