From: Andreas Steinmetz <ast@domdv.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: netfilter-devel@lists.netfilter.org,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: mss to pmtu clamping partially broken?
Date: Mon, 02 Jul 2007 19:04:12 +0200 [thread overview]
Message-ID: <4689300C.9050802@domdv.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0706301034320.22579@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Do you really need clamping? It's a hack, since TCP should do MSS negotiation
> itself. (Of course it may happen that some routers are broken.) But usually not
> for incoming packets.
You never know when you hit ICMP blackholes, broken routers and other
evil things. Better safe than sorry so clamping is the way to go for me.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Steinmetz <ast@domdv.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: mss to pmtu clamping partially broken?
Date: Mon, 02 Jul 2007 19:04:12 +0200 [thread overview]
Message-ID: <4689300C.9050802@domdv.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0706301034320.22579@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Do you really need clamping? It's a hack, since TCP should do MSS negotiation
> itself. (Of course it may happen that some routers are broken.) But usually not
> for incoming packets.
You never know when you hit ICMP blackholes, broken routers and other
evil things. Better safe than sorry so clamping is the way to go for me.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
next prev parent reply other threads:[~2007-07-02 17:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 11:09 mss to pmtu clamping partially broken? Andreas Steinmetz
2007-06-29 11:39 ` Patrick McHardy
2007-06-29 11:58 ` Andreas Steinmetz
2007-06-29 11:58 ` Andreas Steinmetz
2007-06-29 12:03 ` Patrick McHardy
2007-06-29 12:06 ` Andreas Steinmetz
2007-06-29 12:06 ` Andreas Steinmetz
2007-06-29 12:13 ` Patrick McHardy
2007-06-29 12:16 ` Andreas Steinmetz
2007-06-29 12:16 ` Andreas Steinmetz
2007-07-02 17:02 ` Andreas Steinmetz
2007-06-30 8:35 ` Jan Engelhardt
2007-07-02 17:04 ` Andreas Steinmetz [this message]
2007-07-02 17:04 ` Andreas Steinmetz
2007-07-02 18:28 ` Phil Dibowitz
2007-07-02 19:16 ` Krzysztof Oledzki
2007-07-02 19:16 ` Krzysztof Oledzki
2007-07-02 19:35 ` Phil Dibowitz
2007-07-02 19:35 ` Phil Dibowitz
2007-07-02 19:50 ` Krzysztof Oledzki
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=4689300C.9050802@domdv.de \
--to=ast@domdv.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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.