From: "Udo A. Steinberg" <reality@delusion.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-net <linux-net@vger.kernel.org>
Subject: mmapped packet socket queueing tcp packets twice?
Date: Tue, 26 Feb 2002 04:54:21 +0100 [thread overview]
Message-ID: <3C7B06ED.8EC55523@delusion.de> (raw)
Hi,
While playing around with packet sockets I stumbled across the following strange
thing:
Feb 26 04:41:56 Kerberos ipacctd: [Slot 4] Incoming TCP - Len: 136 Sum: 72b7 [1014694916.161277]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 5] Incoming TCP - Len: 136 Sum: 72b7 [1014694916.161592]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 9] Incoming TCP - Len: 120 Sum: 81b7 [1014694916.168418]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 10] Incoming TCP - Len: 120 Sum: 81b7 [1014694916.168687]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 12] Incoming TCP - Len: 120 Sum: 80b7 [1014694916.170024]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 13] Incoming TCP - Len: 120 Sum: 80b7 [1014694916.170283]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 15] Incoming TCP - Len: 120 Sum: 7fb7 [1014694916.171432]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 16] Incoming TCP - Len: 120 Sum: 7fb7 [1014694916.171681]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 18] Incoming TCP - Len: 120 Sum: 7eb7 [1014694916.172807]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 19] Incoming TCP - Len: 120 Sum: 7eb7 [1014694916.173094]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 21] Incoming TCP - Len: 120 Sum: 7db7 [1014694916.174245]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 22] Incoming TCP - Len: 120 Sum: 7db7 [1014694916.174499]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 24] Incoming TCP - Len: 120 Sum: 7cb7 [1014694916.176289]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 25] Incoming TCP - Len: 120 Sum: 7cb7 [1014694916.176562]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 30] Incoming TCP - Len: 136 Sum: 6bb7 [1014694916.182037]
Feb 26 04:41:56 Kerberos ipacctd: [Slot 31] Incoming TCP - Len: 136 Sum: 6bb7 [1014694916.182308]
^ ^ ^
| | |
Ring Slot Checksum Timestamp
The program runs under Linux-2.4.17 on machine A and looks for packets of type PACKET_OTHERHOST
coming from and going to machine B. For all incoming tcp traffic of machine B, each packet appears
in the mmapped packet ring twice. The ring slots are adjacent and the checksum is the same.
Only the timestamps differ slightly.
Can someone explain this behaviour?
-Udo.
next reply other threads:[~2002-02-26 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 3:54 Udo A. Steinberg [this message]
2002-02-26 4:45 ` mmapped packet socket queueing tcp packets twice? Udo A. Steinberg
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=3C7B06ED.8EC55523@delusion.de \
--to=reality@delusion.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.