From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Sequence of IP fragment packets on the wire
Date: Thu, 3 Oct 2002 10:51:08 +0000 (UTC) [thread overview]
Message-ID: <anh7es$mpl$1@forge.intermeta.de> (raw)
Hi,
as far as I can see, Linux sends out fragmented IP packets
"butt-first":
11:34:53.927146 alice > bob: (frag 44605:343@1480)
11:34:53.927189 alice.4831 > bob.udpdemo: udp 1815 (frag 44605:1480@0+)
(where the first packet is actually the fragmented 2nd part of the
second packet).
This confuses at least one firewall appliance. As I understand it,
this is done for efficency reasons. Still, is there any way to
suppress this and get the packets sent out in "head first" sequence? I
know that routers might resort the fragments again but in my case I
have an "alice -- firewall -- bob" topology which at the moment drops
the fragment on the floor...
Is there a way to configure this? Maybe even connection specific?
I tested 2.2.19 and 2.4.18 with 100 MBit Ethernet (3Com and eepro100).
Both show the same behaviour.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next reply other threads:[~2002-10-03 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 10:51 Henning P. Schmiedehausen [this message]
2002-10-03 10:53 ` Sequence of IP fragment packets on the wire David S. Miller
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='anh7es$mpl$1@forge.intermeta.de' \
--to=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 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.