On Thu, 2009-07-16 at 00:07 -1000, Joel Roth wrote: > Hmm. It does work _now_, provided the interface is UP. Yes, it has to be UP. > That may be thanks to having a recent kernel with the latest > compat-wireless drivers. > > I was also misled by assuming iwlist's 'ap' option would > provide useful information. It hasn't for many years, really. Oh well, not much we can do about it. > To summarize what I now know, the steps to follow for basic > wireless connectivity to an unencrypted network would be: > > 1. kernel and driver setup - use compat-wireless > > 2. set wireless interface to UP > > ifconfig <interface> up > > 3. find available networks using > > iw dev <interface> scan > or > iwlist <interface> scan This isn't strictly necessary if you know the SSID already. > 4. connect to a network using > > iw dev <interface> connect <SSID> The old way of doing this would be iwconfig wlan0 essid <SSID> But as long as you don't need ancient hardware, you're probably better off using iw. You can also use iw dev <interface> connect -w <SSID> if you run a current git snapshot, and it will wait for the connection to be established or fail and print the status. Oh and if you're just doing this on the command line you can do iw <interface> connect <SSID> (i.e. leave out the "dev"), but please don't script it that way :) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
