[Edgy Regression] Dhclient error on Realtek 8169/8110: send_packet: Message too long

Bug #63209 reported by Niels tijssen
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When I installed the edgy eft distribution from the CD with the default kerne, my network card was not recognized anymore.

I did work out of the box with the dapper drake distribution, which installed successfully on my box. I could configyure the NIC and I could have had access to the internet.

I have an onboard Realtek 8169/8110 gigabit ethernet card.

After installation I cannot connect to the internet and my NIC could not be configured by using the control panel.

[summary was: Install edgy eft breaks compatibility Realtek 8169/8110 NIC]

Revision history for this message
Niels tijssen (tijssenn) wrote :

Here is some update.

Eth0 (my network card) is still having problems. When is is configured with a static ip, the card shows up in the KDE system information and I can ping my router and my ISP dns server.

When I configure eth0 with a dynamic ip using the control panel, eth0 could not obtain a DHCP lease, this did not happen with dapper.

Revision history for this message
Niels tijssen (tijssenn) wrote :

Here is some output from ifconfig and and the dhcp deamon. It looks like kubuntu can not contact my router to obtain a dhcp lease. Note when I boot my PC in windows it works without problems.

tijssenn@tijssenn-desktop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0C:76:E7:80:41
          UP BROADCAST RUNNING MULTICAST MTU:64 Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2480 (2.4 KiB) TX bytes:1368 (1.3 KiB)
          Interrupt:201 Base address:0x2f00

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

tijssenn@tijssenn-desktop:~$ sudo dhclient eth0
Password:
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:0c:76:e7:80:41
Sending on LPF/eth0/00:0c:76:e7:80:41
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Message too long

description: updated
Revision history for this message
towsonu2003 (towsonu2003) wrote :

I took the liberty to change the title to reflect the latest info you provided. hope it's okay. I cannot further triage this bug though (I don't have enough experience).

However, thanks to the latest info you provided, I found this report in bug # 61989
[quote]
When I try to connect to internet dhclient says to me send_packet:"Message too long".

I've found the problem and also the solution.
The problem is the wrong MTU parameter it is normally set to 64 while it should be around 1500.
Besides the file /etc/dhcp3/dhcp.conf has a wrong parameter "interface-mtu".

So the solution is remove the parameter "interface-mtu" in the file /etc/dhcp3/dhclient and set the parameter MTU to 1500 doing ifconfig eth0 mtu 1500.

Many users in Italy have this problem with their router,please see www.ubuntu-it.org in the section related to edgy.
[/quote]

please see if it helps. if it does help, pls add a comment to that bug. In that case, I will mark this as a dupe of bug # 61989.

thanks

Revision history for this message
Niels tijssen (tijssenn) wrote :

Hi

Thanks for the workaround, this was a nasty one since I did not have a clue that it was a bothed DHCP config.

It works and I am now upgrading my box to stay current.

Revision history for this message
towsonu2003 (towsonu2003) wrote :

Thanks for the comment. I'm closing this one, the work will go on in he other bug report :)

Changed in linux-source-2.6.17:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.