For wpa_supplicant.conf you can change the contents to what I posted. The other files just need the lines changed or added if not there. For instance ...


... ifcfg-wlan0 already includes an entry , so you would just make it look like . Same for channel. If it's not there just add it.


If you mean the modules where not loaded it means it's missing an entry and alias in /etc/modprobe.conf:
If after adding this (and a reboot) it *still* doesn't work, then run 'depmod' just to make sure it knows where to find the necessary modules. Note a reboot isn't really necessary but at least you know it's working then.


I'm sorry but talking about errors doesn't work for me and my ESP is low today so guesswork you won't get from me. Post exact error messages could help.


Never heard of "AKIP" and your scan output doesn't show it using "AKIP" either.

sorry bro, i still really don't get what you meant by wedging in an entry with the MAC and channel. i can't find anything in the man pages for either wpa_supplicant or wpa_supplicant.conf about MACs or channels. is there just something i'm missing here? also as regards madwifi and wpa_supplicant.conf, i found this in the man pages, but i don't understand it. is this part of the problem?

" madwifi driver for cards based on Atheros chip set (ar521x)
(http://sourceforge.net/projects/madwifi/) Please note that you
will need to modify the wpa_supplicant .config file to use the
correct path for the madwifi driver root directory (CFLAGS += -I../madwifi/wpa line in example defconfig). "


so right now, when i run wpa_supplicant, it seems to run fine without throwing any errors, and scans like this over and over:

Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
49 6e 74 65 72 77 65 62 Interweb
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 10
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b19 len=8
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 10
No suitable AP found.
Setting scan request: 5 sec 0 usec

i'm not sure whether that's a good thing or not. it doesn't seem to be authenticating to the AP even though it's present. wrt boot errors, i wasn't expecting you to guess stuff, i was just telling you it doesn't show up at boot. AKIP is what the guy who maintains the network told me it uses - he specifically said it was "AKIP, not TKIP" - is he wrong?

L

I mean "add or change the line containing (mac or channel)"


Yes and no. The MAC of the AP is called a "BSSID". From your previous output the line to add to the "Interweb" section of wpa_supplicant.conf is "bssid=00:1b:5b:46:4e:51". The channel is the frequency: 2.417 GHz means channel 2. So add a line "CHANNEL=2" to ifcfg-wlan0.


I don't know. Let's see if we can get it to work first and revisit that if it fails.


This shows you've got the kernel modules loaded OK (just check, will you), the interface up and wpa_supplicant running. Good.


It's good since it shows it works. But because you haven't entered the right auth method and passphrase in wpa_supplicant.conf it can't authenticate. Ask the the guy who maintains the network to give you the full authentication details by e-mail or any other digital means (like on a USB stick so you can copy and paste). If he starts mumbling about certificates or something make sure he gives you complete instructions how to get or make those. While you're at it ask him if he set up MAC address or any other restrictions that could keep you from authenticating. When you talk to him try to go over the authentication procedure. Maybe take notes if that helps.

hey, sorry about the delay - couldn't get to a machine where i was. i've modified the files like you said (sorry about the confusion there) and now when running wpa_supplicant, i get a huge output that seems to be the machine authenticating via EAP or something to the AP - ends like this:

RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8b19 len=8
Received 913 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 10
0: 00:1b:5b:46:4e:51 ssid='Interweb' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
selected based on RSN IE
Already associated with the selected AP.

this repeats, so i think it might be working now. if it is, you're all total legends and i seriously owe you all, especially you unSpawn. i'm gonna go test it - results later.

L

okay, being slightly too optimistic here. with no ethernet connected, i get the same output, but still can't ping anything or bring up anything via HTTP. anyone got any ideas?

L

I'd like to remind you that by now you know which components are needed for Wireless to work. You know how to check them by using lsmod, network and wireless-tools and by reading logs. Without posted output I can do anything with nor proof of you having completed the authentication stuff from my last reply there isn't much I can do.

wrt proof of the auth stuff, i figured i had the right details in the configs anyway, since it was able to authenticate to the AP like you see it doing in #19. the guy gave me a note that just said "WPA2 - AKIP - Interweb" and the passphrase, so there's not exactly a whole lot of help in that direction. do you want me to hassle him again, or does the fact that it could connect change things?

as for output, it's intermittent. sometimes it scans over and over again like this:

Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
49 6e 74 65 72 77 65 62 Interweb
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 10
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b19 len=8
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 10
No suitable AP found.
Setting scan request: 5 sec 0 usec

and sometimes it authenticates, and that output is way too long to post unless you need it. it goes through the process of an EAPOL handshake fine, giving COMPLETED or SUCCESS messages as it goes, hangs for ages at this line:

EAPOL: startWhen --> 0

and then loops like this:

RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8b19 len=8
Received 677 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 10
0: 00:1b:5b:46:4e:51 ssid='Interweb' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
selected based on RSN IE
Already associated with the selected AP.

however when this happens, i still can't access the Web or ping anything. please tell me specifically what else you want, cause i honestly can't tell just from what i already know - i still don't know how these components hang together or what my problem is, much less how to fix it, i've only been running Linux for a couple of months.

No, it shows it can associate with the AP. Think of it as you being allowed to approach the Customs booth. The next stage would be a proper inspection of your passport. At this point you didn't hand over your passport but a greasy note which reads "OMG t3H iz meh PaS5pprt0!!!!!!!" which the official rejects. (Preposterous, I know)


As I said before I don't know "AKIP" so unless somebody else jumps in with more help we need all the info we can get. And if you pay for access then asking for details is not harassment: you're *entitled* to it (FCOL).

ah, they're not the same thing then - my bad. in that case i'm gonna go see if i can find the guy; i'll be back with all the data i can get.

wrt AKIP, it's looking like you're probably right, since i can't find any spec documents for that algo or even any reference to it in forums, on Google, etc. which makes me wonder whether my tech guy actually does know any more than i do. any case i'm on it, i still haven't given up and i'll be back with info ASAP.

L

the email from the guy isn't much more verbose than the note... it says:

Network Name: Interweb (00:1b:5b:46:4e:51)
Channel: 2 (2417MHz)
Security: WPA2-PSK (AES)
Password: [redacted]
802.11g
DTIM Period 3
DHCP

is there any other data you can think of he didn't include? he said it's fine to come back and ask for more.

L

Should do. Read up the wpa_supplicant docs, there's an example about WPA2-PSK, figure it out, test, check with iwconfig if it fails, test again in debug mode, and post the relevant bits if you can't make it work including output/errors. You're almost there :-]

just so you know, i'm on it. i'll let you know how it goes.

L

okay. been through all the examples in the man page, plus the example config files in /usr/share/doc and the extended example wpa_supplicant.conf file. there's no one example that corresponds to WPA2-PSK as far as i can tell, but from what i understand according to the extended example, my wpa_supplicant.conf is good to go for that setup. i've been through it making sure, and adding in some default parameters, anyway. it looks like this now:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
eapol_version=1
ap_scan=1
fast_reauth=1
update_config=1

network={
disabled=0
ssid="Interweb"
bssid=00:1b:5b:46:4e:51
priority=10
scan_ssid=1
proto=WPA RSN
key_mgmt=WPA-PSK
auth_alg=OPEN SHARED
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
peerkey=1
psk=[redacted]
}

still the same result though, i can associate but not authenticate. two things i can think of: am i meant to be using dhclient, and also there's this in the wpa_supplicant man page:

madwifi driver for cards based on Atheros chip set (ar521x)
(http://sourceforge.net/projects/madwifi/) Please note that you
will need to modify the wpa_supplicant .config file to use the
correct path for the madwifi driver root directory (CFLAGS +=
-I../madwifi/wpa line in example defconfig).

i've pointed this out before, but i just have no idea what the last sentence in brackets means. there is no example called defconfig.

L

I gave you some links before. If you read them it would show WPA2 is the successor to WPA and the main difference is it uses AES instead of TKIP. Wrt Wpa_supplicant, in the config it uses other values for proto, pairwise (and group AFAIK).


Good move. Else I'd never seen the "peerkey" one.


Try this minimal config section: ...if it works fill in details later. Also, in the links I gave you before, one example looks like this: ...so if mine doesn't work you could always try variations. Whatever happens, if it doesn't work, check with your diagnostic iw.* tools and wpa_cli in debug mode what goes on. I remind you I've used wpa_supplicant before, but since I b0rked my laptop I'm doing this kinda blindfolded so I have to rely on you to provide information I can do something with. Also if you've been doing everything religiously from the commandline there would be no need to check related configs, but if you used any GUI to reconfigure say network settings, those UIs may have changed things and then it *would* be good to verify settings are still OK.


Any DHCP client should do be it dhclient, pump or dhcpcdcdc-wotsitcalled. Once activated the client will wait in the background polling for a DHCP lease but you won't get one until you're auth'ed properly by the AP.


This assumes you did not install Wpa_supplicant and Madwifi as RPMs but as tarballs. If the ar521x condition applies to you, then you should probably try that. The CFLAGS part means that you'll 0) have to get tarballs (the source code) for both Madwifi Wpa_supplicant, 1) configure and install Madwifi, then 2) go to the directory where you unpacked Wpa_supplicant in, and 3) add the line "CFLAGS +=-I../madwifi/wpa" to the ".config" file. The ".config" file AFAIK only gets created if you run "./configure" so you'll need to do that first or add the line to the "config.in" file or the "Makefile". Also note that you need to substitute the path, since "../madwifi/wpa" means it's expecting the madwifi source dir in the same dir the wpa_supplicant source dir is in.


Could submit that as a bugtrack item then.

ok, i'm gonna try various different network blocks. i might be a couple days - my painkillers are screwing me over right now, which is why i didn't reply for a while. i promise i'm not going anywhere.

L