TonidoPlug2 DHCP failure

[JacquesV]

After installing ARM Linux I did not get an IP Address from the DHCP Server. I logged in using a serial cable and checked whether dhcpcd command was working. I got an IP-address.

Checked whether the dhcpcd.service was enabled and that is where the problem lies.

Solution:
systemctl reload dhcpcd

Hopefully this helps others with the same problem.

[krabat]

Not quite I fear.

Recent Arch Linux ARM root images are handling the network by systemd-networkd featuring its own DHCP client.

So the fact that you don't get a dhcp lease after boot suggests there's something wrong with systemd-networkd. You may want to check file /etc/systemd/network/eth0.network or output of systemctl status systemd-{networkd,resolved}.service.

Of course, you're free to use whatever tools you want. But if you want to go on using dhcpcd like you do right now you'd better make sure that systemd-networkd gets disabled. Otherwise it might start working for whatever reason yielding two running DHCP client instances.

[JacquesV]

You are correct. Systemd-networkd was also running, but had not received an ip-address.

Content of /etc/systemd/network/eth0.network

$this->bbcode_second_pass_code('', '
[Match]
Name=eth0

[Network]
DHCP=v4

')

systemctl status systemd-{networkd,resolved}.service results in

alarm systemd-networkd[122]: eth0 : DHCP error: client failed: Invalid argument

What could have been the issue? I have disabled systemd-networkd for the time being, but it may be interesting to figure out what causes the problem as it may also be the reason why others have the issues with ssh and dchp on other armv5 devices.

[WarheadsSE]

Check which kernel you have installed, please.

[JacquesV]

using uname -ar shows

Linux alarm 3.1.10-34-ARCH #1 PREEMPT Thu Jul 31 01:56:14 MDT 2014 armv5tel GNU/Linux

[krabat]

It's very likely that the problem is due to the Kernel in use:

Running rather old kernels on Arch Linux ARM, there are frequently problems due to the fact that all the rest of the system is up to date, in particular the Kernel API headers.

So running a more recent kernel will probably solve the issue, maybe the one from package linux-armv5. Unfortunately I seem to be out now as I don't own hardware like this and don't know the details. E. g. I was surprised to see that the root fs as suggested in the installation instructions doesn't seem to comprise a U-Boot package...
Maybe you'll figure out the rest your self or WarheadsSE or someone else can help you out.

Good luck.

[WarheadsSE]

Yup, you need to install linux-kirkwood. Problem should solve itself.

[JacquesV]

Thanks, that did solve the issue.

Maybe someone can adjust the current installation instructions? It's just replacing the ArchLinuxARM-armv5te-latest.tar.gz with ArchLinuxARM-kirkwood-latest.tar.gz. Everything else can stay the same.

[WarheadsSE]

Yeah, assuming you have the necessarily updated uboot (which most new installs will), you should be fine.

[WarheadsSE]

Updated