From: Timo Teras <timo.teras@iki.fi>
To: netdev@vger.kernel.org
Subject: iptables CLAMP MSS to PMTU not working?
Date: Thu, 12 Jul 2012 12:00:21 +0300 [thread overview]
Message-ID: <20120712120021.3dc5cd68@vostro> (raw)
Hi,
We recently noticed that CLAMPMSS to path MTU does not seem to be
working properly. Most recently tested version is linux-3.3.6 which
does not work. linux-2.6.35 works for sure, but I suspect it to have
broken somewhere around 3.0'ish with the inetpeer changes.
In my case, the destination is on gre tunnel (that gets routed to
Internet over IPsec transport mode).
'ip route' command verifies that in both boxes the path-MTU is detected
properly. That, is on both cases the static route MTU is higher. And
after large packets sent, ICMP frag-needed is received and the cache
route is updated properly.
On the new kernel, I get info like:
# ip route get 10.x.x.x
10.x.x.x via 172.16.y.y dev gre1 src 172.16.z.z
cache expires 68sec ipid 0x3153 mtu 1422
And the older kernel:
# ip route get 10.x.x.x
10.x.x.x via 172.16.y.y dev gre1 src 172.16.z.z
cache expires 595sec ipid 0xd241 mtu 1422 advmss 1432 hoplimit 64
For some reason, iptables CLAMPMSS seems to set incorrect MSS for this
route (or maybe it's using the static route instead?).
Any ideas?
Thanks,
Timo
next reply other threads:[~2012-07-12 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 9:00 Timo Teras [this message]
2012-07-12 10:24 ` iptables CLAMP MSS to PMTU not working? Timo Teras
2012-07-16 5:49 ` Timo Teras
2012-07-16 6:20 ` Timo Teras
2012-07-16 7:23 ` Steffen Klassert
2012-07-16 7:55 ` Timo Teras
2012-07-16 10:08 ` Steffen Klassert
2012-07-16 10:53 ` Timo Teras
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=20120712120021.3dc5cd68@vostro \
--to=timo.teras@iki.fi \
--cc=netdev@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