From: "David S. Miller" <davem@redhat.com>
To: schuma@gaertner.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: PF_PACKET: packets out of order
Date: Mon, 08 Oct 2001 16:43:37 -0700 (PDT) [thread overview]
Message-ID: <20011008.164337.31640467.davem@redhat.com> (raw)
In-Reply-To: <200110082332.BAA16370@aunt.gaertner.de>
In-Reply-To: <200110082332.BAA16370@aunt.gaertner.de>
From: Joerg Schumacher <schuma@gaertner.de>
Date: Tue, 9 Oct 2001 01:32:16 +0200 (MET DST)
Hi!
NeTraMet v44b10 uses pcap(3) and complains about timestamps jumping
backwards. Looks like a PF_PACKET socket doesn't receive the packets
in the correct order. Some timestamps from a "tcpdump -tt":
RX: 1001465480.175100 [...]
TX: 1001465480.179111 [...]
RX: 1001465480.177315 [...]
^^^^^^
TX: 1001465480.180514 [...]
RX: 1001465480.179706 [...]
The receive packets are in order, as are the transmit packets.
Anything which absolutely _requires_ all TX and RX packets to
be in precise order, should really be fixed not to have such
a weird restriction.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-08 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 23:32 PF_PACKET: packets out of order Joerg Schumacher
2001-10-08 23:43 ` David S. Miller [this message]
2001-10-09 1:43 ` Joerg Schumacher
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=20011008.164337.31640467.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schuma@gaertner.de \
/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.