timpalpant wrote:Just reverted to dhcp-3.0.6 and it works perfectly now. Looks like it's an issue with net-misc/dhcp-3.1.0, I suggest you mask it and I'm going to file a bug.

Great work. That worked perfectly for me.

Examining my emerge.log, it looks like I was previously running dhcp-3.1.0_rc2 quite happily, and that the bug was introduced when it went to dhcp-3.1.0 after I synced emerge on July 20. Might want to note that in your bug report.

Thanks for your help everyone. It's great when a forum works as well as this.

Sorry, the LiveDVD is affected as well. I figured out how to use net-setup, but both the old LiveDVD version and the newest one are affected.

Though I somehow managed to get the system to use DHCP directly after emerging to the newest version. After a reboot, this doesn't work anymore, sadly enough.

edit: I did downgrade to version 3.0.6 of DHCP - still no go. Sometimes a manual use of "dhclient eth1" manages to get a lease from the server, but as of yet I haven't figured out what the conditions for that to happen are."dhcping -v -s 192.168.0.1" gets a valid response from the server as soon as I've set the IP adresse manually - but dhclient usually doesn't.

Okay, some more weird stuff: DHCP doesn't work 95% of the time when I'm using a wired connection.

It works all the time via wireless but only halfway. I'm connecting to the network, credentials are fine, I get my IP, I can ping the router but cannot connect to the internet. It seems as if the DHCP client doesn't fetch / set the gateway and/or the DNS server. When I set the gateway / DNS-IP manually, everything works fine.