Arch Linux

d1x

Member

From: Czech Republic

Registered: 2012-08-27

Posts: 13

DHCPv4 Request Timeout with NetworkManager

Hi there, I'm facing a very weird issue with my DHCPv4.
The thing is that I'm trying to connect PEAP protected WiFi AP. Everything seems going fine until DHCP IP solicitation (authentication, association...etc).
My DHCPv4 request times-out after 45 seconds and always, in exact 46. second I also see '...unhandled DHCP event for interface...'.

It is always like that, I thought that router is somehow slow and returns IP adress in exact 46. second always but very likely, this is not true. Others (with different OS) are able to receive their IP adress quickly.

I also tried to raise the timeout for DHCP but didn't find the way how to do it. I tried adding 'timeout XX' to /etc/dhcpcd.conf, also creating dhcpcd@.service.d/timeout.conf as suggested on wiki but with no effect. Timeout is always 45.
Anyway I don't think that would resolve the issue

The journalctl log is:

led 29 07:58:23 obst4062l NetworkManager[286]: <info> (wlp2s0): supplicant interface state: scanning -> authenticating
led 29 07:58:23 obst4062l kernel: wlp2s0: authenticated
led 29 07:58:23 obst4062l kernel: wlp2s0: associate with 28:94:0f:f9:3d:69 (try 1/3)
led 29 07:58:23 obst4062l NetworkManager[286]: <info> (wlp2s0): supplicant interface state: authenticating -> associating
led 29 07:58:23 obst4062l kernel: wlp2s0: RX AssocResp from 28:94:0f:f9:3d:69 (capab=0x431 status=0 aid=3)
led 29 07:58:23 obst4062l kernel: wlp2s0: associated
led 29 07:58:23 obst4062l NetworkManager[286]: <info> (wlp2s0): supplicant interface state: associating -> associated
led 29 07:58:23 obst4062l NetworkManager[286]: <info> (wlp2s0): supplicant interface state: associated -> completed
led 29 07:58:23 obst4062l NetworkManager[286]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'RaD'.
led 29 07:58:23 obst4062l NetworkManager[286]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
led 29 07:58:23 obst4062l NetworkManager[286]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
led 29 07:58:23 obst4062l NetworkManager[286]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
led 29 07:58:23 obst4062l NetworkManager[286]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
led 29 07:58:23 obst4062l NetworkManager[286]: <info> dhcpcd started with pid 5130
led 29 07:58:23 obst4062l NetworkManager[286]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
led 29 07:58:23 obst4062l dhcpcd[5130]: version 6.6.7 starting
led 29 07:58:23 obst4062l NetworkManager[286]: dhcpcd[5130]: version 6.6.7 starting
led 29 07:58:23 obst4062l NetworkManager[286]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
led 29 07:58:23 obst4062l dhcpcd[5130]: DUID 00:01:00:01:1c:11:c1:9c:34:e6:d7:10:1c:c5
led 29 07:58:23 obst4062l dhcpcd[5130]: wlp2s0: IAID b7:03:3f:1d
led 29 07:58:23 obst4062l NetworkManager[286]: dhcpcd[5130]: DUID 00:01:00:01:1c:11:c1:9c:34:e6:d7:10:1c:c5
led 29 07:58:23 obst4062l NetworkManager[286]: dhcpcd[5130]: wlp2s0: IAID b7:03:3f:1d
led 29 07:58:23 obst4062l dhcpcd[5130]: wlp2s0: soliciting a DHCP lease
led 29 07:58:23 obst4062l NetworkManager[286]: dhcpcd[5130]: wlp2s0: soliciting a DHCP lease
led 29 07:58:24 obst4062l avahi-daemon[564]: Registering new address record for fe80::4a51:b7ff:fe03:3f1d on wlp2s0.*.
led 29 07:59:08 obst4062l NetworkManager[286]: <warn> (wlp2s0): DHCPv4 request timed out.
led 29 07:59:08 obst4062l dhcpcd[5130]: received signal TERM from PID 286, stopping
led 29 07:59:08 obst4062l dhcpcd[5130]: wlp2s0: removing interface
led 29 07:59:08 obst4062l NetworkManager[286]: dhcpcd[5130]: received signal TERM from PID 286, stopping
led 29 07:59:08 obst4062l NetworkManager[286]: dhcpcd[5130]: wlp2s0: removing interface
led 29 07:59:09 obst4062l NetworkManager[286]: <warn> (wlp2s0): DHCP client pid 5130 didn't exit, will kill it.
led 29 07:59:09 obst4062l NetworkManager[286]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 5130
led 29 07:59:09 obst4062l NetworkManager[286]: <info> Activation (wlp2s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
led 29 07:59:09 obst4062l NetworkManager[286]: <info> Activation (wlp2s0) Stage 4 of 5 (IPv4 Configure Timeout) started...
led 29 07:59:09 obst4062l NetworkManager[286]: <info> (wlp2s0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
led 29 07:59:09 obst4062l NetworkManager[286]: <warn> Activation (wlp2s0) failed for connection 'RaD'
led 29 07:59:09 obst4062l NetworkManager[286]: <info> Activation (wlp2s0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
led 29 07:59:09 obst4062l NetworkManager[286]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
led 29 07:59:09 obst4062l NetworkManager[286]: <info> (wlp2s0): deactivating device (reason 'none') [0]
led 29 07:59:09 obst4062l avahi-daemon[564]: Withdrawing address record for fe80::4a51:b7ff:fe03:3f1d on wlp2s0.
led 29 07:59:09 obst4062l NetworkManager[286]: <warn> (pid 5130) unhandled DHCP event for interface wlp2s0
led 29 07:59:09 obst4062l kernel: wlp2s0: deauthenticating from 28:94:0f:f9:3d:69 by local choice (Reason: 3=DEAUTH_LEAVING)
led 29 07:59:09 obst4062l kernel: cfg80211: Calling CRDA to update world regulatory domain
led 29 07:59:09 obst4062l NetworkManager[286]: <warn> Connection disconnected (reason -3)

kostas213

Member

From: Zürich

Registered: 2012-04-11

Posts: 53

Re: DHCPv4 Request Timeout with NetworkManager

Check if commenting out the following in /etc/dhcpcd.conf helps.

# A ServerID is required by RFC2131.
require dhcp_server_identifier

d1x

Member

From: Czech Republic

Registered: 2012-08-27

Posts: 13

Re: DHCPv4 Request Timeout with NetworkManager

Thanks for the reply. Sadly commenting this didn't help Any other idea?

kostas213

Member

From: Zürich

Registered: 2012-04-11

Posts: 53

Re: DHCPv4 Request Timeout with NetworkManager

Not something specific. Check the DHCP article on the arch wiki. I've had a similar problem but I don't remember how I solved it.

d1x

Member

From: Czech Republic

Registered: 2012-08-27

Posts: 13

Re: DHCPv4 Request Timeout with NetworkManager

Thank you kostas213. I went through all Wirless Network, DHCP, NetworkManager and I finally found how to solve this.
The problem was in dhcpcd.conf. I had to change:
duid -> clientid in /etc/dhcpcd.conf