From: Ronald <ronald645@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Association broken with wpa_supplicant
Date: Fri, 16 May 2008 09:31:24 +0200 [thread overview]
Message-ID: <482D384C.30807@gmail.com> (raw)
I'm not using the latest wireless (2.6.25) but I also have trouble using
wpa_supplicant (same error as you). After *a lot* of trying, I figured
this out, to associate I do this:
/sbin/wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf.2 -B
/bin/sleep 5
/usr/bin/killall wpa_supplicant
/sbin/wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
/bin/sleep 5
/sbin/ifconfig wlan0 192.168.2.252 netmask 255.255.255.248
/sbin/route add default gw 192.168.2.254
The contents of wpa_supplicant.conf.2 is:
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
fast_reauth=0
network={
bssid=00:1B:2F:A9:48:E8
ssid="Chimera"
psk="<<scrubbed>>"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
}
The contents of wpa_supplicant.conf is:
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
fast_reauth=0
network={
bssid=00:1B:2F:A9:48:E8
ssid="Chimera"
psk="<<scrubbed>>"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
}
Trying to associate directly with only wpa_supplicant.conf won't work,
*only* after I used wpa_supplicant.conf.2. Furthermore, I never made a
bugreport as I thought that it would be an error in wpa_supplicant...
I hope this helps you in any way =)
Ronald
next reply other threads:[~2008-05-16 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 7:31 Ronald [this message]
2008-05-16 8:19 ` Association broken with wpa_supplicant Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2008-05-15 22:30 Michael Buesch
2008-05-16 14:57 ` Johannes Berg
2008-05-16 14:58 ` John W. Linville
2008-05-16 18:16 ` Michael Buesch
2008-05-16 18:19 ` Kolekar, Abhijeet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=482D384C.30807@gmail.com \
--to=ronald645@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.