mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Oliver Falk" <oliver@linux-kernel.at>
To: <linux-kernel@vger.kernel.org>
Subject: Dhcp: Ip length 44 disagrees with bytes received 46.
Date: Sun, 26 Dec 2004 07:31:14 +0100	[thread overview]
Message-ID: <200412260631.iBQ6VZTk027678@pils.linux-kernel.at> (raw)

Hi lkml!

Maybe it's not good to ask the lkml, but since there are so many experts
here, it makes sense to me.

I have a dhcp-server running with 2.6.10 (had it running with
2.6.{1,2,3,4,5,6,7,8,9} as well) and the dhcpd logs all the time:

<snip>
Dec 26 07:22:11 brain dhcpd: ip length 44 disagrees with bytes received 46.
Dec 26 07:22:11 brain dhcpd: accepting packet with data after udp payload.
Dec 26 07:22:11 brain dhcpd: ip length 44 disagrees with bytes received 46.
Dec 26 07:22:11 brain dhcpd: accepting packet with data after udp payload.
Dec 26 07:22:51 brain dhcpd: ip length 44 disagrees with bytes received 46.
Dec 26 07:22:51 brain dhcpd: accepting packet with data after udp payload.
Dec 26 07:22:51 brain dhcpd: ip length 44 disagrees with bytes received 46.
Dec 26 07:22:51 brain dhcpd: accepting packet with data after udp payload.
Dec 26 07:23:11 brain dhcpd: ip length 44 disagrees with bytes received 46.
Dec 26 07:23:11 brain dhcpd: accepting packet with data after udp payload.
Dec 26 07:23:11 brain dhcpd: ip length 44 disagrees with bytes received 46.
Dec 26 07:23:11 brain dhcpd: accepting packet with data after udp payload.
</snip>

Now my question; Is this normal? Where does it come from? Why does it
happen? For me this seems strange...

FYI. I have the server running with the above mentioned kernel and Fedora
Core Development Tree (dhcpd 3.0.1).

Any help is welcome!

Best regards,
 Oliver


             reply	other threads:[~2004-12-26  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-26  6:31 Oliver Falk [this message]
2004-12-26 16:58 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200412260631.iBQ6VZTk027678@pils.linux-kernel.at \
    --to=oliver@linux-kernel.at \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®