Gutsy cannot get IP using DHCP on wired network

[Chris Eagan]

1. Start up the machine
2. Log in
3. Network Manager keep trying to get an IP address but fails.

Output found in daemon.log:

dhclient: socket: Address family not supported by protocol - make sure
dhclient: CONFIG_PACKET (Packet socket) and CONFIG_FILTER
dhclient: (Socket Filetering) are enabled in your kernel
dhclient: configuration!

$ uname -a
Linux crystal 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux

NetworkManager reports:
NetworkManager: <information> eth2: Device is fully supported using driver 'skge'.

I apologize for the terse log info as I am typing it all from a different computer. If there are any full lags that would be useful, please request and I will find a way to transfer them.

[James "Doc" Livingston (jrl)]

I'm also seeing this, with 2.6.22-7.

Running ifup manually on the interface causes the same errors from dhclient, so it's not NetworkManager specific

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the full contents of '/var/log/daemon.log'? Thanks in advance.

Doc - are you using the same wireless driver, 'skge', as the original reporter?

[Chris Eagan (ceagan)]

Here is my daemon.log file. For awhile, I had things working with using a static ip address but switching from static to dynamic seemed to kill static which is the reason for the delay in responding to your request.

[Brian Murray (brian-murray)]

Just to be absolutely clear. eth3 is your wired interface and eth2 is your wireless interface is that correct?

[Chris Eagan (ceagan)]

Actually, eth2 is the gigabit wired network and eth3 is 100 megabit. The computer does not have a wireless card.

Today I was able to get dhcp to assign me an address. I have been updating gutsy since I reported this bug so it is possible that an update fixed it.

[Brian Murray (brian-murray)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

[Arthur (iegik)]

how to fix this bug without internet? Because i can`t get network configuration via dhcp3-client

[Chris Eagan (ceagan)]

I believe that I booted from an older livecd that did work, then I mounted
my hard disk in that running instance and used chroot to go into the hard
disk filesystem and ran apt-get from there.
Something like this:

mount /dev/sda1 /mnt/mydrive
cp /etc/resolv.conf /mnt/mydrive/etc/resolv.conf
chroot /mnt/mydrive
apt-get update
apt-get upgrade