You are not logged in.

#1 2013-10-24 15:01:56

eriks
Member
Registered: 2013-06-11
Posts: 27

DHCP NAK issue (doesn't accept correct IP, finally times out)

Hello,

since about the same time the Gnome Shell 3.10 update arrived I have huge problems connecting to my wlan router at home (Fritzbox 7170). No problems at other locations, no problems at home with different operating systems.

Authentication seems to work fine, but then the DHCP handshake doesn't work. The log sequence of

Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: NAK: via 192.168.73.2

is repeated endlessly, finally timing out:

Okt 24 16:48:57 twenty dhcpcd[7366]: timed out
Okt 24 16:48:57 twenty dhcpcd[7366]: exited
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> (wlan0): DHCPv4 client pid 7366 exited with status 1
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> (wlan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> Marking connection '...' invalid.
Okt 24 16:48:57 twenty NetworkManager[1161]: <warn> Activation (wlan0) failed for connection 'Ambient Occlusion'
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> (wlan0): deactivating device (reason 'none') [0]
Okt 24 16:48:57 twenty kernel: wlan0: deauthenticating from 00:04:... by local choice (reason=3)
Okt 24 16:48:57 twenty NetworkManager[1161]: <warn> Connection disconnected (reason -3)
Okt 24 16:48:57 twenty NetworkManager[1161]: <info> (wlan0): supplicant interface state: completed -> disconnected
Okt 24 16:48:57 twenty NetworkManager[1161]: <warn> Connection disconnected (reason -3)

Initially it could get it to connect with commenting out

# require dhcp_server_identifier

in /etc/dhcpd.conf

but now even this doesn't help.

Could this be a hardware issue or am I missing something? Maybe the issue is related to those other current  DHCP questions, but I can't see something in common.

Thanks, erik



Some more log content:

Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Config: set interface ap_scan to 1
Okt 24 16:47:17 twenty kernel: wlan0: authenticate with 00:04:...
Okt 24 16:47:17 twenty kernel: wlan0: send auth to 00:04:... (try 1/3)
Okt 24 16:47:17 twenty kernel: wlan0: authenticated
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> (wlan0): supplicant interface state: disconnected -> authenticating
Okt 24 16:47:17 twenty kernel: wlan0: associate with 00:04:... (try 1/3)
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> (wlan0): supplicant interface state: authenticating -> associating
Okt 24 16:47:17 twenty kernel: wlan0: RX AssocResp from 00:04:... (capab=0x411 status=0 aid=2)
Okt 24 16:47:17 twenty kernel: wlan0: associated
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Ambient Occlusion'.
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> dhcpcd started with pid 7102
Okt 24 16:47:17 twenty dhcpcd[7102]: version 6.0.5 starting
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Activation (wlan0) Beginning IP6 addrconf.
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Okt 24 16:47:17 twenty avahi-daemon[1165]: Withdrawing address record for fe80::...... on wlan0.
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting an IPv6 router
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: ipv6rs_sendprobe: sendmsg: Cannot assign requested address
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: NAK: via 192.168.73.2
Okt 24 16:47:17 twenty NetworkManager[1161]: <info> (wlan0): DHCPv4 state changed preinit -> (null)
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: NAK: via 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: NAK: via 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: NAK: via 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: NAK: via 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: NAK: via 192.168.73.2
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: soliciting a DHCP lease
Okt 24 16:47:17 twenty dhcpcd[7102]: wlan0: offered 192.168.73.232 from 192.168.73.2

... repeated endlessly for seconds

Last edited by eriks (2013-10-24 15:02:45)

Offline

#2 2013-11-03 09:36:28

Dieter
Member
From: Germany
Registered: 2005-10-13
Posts: 121

Re: DHCP NAK issue (doesn't accept correct IP, finally times out)

It seems that I have a similar or the same problem here with a Fritz 7170, but on LAN (not WLAN):

dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled)
   Active: active (running) since So 2013-11-03 10:24:22 CET; 5s ago
  Process: 6133 ExecStop=/sbin/dhcpcd -x (code=exited, status=0/SUCCESS)
  Process: 6169 ExecStart=/sbin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
 Main PID: 6170 (dhcpcd)
   CGroup: /system.slice/dhcpcd.service
           └─6170 /sbin/dhcpcd -q -b

Nov 03 10:24:22 arch64-3.rethmeyers.de systemd[1]: Starting dhcpcd on all interfaces...
Nov 03 10:24:22 arch64-3.rethmeyers.de dhcpcd[6169]: version 6.0.5 starting
Nov 03 10:24:22 arch64-3.rethmeyers.de systemd[1]: Started dhcpcd on all interfaces.
Nov 03 10:24:22 arch64-3.rethmeyers.de dhcpcd[6170]: enp2s0: soliciting an IPv6 router
Nov 03 10:24:22 arch64-3.rethmeyers.de dhcpcd[6170]: enp2s0: soliciting a DHCP lease
Nov 03 10:24:22 arch64-3.rethmeyers.de dhcpcd[6170]: enp2s0: offered 192.168.178.25 from 192.168.178.1
Nov 03 10:24:22 arch64-3.rethmeyers.de dhcpcd[6170]: enp2s0: reject NAK via 192.168.178.1
Nov 03 10:24:25 arch64-3.rethmeyers.de dhcpcd[6170]: enp2s0: reject NAK via 192.168.178.1

Any idea to solve this?
This is my - relatively fresh - test system. My arch "prod" system works, but it uses manually edited systemd dhcpcd configuration with "enp2s0@dhcpcd". But I know that the test system worked well on October 5.

Offline

#3 2013-11-03 19:40:01

Dieter
Member
From: Germany
Registered: 2005-10-13
Posts: 121

Re: DHCP NAK issue (doesn't accept correct IP, finally times out)

It seems to be related to activation of "always use the same IP address for this device" in the setup of Fritz 7170. If I switch that off in the Fritz 7170 configuration, dhcpcd works on both systems.

Offline

#4 2013-11-03 19:54:30

regitator
Member
Registered: 2010-08-10
Posts: 26

Re: DHCP NAK issue (doesn't accept correct IP, finally times out)

I had the same problem and found that dhclient works fine.

Last edited by regitator (2013-11-03 19:55:08)

Offline

#5 2013-11-05 11:38:37

eriks
Member
Registered: 2013-06-11
Posts: 27

Re: DHCP NAK issue (doesn't accept correct IP, finally times out)

Thanks for the hints, some days later the problem disappeared without any modifications to my setup (as it was before some months ago).

I'm always trying to spot updates of related packages and to isolate the source, but must have overlooked what could've been responsible. Not easy being no specialist in the interplay of linux network stack components.

Offline

#6 2014-01-25 12:56:21

sthag
Member
Registered: 2014-01-25
Posts: 2

Re: DHCP NAK issue (doesn't accept correct IP, finally times out)

@Dieter Thank you for your hint. That did the trick!

Offline

#7 2014-02-01 07:48:47

akani
Member
Registered: 2014-02-01
Posts: 1

Re: DHCP NAK issue (doesn't accept correct IP, finally times out)

I can confirm, had the same issue with FritzBox 7390 fw Fritz!OS 06.01
Had to delete the entry on my FritzBox so I got a new IP. After that, I added the entry again with the old IP address and now it works like before. I'm wondering if I have to do this again in a few weeks...

Offline

#8 2014-03-09 10:17:52

mlipp
Member
Registered: 2014-03-09
Posts: 1

Re: DHCP NAK issue (doesn't accept correct IP, finally times out)

I can confirm as well. Deleting the entry in the fritz box (7390, Fritz!OS 06.03) fixes the problem. Once it works, it keeps working even if you check the "always assign same IP address" again. As this started with 6.2.1 (6.1.0 worked), I think something is wrong with dhcpcd 6.2.1, although the corresponding bug (https://bugs.archlinux.org/task/38830) was rejected.

Offline

Board footer

Powered by FluxBB