#2019 BLOC Trial-3: Still need WPA support in the UI
Zarro Boogs per Child
bugtracker at laptop.org
Wed Sep 12 13:24:09 EDT 2007
#2019: Still need WPA support in the UI
----------------------+-----------------------------------------------------
Reporter: Zack | Owner: Zack
Type: defect | Status: new
Priority: blocker | Milestone: Trial-3
Component: sugar | Version:
Resolution: | Keywords: relnote
Verified: 0 |
----------------------+-----------------------------------------------------
Changes (by kimquirk):
* owner: dcbw => Zack
* status: reopened => new
Comment:
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.
--
Ticket URL: <https://dev.laptop.org/ticket/2019#comment:22>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list