On 09/19/2012 12:12 AM, Dan Williams wrote:
then we need some
supplicant debug logging instead, which is roughly:
1) mv /usr/sbin/wpa_supplicant /
2) killall -TERM wpa_supplicant
3) /wpa_supplicant -dddtu
4) retry the connection and let it fail
5) grab the supplicant debug output (careful, may
On 09/20/2012 04:40 PM, Frank wrote:
On 09/19/2012 12:12 AM, Dan Williams wrote:
then we need some
supplicant debug logging instead, which is roughly:
1) mv /usr/sbin/wpa_supplicant /
2) killall -TERM wpa_supplicant
3) /wpa_supplicant -dddtu
4) retry the connection and let it fail
5) grab the
On 09/19/2012 12:12 AM, Dan Williams wrote:
On Tue, 2012-09-18 at 14:45 +0800, Frank wrote:
Here's the wpa_supplicant.conf file:
ap_scan=1
network={
ssid=SSID Name
proto=WPA2
key_mgmt=WPA-EAP
pairwise=CCMP
group=CCMP
eap=PEAP
phase1=peaplabel=0
Here's the wpa_supplicant.conf file:
|ap_scan=1
network={
ssid=SSID Name
proto=WPA2
key_mgmt=WPA-EAP
pairwise=CCMP
group=CCMP
eap=PEAP
phase1=peaplabel=0
phase2=auth=GTC
identity=User name
password=Password
}
|
I can use wpa_supplicant to connect the
On Tue, 2012-09-18 at 14:45 +0800, Frank wrote:
Here's the wpa_supplicant.conf file:
ap_scan=1
network={
ssid=SSID Name
proto=WPA2
key_mgmt=WPA-EAP
pairwise=CCMP
group=CCMP
eap=PEAP
phase1=peaplabel=0
phase2=auth=GTC
identity=User name
