WPA does not work at all.

[ffm]

Steps to reproduce: 1. Boot laptop 2. Try to connect to a WPA network. 3. Press OK.

then, nothing happens. Dialog does not even disappear

[ffm]

Oh, and If I press it enough times, sugar freezes. (also occurs in ship.2)

[ffm]

It should be noted that after attempting to conect to a WPA network, all attempts to connect to other networks fail, even if the other networks use WEP or no encryption.

[ffm]

Oops, seems to work in latest build.

[chiaying.lin]

I tried it with image 649. It seems not work.

[cscott]

Reports are that this is still broken in ship.2. Does this work in joyride?

[cscott]

marcopg: c_scott: I don't have WPA networks to test with here, but if bemasc does some testing I can help tracking it down

[bemasc]

Under Joyride-1403, connection to my WPA access point fails. The access point is a Linksys WRT54G running WPA PSK-TKIP (also known as WPA-1). The name of the network is "bluesteel"; I recommend searching through the logs for that string.

[bernie]

Ricardo points out this workaround:

http://wiki.laptop.org/go/OLPC_Ship.2_Software_Release_Notes#Network_Connectivity

Tomeu seems to have recently worked on keydialog.py lately, which is the module that is said to contain the bug.

Could any of you please look into it? At tonight's IRC meeting this bug was suggested as critical for Update.1.

[HoboPrimate]

Could this be simillar to #5044 (with WPA-PSK)?

[bemasc]

To be clear, the symptoms are very slightly differentfrom #5044. In #5044: "After entering the password pressing Enter or choosing OK doesn't dismiss the dialog."

In this case, pressing OK does dismiss the dialog. The WPA AP's circle blinks for many seconds, and eventually fails. Normally, after failure, the dialog reappears again.

[marco]

This is not #5044, looking at shell.log (#5044 is fixed in joyride).

[rwh]

WPA works for me in joyride 1371 with a D-Link DIR-635 (FW 1.09w). See logs for details.

I removed ~/.sugar/default/nm and /etc/wpa_supplicant/wpa_supplicant.conf and rebooted before taking these logs.

[bemasc]

/var/log/messages showing WPA failure from Sugar on joyride-1403

[bemasc]

shell.log showing WPA connect failure in Sugar on joyride-1403

[bemasc]

NetworkManager --no-daemon log showing failure on 1403.

[bemasc]

Added new failure logs.

[carrano]

I updated the information on the wiki regarding a workaround to connect to an encrypted AP, if the user interface fails.

Please check: http://wiki.laptop.org/go/WPA_Manual_Setting

[dcbw]

As a data point, build 650 works just fine for me with a B2-1 and a Linksys WRT54GC which is based on the broadcom chipset. This is, of course, after commenting out the sigchld handler from /usr/bin/sugar-shell

[marco]

bemasc, ffm, can you please give this another try on 666?

[ffm]

works for me on latest joyride.

[MrDomino]

It appears as though the most recent update.1 build (667) broke WPA entirely---I can't connect through either the neighborhood view or the WPA.sh shell script.

[ffm]

Still works flawlessly in joyride and 653.

[bemasc]

Still broken in 671.

[jg]

Tested in current joyride and update.1..