#dhcpcd — Public Fediverse posts

Except it turns out that getting IPv4 address via DHCP takes long enough that my NFS mounts then don't come up.

I ended up writing an exit-hook, documented here: https://github.com/NetworkConfiguration/dhcpcd/issues/100#issuecomment-2429121515

It works, but still feels a little fragile. Perhaps I should attempt converting `/etc/network/if-up.d/nfsmounts` to systemd paradigms....

#debian #linux #dhcp #dhcpcd #isc

Posted a followup on the freebsd-net mailing list about importing #dhcpcd into the #FreeBSD base system: https://lists.freebsd.org/archives/freebsd-net/2024-June/005024.html

So, the #Mikrotik DHCP server accepts multiple leases with the same MAC address, if they send different ClientIDs.

At some point since the last reboot, the config of #dhcpcd changed and used a different algorithm to pick a ClientID, so the machine wasn't receiving the correct address.

Amusingly, #IPv6 saved my ass because SLAAC did pick the correct address.

Bizarre bug of the week: after a reboot, #dhcpcd will try and get a v4 lease, but not get one for minutes (if ever).DHCPv6 is fine. Restarting dhcpcd reliably gets a v4 lease in <1s.

Config and DUID have not changed, but the OS was reinstalled (same OS: Debian Trixie). NIC hardware has changed and will again, soon. So I'm hoping it's just the weird D-Link USB Ethernet thing, which will be replaced with boring Intel NIC.

#Linux #networking

OK, this post from the link I originally shared got it right: https://forums.FreeBSD.org/threads/is-there-a-working-dhcpv6-client-for-freebsd.60168/post-453562

The trick to a working #DHCPv6 client in #FreeBSD seems to be to install #dhcpcd and then add the following lines to /etc/rc.conf:
```
rtsold_enable="YES"
dhcpcd_enable="YES"
```
*Avoid* having an ifconfig_<interface>_ipv6 line in addition to that, and all seems to work well.

@meka Thanks! I tried the regular #dhcpcd package yesterday, and while it did grab a lease it did not seem to respect a reservation. Without having delved too deep there seemed to be some weirdness in the DUID.

I'm certain that I didn't *used* to have to put `noarp` in my /etc/dhcpcd.conf to avoid wifi taking 5 seconds to "wake up" after opening my laptop.

Maybe that means it's finally time to get off my old #netctl + #wpa_supplicant + #dhcpcd setup and look at this new `iwd` thing.

#Parabola #GNULinux #bitrot

I'm certain that I didn't *used* to have to put `noarp` in my /etc/dhcpcd.conf to avoid wifi taking 5 seconds to "wake up" after opening my laptop.

Maybe that means it's finally time to get off my old #netctl + #wpa_supplicant + #dhcpcd setup and look at this new `iwd` thing.

#Parabola #GNULinux #bitrot

The new #RaspberryPi OS (Bookworm) is a much more exciting upgrade than I would expect from them. The switch to #Wayland and #PipeWire from #X11 and #PulseAudio, a #Firefox browser optimised for Raspberry Pis as an option in addition to the dreadful #Chromium, and #NetworkManager as the default now instead of #dhcpcd. Honestly the best thing about this upgrade is their documentation all about it, it's very well written and even I was able to learn all about why they did what they did, and what these changes mean for Raspberry Pis in the long run.

Bookworm Raspberry Pi OS is available for a clean install on all the Raspberry Pis now, but with some certain features missing or coming for Raspberry Pi 3 or older. 4 and 5 should already support all that Bookworm has to offer.

🔗 https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os

I've updated #ArchLinux on my router and on the way it pushed dhcpcd from 9.4.1-1 to 10.0.1-1.
After reboot, I was offline...
Looks like I ran into a bug in #dhcpcd (see https://github.com/NetworkConfiguration/dhcpcd/issues/201). It seems to be an issue when running dhcpcd 10.x to get an IPv6 prefix (PD) over PPP (pppoe).
I didn't have time to investigate the problem yet, so I've just downgraded to 9.x to fix the issue for now.
But that's another example why it's always a good idea to keep old packages around...

@js @anubhav
I have a simple /etc/dhcpcd.exit-hook which reloads #npf on #netbsd when #dhcpcd updates. It should really also check $reason and only do it for IP changes, but this was the "fewest moving parts" option :)

#!/bin/sh

case "$interface" in
lo[0-9]* | tun[0-9]*) exit;;
esac

/etc/rc.d/npf reload

#RFC - #NetBSD systems using #dhcpcd starting/stopping services

(Fishing for thoughts/advice)

I have a few small servers which get Internet via dhcpcd, but also need to run some network services on the same interface. (Various combinations of openvpn, ntp{,date}, samba, syncthing, unifi etc)

Some of these services are "safe to start" without Internet access (syncthing, samba), and others (openvpn) really need to only start after Internet is available (and in some cases shutdown when its down)