From: David Schwartz <davids@webmaster.com>
To: <hps@intermeta.de>, <linux-kernel@vger.kernel.org>
Subject: Re: Sequence of IP fragment packets on the wire
Date: Thu, 3 Oct 2002 04:18:36 -0700 [thread overview]
Message-ID: <20021003111847.AAA15244@shell.webmaster.com@whenever> (raw)
In-Reply-To: <anh7es$mpl$1@forge.intermeta.de>
On Thu, 3 Oct 2002 10:51:08 +0000 (UTC), Henning P. Schmiedehausen wrote:
>as far as I can see, Linux sends out fragmented IP packets
>"butt-first":
>(where the first packet is actually the fragmented 2nd part of the
>second packet).
>
>This confuses at least one firewall appliance.
I'm afraid that this firewall appliance is fundamentally broken. Nothing you
can do to Linux can fix this fundamental breakage. I can give further
examples, analogies, and argumentation, but it really should be obvious that
IP, fundamentally, does not guarantee any particular reception order and
anything that assumes it does cannot be fixed except by changing the
assumption.
This is as bad as a TCP application that assumes one 'read' call will return
an entire line or command. You cannot push the problem elsewhere.
DS
next prev parent reply other threads:[~2002-10-03 11:13 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
2002-10-03 11:18 ` David Schwartz [this message]
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=20021003111847.AAA15244@shell.webmaster.com@whenever \
--to=davids@webmaster.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