As blogged previously BSD systems have issues when you try and change or delete the automatically added subnet route. My patches have now been comitted to NetBSD here and here. If your NetBSD version is 5.99.6 or higher, then you can safely know dhcpcd will work (well, in regard to this anyway).
I’ll try and get them backported to NetBSD-5 and NetBSD-4 in the New Year.
Today I became a NetBSD developer! I’ll mainly be working with dhcpcd in NetBSD and some pkgsrc stuff. I do however have two patches lined up for the main NetBSD src tree- two trivial userland applications for POSIX compat (tabs and a new swtich to unexpand).
this is a small commit with big consequences. Basically it means that dhcpcd will no longer send a default ClientID. You have to specify this behavior. This change has been made so that we mirror the lease credentials sent by the in-kernel DHCP client, the ClientID itself is NOT mandatory for ethernet and it turns out some very badly written DHCP servers do not like ANY ClientID.How does this affect you?
Nothing major - the 4.0 branch gets a fix to send DECLINE messages correctly (basically we forgot to add the IP and ServerID to the message) and the ntp.conf file path is tunable by NTP_CONF=/usr/pkg/etc/ntp.conf in /etc/dhcpcd.enter-hook. 4.99.3 got released as well with more fixes, mainly for 4.0 features which were broken. I’m no longer hopeful about getting IPv6 support in by the end of the year as I don’t see where I’m going to get the time from.
And it was almost entirely painless! Just like my quard core as an issue booting NetBSD MP (I need to have a PS2 keyboard plugged in OR the PS2 port disabled in the kernel), it seems that it doesn’t like ACPI on my server. No matter - ACPI is not essential there. After that hurdle is passed the system booted. I guessed the wrong interface driver for the on board ethernet and my 6to4 tunnel isn’t working- but everthing else appears to be.
Roy's Blog