#5104 HIGH 8.2.0 (: After reboot, you have to enter WEP key every time

[Zarro Boogs per Child]

#5104: After reboot, you have to enter WEP key every time
-------------------------------+--------------------------------------------
   Reporter:  kimquirk         |       Owner:  dcbw                
       Type:  defect           |      Status:  closed              
   Priority:  high             |   Milestone:  8.2.0 (was Update.2)
  Component:  network manager  |     Version:                      
 Resolution:  worksforme       |    Keywords:                      
Next_action:  never set        |    Verified:  0                   
  Blockedby:                   |    Blocking:                      
-------------------------------+--------------------------------------------
Changes (by sjoerd):

  * next_action:  => never set


Comment:

 Looking at the log the interesting bit is the following:

 {{{
 Jun 21 10:41:33 localhost NetworkManager: <info>  dhclient started with
 pid 1678
 Jun 21 10:41:33 localhost NetworkManager: <info>  Activation (eth0) Stage
 3 of 5 (IP Configure Start) complete.
 Jun 21 10:41:33 localhost NetworkManager: <info>  DHCP: device eth0 state
 changed (null) -> preinit
 Jun 21 10:41:33 localhost dhclient: Listening on
 LPF/eth0/00:17:c4:0c:f3:9d
 Jun 21 10:41:33 localhost dhclient: Sending on
 LPF/eth0/00:17:c4:0c:f3:9d
 Jun 21 10:41:33 localhost dhclient: Sending on   Socket/fallback
 Jun 21 10:41:33 localhost dhclient: DHCPDISCOVER on eth0 to
 255.255.255.255 port 67 interval 7
 Jun 21 10:41:35 localhost dhclient: DHCPOFFER from 172.16.16.1
 Jun 21 10:41:35 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255
 port 67
 Jun 21 10:41:36 localhost dhclient: DHCPACK from 172.16.16.1
 Jun 21 10:41:36 localhost dhclient: bound to 172.16.16.11 -- renewal in
 38062 seconds.
 Jun 21 10:41:40 localhost NetworkManager: <info>  Old device 'eth0'
 activating, won't change.
 Jun 21 10:42:18 localhost NetworkManager: <info>  Device 'eth0' DHCP
 transaction took too long (>45s), stopping it.
 Jun 21 10:42:18 localhost NetworkManager: <info>
 nm_dhcp_manager_cancel_transaction_real(): enter, pid 1678
 }}}

 So eth0 was associated, and a dhcp client starts.. The dhcp client
 actually gets an ip, but for some reason NM doesn't notice that and after
 45 seconds assumes that it has time out. Marking the connection as failed
 and on the retry will ask for the security configuration again as it
 somewhat assumes that this is the cause of the failure

-- 
Ticket URL: <http://dev.laptop.org/ticket/5104#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system