Arch under SmartOS can't successfully obtain DHCP leases

kinghajj · 2015-09-03 20:54:57

I built a new server a couple months ago and have been using SmartOS as the hypervisor. Initially, my Arch VMs worked just fine. After some point (sorry--I can't recall exactly when), however, they all failed to obtain DHCP leases from my router. I've tried other distros--CentOS, Debian, etc.--and none of them have this problem, only Arch. I gave up for the time being, but just tried again today using the latest Arch ISO and SmartOS platform, but with the same result: all attempts to obtain a DHCP lease time out. Does anyone have an idea why this might be happening? Has there been a recent change to the virtio NIC driver, for instance, that may be causing it to be incompatible with SmartOS's implementation?

rsmarples · 2015-09-04 13:02:33

Which DHCP client software are you using in Arch?

kinghajj · 2015-09-04 16:55:47

Just dhcpcd. I suppose I'll try systemd-networkd and netctl, in case either of those happen to work.

alphaniner · 2015-09-04 17:55:37

I'm pretty sure netctl also uses dhcpcd, probably systemd-networkd too. The only other client I know of is dhclient. There is an Arch package in [extra], but it's probably not installed on the iso live system. Maybe running dhcpcd with verbose or debug output would provide some clues.

rsmarples · 2015-09-04 18:23:46

OK, so I can support dhcpcd (just not on Arch as I use NetBSD and Gentoo atm) as I wrote it

Typically dhcpcd will fail to work with older routers due to dhcpcd defaulting to using a duid instead of a clientid and stating that we support the Rapid Commit option.
These are newish DHCP settings and fully RFC compliant - however some old DHCP servers don't like this for reasons of their own.

So in /etc/dhcpcd.conf, comment out the duid directive, uncomment the clientid directive and comment out the rapid commit option.
dhcpcd should then start working. If it still fails to work, the chances are that dhcpcd itself is not to blame and the fault lies elsewhere.

Let me know how it goes for you!

kinghajj · 2015-09-04 18:26:01

root@archiso ~ # dhcpcd -d -4 eth0
eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
DUID 00:01:...
eth0: IAID 25:...
eth0: delaying IPv4 for 0.9 seconds
eth0: soliciting a DHCP lease
eth0: sending DISCOVER (xid 0xdc4d526c), next in 4.8 seconds
eth0: sending DISCOVER (xid 0xdc4d526c), next in 8.2 seconds
eth0: sending DISCOVER (xid 0xdc4d526c), next in 15.2 seconds
eth0: sending DISCOVER (xid 0xdc4d526c), next in 32.3 seconds
timed out
dhcpcd exited

I also just tried various old ISOs (July, June, May, and January of this year), and none of them succeeded as well.

kinghajj · 2015-09-04 18:28:33

rsmarples wrote:

OK, so I can support dhcpcd (just not on Arch as I use NetBSD and Gentoo atm) as I wrote it
Typically dhcpcd will fail to work with older routers due to dhcpcd defaulting to using a duid instead of a clientid and stating that we support the Rapid Commit option.
These are newish DHCP settings and fully RFC compliant - however some old DHCP servers don't like this for reasons of their own.
So in /etc/dhcpcd.conf, comment out the duid directive, uncomment the clientid directive and comment out the rapid commit option.
dhcpcd should then start working. If it still fails to work, the chances are that dhcpcd itself is not to blame and the fault lies elsewhere.
Let me know how it goes for you!

Haha, that works! Specifically, I commented out duid and uncommented clientid. I didn't change rapid commit though. My router isn't old, it's an AC1900WRT running OpenWRT, but I guess it doesn't support duid still? Anyway, thanks for the help! Now I can use my favorite distro on here again.

rsmarples · 2015-09-04 18:36:38

Well, how have you setup the OpenWRT router for DHCP? Is it fairly stock?
I have a couple myself, but just as AP's - the DHCP server I use is ISC dhcpd on my NetBSD powered Edge Router Lite which is my central hub.

EDIT: You may want to file an OpenWRT bug about this as well.

Last edited by rsmarples (2015-09-04 18:37:11)

Arch Linux

#1 2015-09-03 20:54:57

Arch under SmartOS can't successfully obtain DHCP leases

#2 2015-09-04 13:02:33

Re: Arch under SmartOS can't successfully obtain DHCP leases

#3 2015-09-04 16:55:47

Re: Arch under SmartOS can't successfully obtain DHCP leases

#4 2015-09-04 17:55:37

Re: Arch under SmartOS can't successfully obtain DHCP leases

#5 2015-09-04 18:23:46

Re: Arch under SmartOS can't successfully obtain DHCP leases

#6 2015-09-04 18:26:01

Re: Arch under SmartOS can't successfully obtain DHCP leases

#7 2015-09-04 18:28:33

Re: Arch under SmartOS can't successfully obtain DHCP leases

#8 2015-09-04 18:36:38

Re: Arch under SmartOS can't successfully obtain DHCP leases

Board footer