[Edgy dhclient regression] error: Message too long

I get the same problem in one of the places I connect to.

Interestingly this bug isnt on dapper.

I too had the same problem with D-Link DES-1008D switch. I didn't have this problem with Linksys WRT54G.

I read earlier about removing the "interface-mtu" parameter but doing only that didn't do any good. The mtu must have been wrong because when following bertoldic's instructions it started working.

30/09/06 Still unpatched!!!

I took the liberty to change the bug title, in the hopes that it might get some more attention (as a regression). hope it was okay.

I marked earlier bug #58927 about the same issue as duplicate of this as this had one duplicate already and the description/title is more concise. Anyway, I'll repeat some info the other bug:

The bug is actually in the crappy router which reports too low value for interface-mtu (64 in all reports I have seen). Why this worked fine in dapper is because dhclient did not ask for interface-mtu then and the default value is used instead in that case, and the network works fine. Then dhclient.conf was changed to include "interface-mtu" query in Debian and the package was imported to Ubuntu post-dapper. Most of the routers cannot be fixed to return correct interface-mtu, so the dhcp should not ask for it by default. This very same "bug" was actually fixed once already (from the changelog):

dhcp3 (3.0.1-1ubuntu4) hoary; urgency=low
  * Revert changes to debian/dhclient.conf, apparently at least some DHCP servers supply broken interface-mtu information, so this isn't safe to enable without broader testing (Ubuntu #8241)

I hope it will fixed again before edgy :)

Hi there,
I have encountered this bug as well while connecting to a public WAP. I am using the madwifi-ng drivers from their subversioning trunk, because of Bug #63886.

Bug #63886 also has information relating to my system, but if more info is needed please let me know.

I did not have chance to search for this bug while I was at the access point (because I did not have Internet access :)

Attached is the output from my '/etc/init.d/networking restart' command.

I'm not sure I understand your work around 100%, but I'll see what I can dig up from some man pages first.

It would be nice to this bug resolved.

Flagged for edgy.

I'm not sure whether we can ignore the MTU provided by the router and still be standards-compliant; it might be preferable in the long term to ignore obviously bogus values like 64 (probably anything <576).

The safest thing for now would be to revert to the old behaviour, even though it reopens other bugs.

 dhcp3 (3.0.4-6ubuntu6) edgy; urgency=low
 .
   * remove the interface-mtu parameter from dhclient.conf, there are still to
      many dhcp servers out there supplying a wrong mtu. (closes malone #61989)

This is still an issue in Ubuntu 9.04 Beta

I'm behind a router that serves as a DHCP server.
I boot the live CD Ubuntu 9.04 Beta, and I have no connection. The mtu is set to 64 and dhcp failed.
I have to:
- "sudo vi /etc/dhcp3/dhclient.conf" and remove "interface-mtu,"
- "sudo ifconfig eth0 mtu 1500"
- then go to NetworkManager Applet and disable and enable back networking

Changing it in the NetworkManager Applet from automatic to 1500 has no effect.

Please don't change the status of Fixed bugs from old releases. In the future please open a new bug. What you're describing is from bug 352779 which has already been fixed.