Ticket #2213 (new defect)

Opened 4 years ago

Last modified 3 years ago

Wifi: Can't connect to WPA2 Enterprise network

Reported by: jancona Owned by: Nytowl
Priority: normal Milestone:
Component: Distro Version: unspecified
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

My workplace has a WPA2 Enterprise wifi network. I have been unable to connect to it with my Freerunner, despite using a wpa_supplicant configuration that works for other Linux users.

I've tried this with assorted distros and kernels and it has never worked. My most recent attempt:

  • Flashed FSO testing image from 18-Jan-2009
  • Flashed kernel uImage-moredrivers-GTA02_andy-tracking_f2d78193eae5dccd.bin from http://people.openmoko.org/andy/
  • Created the following wpa_supplicant.conf (which works for other Linux users:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={

ssid="CTCTprivate"
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
identity=""
password="
"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"

}

  • Executed the following commands:

root@om-gta02:~# ifconfig eth0 up
root@om-gta02:~# wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -dd

wpa_supplicant failed to connect. The log I collected is attached.

Attachments

wpa_supplicant.log (8.0 KB) - added by jancona 4 years ago.
Log of wpa_supplicant session
wpa_success.log (102.6 KB) - added by kapiteined 3 years ago.
Log of a succesful connection

Change History

Changed 4 years ago by jancona

Log of wpa_supplicant session

comment:1 Changed 4 years ago by roh

  • Owner changed from julian_chu to Nytowl

maintainer change

comment:2 Changed 4 years ago by cryregarder

comment:3 Changed 3 years ago by kapiteined

I got it working with a "new" kernel: 2.6.29-rc3

We use a RSA token and sometimes you need a few tries, because it start asking for the next token, which the
supplicant can not provide.

So it is not a hardware problem, the openmoko is capable of setting up the connection.

See the attached log wpa_succes.log

Changed 3 years ago by kapiteined

Log of a succesful connection

Note: See TracTickets for help on using tickets.