With kernel 2.6.12 bogus UDP packets for dhcp

Bug #18891 reported by Xavier Poinsard on 2005-07-12
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Medium
Fabio Massimo Di Nitto

Bug Description

When I try to boot with linux-image-2.6.12-3-686, the dhcp sequence fails to get
an IP.

The dhcp server (a Debian sarge server) is reporting the following :
dhcpd: DHCPDISCOVER from XXX (mymachine) via eth0
dhcpd: DHCPOFFER on YYY to XXX (mymachine) via eth0
dhcpd: bogus UDP packet length: 308

If I use a 2.6.10 image everything works fine.

Ante Karamatić (ivoks) wrote :

What ethernet card are you using?

Xavier Poinsard (xpoinsard) wrote :

Extract from lspci :
Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet
(rev 02)
        Subsystem: Dell: Unknown device 8126

Ante Karamatić (ivoks) wrote :

Interesting... Well, I can't confirm this, even tough I have few gigabit
broadcoms, but they are all on hoary. 100mbit broadcom works ok on breezy. I
would say this isn't an ethernet card problem. Could you investigate a bit more?
How does dhclient behaves while getting IP? Could you send output?

Chuck Short (zulcss) wrote :

What does dmesg say after you try dhcp?

Xavier Poinsard (xpoinsard) wrote :

dhclient output :

Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:0b:db:05:36:2a
Sending on LPF/eth0/00:0b:db:05:36:2a
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Xavier Poinsard (xpoinsard) wrote :

dmesg reports nothing special :
...
[4294696.147000] tg3.c:v3.31 (June 8, 2005)
[4294696.147000] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11
(level, low) -> IRQ 11
[4294696.172000] eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)]
(PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:0b:db:05:36:2a
[4294696.172000] eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0]
WireSpeed[1] TSOcap[1]
[4294696.172000] eth0: dma_rwctrl[763f0000]
...
[4294700.703000] NET: Registered protocol family 17
[4294702.442000] tg3: eth0: Link is up at 100 Mbps, half duplex.
[4294702.442000] tg3: eth0: Flow control is off for TX and off for RX.
...
[4294736.128000] device eth0 entered promiscuous mode
[4294738.885000] device eth0 left promiscuous mode
[4294746.017000] NET: Registered protocol family 10
[4294746.017000] Disabled Privacy Extensions on device c0332aa0(lo)
[4294746.018000] IPv6 over IPv4 tunneling driver
[4294756.338000] eth0: no IPv6 routers present
[4294929.811000] Disabled Privacy Extensions on device f69e3000(sit0)
[4294940.389000] eth1: no IPv6 routers present

I have a gigabit that uses the tg3 driver and it gets an ip via dhcp with no
problems,
but it's working at 100Mb. Could you try to force the switch to go down to 100Mb
(without
touching the card) and see if that could be the problem?

Fabio

Xavier Poinsard (xpoinsard) wrote :

as you can see in the log provided, I am already connected at 100 Mbits.
worse it seems that I have the same dhcp problem with my wireless connection,
but I can't confirm since I can't access the logs of my ISP.

Chuck Short (zulcss) wrote :

I use the same module at work using dhcpcd I dont have the same problem.

Regards
chuck

Xavier Poinsard (xpoinsard) wrote :

bugs seems fixed with 2.6.12-4

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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