Comment 6 for bug 58927

I can confirm this bug with the Edgy beta release. I upgraded a Dapper box to Edgy on the day of the beta release, and lost wired Internet connectivity. The fix of manually editing dhclient.conf worked for me.

Some info:

Before applying the dhclient.conf fix, if I set the network card to connect via DHCP, I could not ping either my router or www.google.com, receiving 'unknown host' in response to each.

If I set the network card to a static IP and gave the routers address as gateway, then I got response when ping'ing the router, but still 'unknown host' when ping'ing google.

I then ran 'sudo dhclient eth0', and got this output. I could see that it was sending out DHCPREQUEST's and was receiving 'send_packet: Message too long'. Whether this came from the router or a local process I don't know. dhclient then found a previous and still valid dhcp lease and tried that, ping'ed the router successfully. I could then ping my router, google.com, or ubuntu.com, but I could not get any web pages (including google and ubuntu) in my web browser. I will attach the output of this dhclient run.

Next, I removed "interface mtu" from "request" line in /etc/dhcp3/dhclient.conf as Jarmo suggests. I also did 'sudo ifconfig eth0 mtu 1400'. Then ran dhclient again, it receives a new dhcp lease, Internet connection is fine, I'm now filing this bug report online. I will attach output from the successful dhclient run also, and info about my network card and configuration.

The router I am using is a Q-TEC 584AA ADSL modem & 4 port router. Item no. 13565: http://www.qtec.info/products/hirespics.htm?artnr=13565

The Internet connection that I gained soon disappeared and on running dhclient again I got the message too long error again, I had to change the mtu with ifconfig again and then run dhclient again, to once again successfully get a connection.

The attached file contains outputs from various commands, separated by:

============================================