Pretty catchall title but I fugure these snippets may save you a lot of pain.
Assuming you have hurdled the trouble of identifying your wifi, getting the module to load and sorting your firmware out then the last step is actually connecting with it.
Sometimes this bit is the most frustrating with several of the GUIs being sub-Beta quality at best.
Time to trust to the console - you only need a few basic commands (AS ROOT)
will tell you which ethx to use (eth0, eth1, eth2, whatever). You may have wlan0 or ath0 but you'll be used to that by now if you use an odd distro :-). WRITE DOWN THE DEVICE NAME because you'll feel silly wasting an hour after a 'no wireless extensions' error occurs on your LAN NIC. :-)
If you're using WEP then have a care about your binary & hex.....iwconfig accepets hex codes but some APs probably use binary...oh what fun.
If you are using 128bit WEP then you need a 26 element hex key in this format USE THE HYPHENS ---
iwconfig eth0 key 0123-4567-8901-2345-6789-0123-45
64 bit WEP uses 10 hex elements in this format
iwconfig eth0 key 0123456789
set your essid (in this case 'linux') thus,
iwconfig eth0 essid linux
Maybe you wanna set that to ANY if you're not sure.....
Lastly fire off a
Remember that a simple iwconfig with no device parameter WILL NOT give you any details of an assigned IP address...check that with ifconfig or any of the sweet monitoring apps like wmifinfo
if all else fails
man iwlist; man iwconfig