Opened 7 years ago

Closed 7 years ago

#2019 closed defect (worksforme)

Still need WPA support in the UI

Reported by: Zack Owned by: dcbw
Priority: blocker Milestone: Future Release
Component: sugar Version:
Keywords: relnote Cc: Zack
Blocked By: Blocking:
Deployments affected: Action Needed:
Verified: no

Description

Dan says the driver bits for WPA are in place, but we still need to hook it up in the UI. Setting blocker since this is on the release criteria for Trial-2. Is this just sugar, or is it NM too?

Attachments (4)

messages (219.4 KB) - added by Zack 7 years ago.
/var/log/messages
wpa_supplicant.log (63.4 KB) - added by Zack 7 years ago.
/var/log/wpa_supplicant.log
messages.2 (112.0 KB) - added by Zack 7 years ago.
575 /var/log/messages
wpa_supplicant.2.log (65.9 KB) - added by Zack 7 years ago.
575 /var/log/wpa_supplicant.log

Download all attachments as: .zip

Change History (33)

comment:1 Changed 7 years ago by dcbw

just sugar

comment:2 Changed 7 years ago by coderanger

Adding reporter to CC list

comment:3 Changed 7 years ago by coderanger

  • Cc Zack added

Adding reporter to CC list

comment:4 Changed 7 years ago by chiaying.lin

BIOS: Q2C18 , Image:535
Wireless AP: D-link DI624s, DIR635
Set the wireless AP: security mode to open system and WEP.
It shows the wireless AP icon in neighbor mode.
Set the wireless AP: security mode to WPA-PSK.
The wireless AP didn't show up in neighbor mode.-->problem
Using iwlist scanning, it had found out the AP.-->OK

comment:5 Changed 7 years ago by dcbw

  • Resolution set to fixed
  • Status changed from new to closed

WPA support has been committed to master and trial-2 branches.

comment:6 Changed 7 years ago by Zack

  • Resolution fixed deleted
  • Status changed from closed to reopened

Still not working, though this may deserve another ticket.

My XO (including sugar and iwconfig) thought it was connected to my WPA2 AP at home, and DHCP did seem to work, but no packets got routed - I couldn't actually ping the router either.

comment:7 Changed 7 years ago by jg

  • Cc changed from , Zack to Zack
  • Keywords relnote added
  • Milestone changed from Trial-2 to Trial-3

comment:8 Changed 7 years ago by jg

  • Owner changed from dcbw to Zack
  • Status changed from reopened to new

Please try again on 542.

Execute the command 'touch /etc/NetworkManager/log-supplicant' and try again. Please attach the resulting log files /var/log/messages and /var/log/wpa_supplicant.log to this trac ticket, along with the exact manufacturer and model of the access point.

comment:9 Changed 7 years ago by Zack

I'll test 542 shortly.

The access point is a Linksys WRT54g v4 running DD-WRT firmware from www.dd-wrt.com. I use it regularly with FC6, F7, Windows XP and MacOS.

comment:10 Changed 7 years ago by Zack

Just waiting for my usb stick to be unmountable, now... ;)

comment:11 Changed 7 years ago by jg

  • Resolution set to fixed
  • Status changed from new to closed

Changed 7 years ago by Zack

/var/log/messages

Changed 7 years ago by Zack

/var/log/wpa_supplicant.log

comment:12 Changed 7 years ago by Zack

  • Resolution fixed deleted
  • Status changed from closed to reopened

DHCP succeeds, but immediately after, encryption seems to get disabled, making the link useless.

comment:13 Changed 7 years ago by Zack

  • Owner changed from Zack to dcbw
  • Status changed from reopened to new

comment:14 Changed 7 years ago by Zack

Just tried on 551 with q2c25 and it's pretty much the same. I'm currently in some weird state, though, after sugar asked me several times for the WPA2 key. I ended up cancelling the dialog, and now the AP icon is still blinking on the inside, and eth0 isn't showing up in ifconfig.

comment:15 Changed 7 years ago by Zack

Still not working in 557.

comment:16 Changed 7 years ago by jg

What access point type?

comment:17 Changed 7 years ago by marco

Zack can you please test with the latest build and provide informations about the access point type?

comment:18 Changed 7 years ago by marco

  • Resolution set to fixed
  • Status changed from new to closed

I'm marking it as fixed since WPA support is in. If you see the problem again please open a separate ticket with the required informations.

comment:19 Changed 7 years ago by Zack

  • Resolution fixed deleted
  • Status changed from closed to reopened

Jim, I already described the access point above (1 month ago). What more information do you need?

Marco, what do you mean WPA support "is in"? I've been testing it for over 2 months, and it isn't working.

I will try the latest build today, though.

comment:20 Changed 7 years ago by Zack

Doesn't work on 571.

comment:21 Changed 7 years ago by marco

https://dev.laptop.org/ticket/2019#comment:5

That's what I mean with "is in".

comment:22 Changed 7 years ago by kimquirk

  • Owner changed from dcbw to Zack
  • Status changed from reopened to new

Zack, From the attached messages log, it looked like there was a known key (you didn't have to enter it); and it got past most of the WPA stuff, but couldn't get a dhcp IP address.

here is a snippet that was repeated in this log:
Aug 7 20:10:54 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
363 Aug 7 20:10:54 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
364 Aug 7 20:10:54 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
365 Aug 7 20:10:54 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
366 Aug 7 20:10:54 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
367 Aug 7 20:10:54 localhost NetworkManager: <info> Activation (eth0/wireless): access point 'z' is encrypted, and a key exists. No new key needed.
368 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth0 wext /var/run/wpa_supplicant '
369 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was 'OK'
370 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
371 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was 'OK'
372 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
373 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was '0'
374 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 7a'
375 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was 'OK'
376 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA2'
377 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was 'OK'
378 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
379 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was 'OK'
380 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
381 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was 'OK'
382 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
383 Aug 7 20:10:54 localhost NetworkManager: <info> SUP: response was 'OK'
384 Aug 7 20:10:54 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
385 Aug 7 20:10:54 localhost kernel: [ 114.703294] ADDRCONF(NETDEV_CHANGE): msh0: link becomes ready
386 Aug 7 20:10:55 localhost avahi-daemon[1507]: Registering new address record for fe80::217:c4ff:fe03:56da on msh0.*.
387 Aug 7 20:10:56 localhost NetworkManager: <info> msh0: Got association; scheduling association handler
388 Aug 7 20:10:56 localhost NetworkManager: <info> msh0: got association event from driver.
389 Aug 7 20:10:56 localhost NetworkManager: <info> Activation (eth0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'z'.
390 Aug 7 20:10:56 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
391 Aug 7 20:10:56 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
392 Aug 7 20:10:56 localhost NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
393 Aug 7 20:10:56 localhost NetworkManager: <info> eth0: nm_dhcp_manager_begin_transaction():655 started timeout source 0x80ab690
394 Aug 7 20:10:56 localhost NetworkManager: <info> dhclient started with pid 1656
395 Aug 7 20:10:56 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
396 Aug 7 20:10:56 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat
397 Aug 7 20:10:56 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
398 Aug 7 20:10:56 localhost dhclient: All rights reserved.
399 Aug 7 20:10:56 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
400 Aug 7 20:10:56 localhost dhclient:
401 Aug 7 20:10:56 localhost NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
402 Aug 7 20:10:57 localhost dhclient: Listening on LPF/eth0/00:17:c4:03:56:da
403 Aug 7 20:10:57 localhost dhclient: Sending on LPF/eth0/00:17:c4:03:56:da
404 Aug 7 20:10:57 localhost dhclient: Sending on Socket/fallback
405 Aug 7 20:10:57 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
406 Aug 7 20:10:57 localhost NetworkManager: <info> Old device 'eth0' activating, won't change.
407 Aug 7 20:11:01 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
408 Aug 7 20:11:06 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
409 Aug 7 20:11:14 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
410 Aug 7 20:11:34 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
411 Aug 7 20:11:41 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
412 Aug 7 20:11:41 localhost NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it.
413 Aug 7 20:11:41 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled...
414 Aug 7 20:11:41 localhost NetworkManager: <info> eth0: canceled DHCP transaction, dhclient pid 1656
415 Aug 7 20:11:41 localhost NetworkManager: <info> nm_dhcp_manager_cancel_transaction_real(): calling timeout_cleanup
416 Aug 7 20:11:41 localhost NetworkManager: <info> eth0: nm_dhcp_device_timeout_cleanup():175 cleared timeout source 0x80ab690
417 Aug 7 20:11:41 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started...
418 Aug 7 20:11:41 localhost NetworkManager: <info> Activation (eth0) failure scheduled...
419 Aug 7 20:11:41 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
420 Aug 7 20:11:41 localhost NetworkManager: <info> Activation (eth0) failed for access point (z)
421 Aug 7 20:11:41 localhost NetworkManager: <info> Activation (eth0) failed.
422 Aug 7 20:11:41 localhost NetworkManager: <info> Deactivating device eth0.
423 Aug 7 20:11:41 localhost NetworkManager: <info> eth0: will stop DHCP
424 Aug 7 20:11:42 localhost avahi-daemon[1507]: Withdrawing address record for fe80::217:c4ff:fe03:56da on eth0.
425 Aug 7 20:11:42 localhost NetworkManager: <info> SWITCH: no current connection, found better connection 'msh0'.

On the other hand, the WAP Supplicant log refers to a number configuration settings that we probably should also match up the configuration of your WPA router with what we are seeing there to see if there is a mis-configuration.

Can you please do this:

# Upgrade to 575 without backing up data (hold down the X and Square while booting)
# When the laptop comes up; go to the mesh view and click on your WPA AP (don't do anything else just to keep the logs clean and to be able to match up the timestamps between them)
# It should ask you for a password, etc. Please note all the UI interactions so we can try to match those up with the logs.
# When it has had a chance to try to connect (a couple of minutes); then grab the messages and supplicant logs.
# Also, please add as much configuration data as you can get from your AP -- pretty much anything that you could set in its UI.

If we can't figure it out from all that data; then we'll go out and buy the linksys you have and see if we can recreate it here.

it will need to ask you for the password; then we should compare this same log messages and exactly the steps that you took weeks ago, to try to figure out if the problem is in the password or in getting an IP address, or something in between.

Please note what steps the UI goes through so we can match them up to the log messages.

comment:23 Changed 7 years ago by kimquirk

Sorry for the mess at the bottom of the last note. Ignore that last two paragraphs... is there a way to edit notes? it would be nice to format the numbered list as well.

comment:24 Changed 7 years ago by Zack

Sadly, I don't know of a way to edit comments :(

575 is almost done downloading.

comment:25 Changed 7 years ago by Zack

I had to redownload the 575 image, as the first one got corrupted somehow.

I upgraded without backing up as you instructed. I switched to the console to enable wpa-supplicant logging. Then I waited for the XO to connect to the mesh; since it does it automatically, I figured it'd be best to not interrupt it, possibly causing more confusion. I clicked on the AP, then I entered the password, and it began connecting. I left it alone for a few minutes. When I came back, it was connected to the mesh again. Inspecting the logs revealed that DHCP had timed out on the WPA2 connection, but the wpa-supplicant log seemed to show that authentication had succeeded. However, it was dropped right away - "Michael MIC failure detected" messages are followed by a "TKIP countermeasures started" message, and a "State: COMPLETED -> DISCONNECTED" message immediately after that.

I decided to try again. I clicked on the AP, and was prompted for the password again - which I entered. This time, when I came back, sugar thought it was connected - i.e. blinking white outer circle. The logs indicated that DHCP *succeeded*, but the wpa-supplicant log contain the same messages described above. 'iwconfig eth0' now shows 'Encryption key: off'. 'ifconfig eth0' shows the IP address that the AP would have given the XO. So it does succeed, but dies right away.

I will post the /var/log/messages and /var/log/wpa-supplicant that show both attempts.

Changed 7 years ago by Zack

575 /var/log/messages

Changed 7 years ago by Zack

575 /var/log/wpa_supplicant.log

comment:26 Changed 7 years ago by kimquirk

  • Owner changed from Zack to dcbw

comment:27 Changed 7 years ago by jg

  • Milestone changed from Trial-3 to First Deployment, V1.0

comment:28 Changed 7 years ago by kimquirk

  • Milestone changed from First Deployment, V1.0 to V1.1

comment:29 Changed 7 years ago by ffm

  • Resolution set to worksforme
  • Status changed from new to closed

we already have wpa support in sugar. worksforme.

Note: See TracTickets for help on using tickets.