no network connection after reboot

[hp4]

I'm running archlinuxarm (most recent update status) on a raspberrypi, dhcpcd version 6.4.3-1

in many cases after a reboot I can't access the (headless) Raspberry Pi via network. Systemlog is full with the messages shown below. I've written a script which automatically starts a reboot after half an hour with no network connection. After this second reboot everything works fine. The dhcp-server is running on a dsl-router (Fritzbox).

I'm saving /var/lib/dhcpcd/dhcpcd-eth0.lease (last dhcp-offer from fritzbox ?) after every reboot, which seems to be identical in all cases independent of the problem.

Any idea what's going wrong or how to locate the problem?

Why is dhcpcd trying to connect to 192.168.0.254? This is not a valid ip-address in the address-space of the fritzbox, therefore the NAK is plausible.

I'm not an expert for dhcp, is there any debugging-option when starting dhcpcd ?

---------------------------------------------------------------------------------
hundreds of the following entries in the syslog:

Jan 1 01:10:51 mars dhcpcd[157]: eth0: soliciting a DHCP lease
Jan 1 01:10:51 mars dhcpcd[157]: eth0: offered 192.168.178.9 from 192.168.178.1
Jan 1 01:10:52 mars dhcpcd[157]: eth0: NAK: from 192.168.0.254
Jan 1 01:10:52 mars dhcpcd[157]: eth0: soliciting a DHCP lease
Jan 1 01:10:52 mars dhcpcd[157]: eth0: offered 192.168.178.9 from 192.168.178.1
Jan 1 01:10:52 mars dhcpcd[157]: eth0: NAK: from 192.168.0.254
Jan 1 01:10:53 mars dhcpcd[157]: eth0: soliciting a DHCP lease
Jan 1 01:10:53 mars dhcpcd[157]: eth0: offered 192.168.178.9 from 192.168.178.1
Jan 1 01:10:53 mars dhcpcd[157]: eth0: NAK: from 192.168.0.254

[sdjf]

Not sure about debugging, but you might want to look at the active profile in /etc/netctl. Does the ethernet profile there match your setup? You may need to use a different one, taken from /etc/netctl/examples.

[WarheadsSE]

If this is the latest official tarball, this might be on systemd-networkd

[cloph]

Ignoring the address from the different network block:

I also had DHCP problems after I reinstalled arch/replaced the SD-Card. For some reason the DHCP failed because I was using a different hostname right from the start instead of the default. But there I always got the NAK, at least 4-5 reboots/restarts of network didn't make a difference.

After changing the hostname in the Fritzbox-Webinterface for the known leases DHCP worked fine again all the time.

I also found notes about some people having to uncomment = disable
$this->bbcode_second_pass_code('', 'require dhcp_server_identifier')
in /etc/dhcpcd.conf - but in my case this didn't make a difference.

So while it might not help the original poster, hopefully this is useful to people visiting the thread in the months and years to come when having similar DHCP problems in combination with Fritzbox.