Comment 6 for bug 933378

2012/03/20 08:20:01 :: Autoconnecting...
2012/03/20 08:20:01 :: No wired connection present, attempting to autoconnect to wireless network
2012/03/20 08:20:02 :: trying to automatically connect to...IASTATE
2012/03/20 08:20:05 :: Connecting to wireless network IASTATE
2012/03/20 08:20:06 :: Putting interface down
2012/03/20 08:20:06 :: Releasing DHCP leases...
2012/03/20 08:20:06 :: Setting false IP...
2012/03/20 08:20:06 :: Stopping wpa_supplicant
2012/03/20 08:20:06 :: Flushing the routing table...
2012/03/20 08:20:06 :: Putting interface up...
2012/03/20 08:20:08 :: Running DHCP with hostname arbok
2012/03/20 08:20:08 :: dhcpcd[18081]: version 5.5.4 starting
2012/03/20 08:20:08 ::
2012/03/20 08:20:08 :: dhcpcd[18081]: wlan0: waiting for carrier
2012/03/20 08:20:08 ::
2012/03/20 08:20:08 :: dhcpcd[18081]: wlan0: carrier acquired
2012/03/20 08:20:08 ::
2012/03/20 08:20:08 :: dhcpcd[18081]: wlan0: sending IPv6 Router Solicitation
2012/03/20 08:20:08 ::
2012/03/20 08:20:08 :: dhcpcd[18081]: wlan0: sendmsg: Cannot assign requested address
2012/03/20 08:20:08 ::
2012/03/20 08:20:08 :: dhcpcd[18081]: wlan0: broadcasting for a lease
2012/03/20 08:20:08 ::
2012/03/20 08:20:09 :: dhcpcd[18081]: wlan0: offered 10.24.220.189 from 129.186.1.16 `netreg-1.its.iastate.edu'
2012/03/20 08:20:09 ::
2012/03/20 08:20:09 :: dhcpcd[18081]: wlan0: acknowledged 10.24.220.189 from 129.186.1.16 `netreg-1.its.iastate.edu'
2012/03/20 08:20:09 ::
2012/03/20 08:20:09 :: dhcpcd[18081]: wlan0: checking for 10.24.220.189
2012/03/20 08:20:09 ::
2012/03/20 08:20:10 :: dhcpcd[18081]: wlan0: Router Advertisement from fe80::205:dcff:fe1f:3c00
2012/03/20 08:20:10 ::
2012/03/20 08:20:10 :: dhcpcd[18081]: forked to background, child pid 18104
2012/03/20 08:20:10 ::
2012/03/20 08:20:10 ::
2012/03/20 08:20:10 :: DHCP connection successful
2012/03/20 08:20:10 :: not verifying
2012/03/20 08:20:10 :: Connecting thread exiting.
2012/03/20 08:20:12 :: Sending connection attempt result success
--at this point, wicd says connection failed.

As can be seen, the ipv6 address gets obtained while the ipv4 address is still being verified. This causes dhcdcp to fork to the background, and then wicd gets confused because there isn't an ipv4 address yet.

It appears that the dhcpcd devels don't care about this problem--they have this immature idea that as soon as we start using ipv6, ipv4 will magically go away.

sleeping for 5 seconds is a hack, and personally, I don't have to wait for an extra 5 seconds (look at what technology has done to us--we're all impatient now)

It appears that dhcpcd has an option, noipv6rs that can be called from the command line. I suggest that wicd call dhcpcd with this option to alleviate this problem.