wpa_supplicant: how do I know what I did wrong
Hi everybody,
I am trying to connect to the network at Purdue University using the instruction here http://purduelug.org/?page_id=11 I follow section 4 of it: I was able to use wpa_cli list_networks to see the network, but unable to connect to the network. I don't know where things go wrong. Can you guys give me a clue or at least show me which log files should I look at to find out what went wrong? Thank you. |
Run the wpa_supplicant daemon in the foreground (no -B option), with increased verbosity (-dd). Example:
wpa_supplicant -w -dd -c/etc/wpa_supplicant.conf -Dwext -iwlan0 Then, sit back and watch the fun. The messages may appear to be cryptic, but read them carefully or post here and hopefully we can help you. |
Hi,
I would suggest that you look at 'Configuring your network in Slackware'. Great wiki by Alien_Bob. This link and others are available from 'Slackware-Links'. More than just SlackwareŽ links! |
Thank you, guys. I'll try these advices and report the progress.
|
You can also use wicd from the extra/ directory (of the Slack installation CD, or find a copy in the mirrors). It's a GUI tool to setup you wireless connection.
|
Hi,
'wicd' is referenced in the link that I provided in the above post. Alien_Bob has covered network setups to the 'T'. Great Wiki! |
I tried the wikie of Alien_Bob. But I stuck. Here are some of the outcome.
this is my rc.inet1.conf Quote:
Quote:
Quote:
Do you have any idea what I should do next? (I haven't tried the Wicd because I want to to it by these configuration files to find out how it work and things like that. Thank you for all your help and relies. |
Another thing,
when I run the command /etc/rc.d/rc.inet1 stop /etc/rc.d/rc.inet1 start I get the outcome Quote:
|
This is what happens now:
It seems to me like there's a problem when wpa_supplicant tries to login on the network. This setup requires that you provide a username and password before you get a encryption key (but you already knew that) Something goes wrong when wpa_supplicant tries to do that. After failing to get a wireless connection, the slackware scripts try to get an IP by running dhcpcd, just in case the carrier detection is wrong. Since there really isn't a link, you cannot get an IP. -- The difficult part is that the encryption key for the network has to be obtained after a login. Most WPA encrypted networks work with a passphrase, and either you have configured the right passphrase, or not. If you want to find out what goes wrong, take 2Gnu's suggestion. Kill the wpa_supplicant that is running after bootup, and execute the wpa_supplicant command that 2Gnu gave in his post above. You should be able to kill wpa_supplicant with this command: Code:
wpa_cli terminate Code:
ifconfig eth1 up edit: if the wpa_supplicant command is successfull, go to another console and run the following command, after that you should be able to connect to the internet (at least until reboot): Code:
dhcpcd eth1 |
Thank you. I'll try that.
|
I tried WiCD and failed (mysteriously, and I don't know why)
I ran the command wpa_supplicant -i eth1 -D wext -c /etc/ssl/certs/ca.crt and here is the outcome I got Quote:
Is there any "special" thing about those certificate, or is there any thing else I can do here? Thank you for your advice so far. |
Quote:
Quote:
Code:
-----BEGIN CERTIFICATE----- I also see that that website lists Code:
phase1="peaplabel=0" Eric |
For sure, Alien_Bob, you pointed out my mistake.
I used the right command which was wpa_supplicant -i eth1 -D wext -c /etc/wpa_supplicant.conf (I only posted it here wrong) About the certificate, I did copy and pasted that exact part and saved it as /etc/ssl/certs/ca.crt the line ca_cert in the file wpa_supplicant.conf did point to that file |
And now, I am running into another problem.
There are two networks available as I can see, one is "PAL2.0", the other is "erdos". And even though I want to connect to PAL2.0, whenever I run the command Quote:
Quote:
(And before I ran the wpa_supplicant command, I did run Quote:
What should I do? PS: After a few more tries, it stopped kicking me out, but the problem remained the same. By the suggestion of Alien_bob, I also tried "peaplable=1" and "peaplabel=0" They both gave the same result. I do suspect about the certificate, by reading through the instruction at purduelug.org, it seems to me that this is something I can acquire independently with the network administration. Do you know anywhere else where I can get it? Thank you. |
The first error that appears in the output from wpa_supplicant you posted is: (when you ran wpa_supplicant yourself on the command line, without the "-B" option)
Quote:
I've found the instructions for setting up Windows XP, and it seems the needed certificate is a root certificate that is widely distributed. I've found a certificate with the same name as the expired one (and the name mentioned in the XP howto) on my slackware 12.2 + KDE4 installation. It is located in the file /usr/share/apps/kssl/ca-bundle.crt The name is Thawte Premium Server CA. If you have KDE installed, look if you have the certificate bundle. Try to list that as your "ca_cert=" entry in wpa_supplicant.conf |
All times are GMT -5. The time now is 04:46 PM. |