All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Schmiedehausen <hps@intermeta.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Sequence of IP fragment packets on the wire
Date: 03 Oct 2002 15:51:44 +0200	[thread overview]
Message-ID: <1033653105.22055.2.camel@forge> (raw)
In-Reply-To: <1033647370.28022.0.camel@irongate.swansea.linux.org.uk>

Hi,

thanks to anyone for making this clear. Replacing this particular
system is currently out of question but I will take it on with the
people from SonicWall (oops, now the name did slip, silly me...)
to get this fixed ASAP. 

	Regards
		Henning


On Thu, 2002-10-03 at 14:16, Alan Cox wrote:
> On Thu, 2002-10-03 at 11:51, Henning P. Schmiedehausen wrote:
> > This confuses at least one firewall appliance. As I understand it,
> 
> You should replace that appliance. Packets can get re-ordered by a
> million different things on the wire not just by the fact Linux is
> optimising the fragment processes.
> 
> > Is there a way to configure this? Maybe even connection specific? 
> 
> No
> 
> Alan

-- 
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   


  reply	other threads:[~2002-10-03 13:46 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
2002-10-03 12:42   ` Richard B. Johnson
2002-10-03 12:16 ` Alan Cox
2002-10-03 13:51   ` Henning Schmiedehausen [this message]
     [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=1033653105.22055.2.camel@forge \
    --to=hps@intermeta.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.