From: Patrick McHardy <kaber@trash.net>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] don't allow netfilter --setmss to increase mss
Date: Wed, 05 Dec 2007 09:37:14 +0100 [thread overview]
Message-ID: <4756633A.8010201@trash.net> (raw)
In-Reply-To: <47565F64.2000907@trash.net>
Patrick McHardy wrote:
> Benjamin LaHaise wrote:
>> Yes, I am aware of --clamp-mss-to-pmtu, but it doesn't work for
>> outgoing connections from clients (ie web traffic), as it only looks
>> at the PMTU on the destination route, not the source of the packet
>> (the DSL interfaces in question have a 1442 byte MTU while the
>> destination ethernet interface is 1500 -- there are problematic hosts
>> which use a 1300 byte MTU). Reworking that is probably a good idea at
>> some point, but it's more work than this is.
>
> Yes, this has always annoyed me too as it doesn't really work for me
> in a similar setup where traffic first goes through an IPsec tunnel,
> then through a MSS mangling gateway and then over a DSL line. I'll
> add a patch on top of yours to take the MSS in reverse direction
> into account.
This gets a bit too ugly because of rp-filters and actually might
not properly work in setups with routing by fwmark, so I'll leave
it as it is, its probably better to manually set the MSS in these
cases.
prev parent reply other threads:[~2007-12-05 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 22:45 [PATCH] don't allow netfilter --setmss to increase mss Benjamin LaHaise
2007-12-05 8:20 ` Patrick McHardy
2007-12-05 8:37 ` Patrick McHardy [this message]
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=4756633A.8010201@trash.net \
--to=kaber@trash.net \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).