2012-11-08T13:07:58ZFluxBBhttps://bbs.archlinux.org/viewtopic.php?id=152229Think I have identified the issue now.

Neither dhcpcd or dhclient is sending the host name properly to the DHCP server anymore. I had an IP address reserved in the DHCP server for my host and after deleting this reservation my host is able to acquire an IP (dynamic) address. The reserved static address could never be acquired.

Conclusion: dhclient and dhcpcd is not sending the host name as before, causing the DHCP server to get stuck (while waiting for the host name) whenever a NIC with a reserved IP address is requesting an IP address.

Downgrading the dhcp clients has not yet worked, so there might be some underlying component that is causing the problem. ath5k? systemd?

]]>https://bbs.archlinux.org/profile.php?id=637582012-11-08T13:07:58Zhttps://bbs.archlinux.org/viewtopic.php?pid=1189707#p1189707Maybe I was a bit too fast to jump to a conclusion.

After doing some testing it seems like my "new" Arch setup is crashing my DHCP server. I can lease once, but if I suspend the machine and wake it up, the new DHCP request/negotiation crashes the DHCP server.This did not happen before the upgrade (for SW versions see original post).

Anyone else who has experienced this?

The DHCP "server" is a DLink DIR-600 B2 2.05, which has worked flawlessly until this upgraded machine came along.

]]>https://bbs.archlinux.org/profile.php?id=637582012-11-04T20:02:21Zhttps://bbs.archlinux.org/viewtopic.php?pid=1187750#p1187750I'll move it to dustbin for you.]]>https://bbs.archlinux.org/profile.php?id=272892012-11-04T17:33:16Zhttps://bbs.archlinux.org/viewtopic.php?pid=1187649#p1187649Nevermind, 5 mintues after submitting this post my DHCP server crashed. After a reboot everything works accordingly.

Can I delete this thread or do I label it as "Solved"?

]]>https://bbs.archlinux.org/profile.php?id=637582012-11-04T14:57:47Zhttps://bbs.archlinux.org/viewtopic.php?pid=1187554#p1187554Upgraded my system today from Gnome 3.4 to 3.6 (and systemd was updated as well), and since then acquiring an IP address using DHCP does not work anymore.I am using IPv4 only internally, but neither dhclient or dhcpcd manages to get an IPv4 address. It seems like IPv6 is priority one, and beacuse there is no IPv6 DHCP server available NetworkManager aborts the whole setup process.

To make sure that IPv6 should not be considered, I have changed "method" in NetworkManager to "Ignore" for IPv6.

I have also tried to downgrade NM to 0.9.6.0 from 0.9.6.4 (since that version works on another, not upgraded, machine), without any result.

Also switched dhclient to dhcpcd, without any result.

The machine is a "pure" systemd machine.

DHCP works for other devices in the network.

Versions:systemd 195-2NetworkManager 0.9.6.4isc-dhclient-4.2.3-P2

I have no issues on a system where following versions are running:systemd 189-4NetworkManager 0.9.6.0dhcpcd 5.6.2