Re: NM 0.9.8 doesn't realise that DHCP worked

[Pavel Simerda <psimerda redhat com>]

----- Original Message -----
> From: "Bastien Nocera" <hadess hadess net>
> Heya,
>
> I'm using rawhide on my laptop, and I can get the network to work in
> sporadic 30 second bursts, as NM doesn't realise that dhclient got an
> IP
> address:
> Feb 26 13:35:16 sirocco dhclient[1177]: bound to 192.168.0.24 --
> renewal in 17055 seconds.
> Feb 26 13:35:59 sirocco NetworkManager[576]: <warn> (wlan0): DHCPv4
> request timed out.

Looks wrong. 

> Feb 26 13:35:59 sirocco NetworkManager[576]: <info> (wlan0): canceled
> DHCP transaction, DHCP client pid 1177
> Feb 26 13:35:59 sirocco NetworkManager[576]: <info> Activation
> (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
> Feb 26 13:35:59 sirocco NetworkManager[576]: <info> Activation
> (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
> Feb 26 13:35:59 sirocco kernel: [  211.996738] wlan0:
> deauthenticating from f4:ca:e5:94:aa:60 by local choice (reason=3)
> Feb 26 13:35:59 sirocco NetworkManager[576]: <info> (wlan0): device
> state change: ip-config -> failed (reason 'ip-config-unavailable')
> [70 120 5]
>
> Any ideas what might be causing this? I get the same problem on wired
> and wireless networks.

Not really. Did you check if it isn't a selinux issue? We changed quite a lot of stuff but DHCP was always 
working for me. We didn't modify the dhclient action binary for time, so it might be theoretically somewhere 
in the dhcp plugin.

Btw you said the network works for you sometimes? Does that mean dhclient sets up the address directly? That 
would suggest it's not running NM's dhcp action script at all but instead runs the default one.

Maybe also try to killall dhclient (and NetworkManager) before you test once again.

Pavel