From: "David S. Miller" <davem@redhat.com>
To: hps@intermeta.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sequence of IP fragment packets on the wire
Date: Thu, 03 Oct 2002 03:53:52 -0700 (PDT) [thread overview]
Message-ID: <20021003.035352.132919623.davem@redhat.com> (raw)
In-Reply-To: <anh7es$mpl$1@forge.intermeta.de>
From: "Henning P. Schmiedehausen" <hps@intermeta.de>
Date: Thu, 3 Oct 2002 10:51:08 +0000 (UTC)
as far as I can see, Linux sends out fragmented IP packets
"butt-first":
Right.
Is there a way to configure this? Maybe even connection specific?
No.
next prev parent reply other threads:[~2002-10-03 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 10:51 Sequence of IP fragment packets on the wire Henning P. Schmiedehausen
2002-10-03 10:53 ` David S. Miller [this message]
2002-10-03 11:18 ` David Schwartz
2002-10-03 12:42 ` Richard B. Johnson
2002-10-03 12:16 ` Alan Cox
2002-10-03 13:51 ` Henning Schmiedehausen
[not found] <anh7es$mpl$1@forge.intermeta.de.suse.lists.linux.kernel>
[not found] ` <20021003.035352.132919623.davem@redhat.com.suse.lists.linux.kernel>
2002-10-03 17:13 ` Andi Kleen
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=20021003.035352.132919623.davem@redhat.com \
--to=davem@redhat.com \
--cc=hps@intermeta.de \
--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