Bug 89959 - dhclient(8): dhcp: ip length 314 disagrees with bytes received 534
Summary: dhclient(8): dhcp: ip length 314 disagrees with bytes received 534
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 6.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-05 03:50 UTC by robert
Modified: 2022-09-04 20:57 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description robert 2005-12-05 03:50:02 UTC 
"ip length 314 disagrees with bytes received 534" message diplays whenever
renewing dhcp lease with router:

DHCPREQUEST on rl0 to 255.255.255.255 port 67
ip length 314 disagrees with bytes received 534.
accepting packet with data after udp payload.
DHCPACK from 192.168.0.1
bound to 192.168.0.4 -- renewal in 1013730269 seconds.

However, I do not seem to have symptoms others have reported in bsd forums,
like unable to ping yahoo.com. I can ping and dig is working.

Fix: 

unknown. IPv6 suspected. Please contact me to request further system info.
How-To-Repeat: 1. reboot (then see: 'dmesg -a |grep disag' output) or,
2. run: # /sbin/dhclient on your nic
Comment 1 Gleb Smirnoff freebsd_committer freebsd_triage 2005-12-12 09:53:02 UTC 
Responsible Changed
From-To: freebsd-bugs->brooks

To maintainer.
Comment 2 Brooks Davis freebsd_committer freebsd_triage 2006-01-14 17:59:54 UTC 
State Changed
From-To: open->feedback

It seems fairly unlikely this has anything to do with dhclient.  I'm 
betting on a driver bug or something with bpf.  Does this still occur in 
6-STABLE?  What network interface and dhcp server are you using?
Comment 3 Brooks Davis freebsd_committer freebsd_triage 2006-05-13 05:07:29 UTC 
State Changed
From-To: feedback->open

I've actually got a router/AP that produces this output on both 
wired and wireless networks so I'll get to looking at it eventually. 
My guess is that it's a buggy behavior in the device and we'll just 
end up wanting to turn this printout off.
Comment 4 Brooks Davis freebsd_committer freebsd_triage 2007-01-15 17:20:04 UTC 
State Changed
From-To: open->feedback

I think this has been fixed in 6-STABLE and HEAD as of bpf.c revs 
1.2.2.4 and 1.7 respectivly (6.2-RELEASE contains this revison). 

Can you confirm this? 

To check the revision of the bpf.c used in your dhclient use: 

ident /sbin/dhclient | grep bpf 

Thanks, 
Brooks
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2007-06-14 07:30:51 UTC 
State Changed
From-To: feedback->closed

Feedback timeout (> 4 months).
Comment 6 Brooks Davis freebsd_committer freebsd_triage 2007-06-14 15:11:37 UTC 
State Changed
From-To: closed->open

I thought I'd fixed this, but discoved I hadn't and forgot to switch the 
state out of feedback so re-open this.
Comment 7 Brooks Davis freebsd_committer freebsd_triage 2014-06-17 14:57:40 UTC 
I've had not time for this so return to the pool.  This problem persists for a subset of NICs.  It appears to be mostly harmless, but should be better analyzed.
Comment 8 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:51:16 UTC 
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"