From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
jaco@uls.co.za
Subject: Re: [NETFILTER]: xt_TCPMSS: Consider reverse route's MTU in clamp-to-pmtu
Date: Wed, 23 Jan 2008 23:29:55 +0100 [thread overview]
Message-ID: <4797BFE3.6090603@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801232155020.12676@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On top of standard net branch, no previous patch required.
>
> ===
> commit 46bfc78a6b91251fd55140b27f382259fc3333a2
> Author: Jan Engelhardt <jengelh@computergmbh.de>
> Date: Wed Jan 23 16:35:00 2008 +0100
>
> [NETFILTER]: xt_TCPMSS: Consider reverse route's MTU in clamp-to-pmtu
>
> The TCPMSS target in Xtables should consider the MTU of the reverse
> route on forwarded packets as part of the path MTU.
>
> Point in case: IN=ppp0, OUT=eth0. MSS set to 1460 in spite of MTU of
> ppp0 being 1392.
>
> Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de>
>
Applied, thanks.
> +static u_int32_t tcpmss_reverse_mtu4(const struct iphdr *iph)
> +{
> + struct flowi fl = {.nl_u = {.ip4_u = {
> + .daddr = iph->saddr,
> + .tos = RT_TOS(iph->tos),
>
This doesn't make much sense, we don't know the ToS value
that will be used in the reverse direction. People might also
use routing rules based on source address, iif etc., so I
think we should make this optional.
I'm on my way out the door, I'll take care of that tommorrow.
next prev parent reply other threads:[~2008-01-23 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 20:57 [NETFILTER]: xt_TCPMSS: Consider reverse route's MTU in clamp-to-pmtu Jan Engelhardt
2008-01-23 22:29 ` Patrick McHardy [this message]
2008-01-23 22:43 ` Jan Engelhardt
2008-01-24 3:47 ` Jaco Kroon
2008-01-24 7:53 ` Patrick McHardy
2008-01-24 8:57 ` Jaco Kroon
2008-01-24 9:58 ` Pascal Hambourg
2008-01-24 10:49 ` Jaco Kroon
2008-01-24 11:20 ` Jan Engelhardt
2008-01-29 12:55 ` Patrick McHardy
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=4797BFE3.6090603@trash.net \
--to=kaber@trash.net \
--cc=jaco@uls.co.za \
--cc=jengelh@computergmbh.de \
--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 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.