From: Patrick McHardy <kaber@trash.net>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: mss to pmtu clamping partially broken?
Date: Fri, 29 Jun 2007 13:39:22 +0200 [thread overview]
Message-ID: <4684EF6A.7070109@trash.net> (raw)
In-Reply-To: <4684E853.20900@domdv.de>
Andreas Steinmetz wrote:
> There seems to be a problem with mss to pmtu clamping for incoming syn
> packets on reply to an outgoing connection on a ppp interface. The mss
> of the outgoing syn packets is always always clamped to the pmtu, I did
> check this with a target host I do have access to. The incoming syn
> reply to such a packet, however, is mss clamped only sometimes and this
> seems to depend on the DSL line used.
>
> The kernels tested were 2.6.20.1, 2.6.20.3 and 2.6.22rc6.
>
> Test setup: Two DSL lines, otherwise identical setup (same masquerading
> linux gateway, same DSL account, same DSL modem, same DSL line provider,
> same target host, request from and tcpdump on the same client).
>
> Linux Client<->Masquerading Linux Gateway<->DSL Modem<->DSL Line<->...
>
> DSL line 1, working:
>
> 22:26:39.319281 IP (tos 0x0, ttl 64, id 22377, offset 0, flags [DF],
> length: 48
> ) 192.168.0.253.1164 > 64.34.165.170.80: S [tcp sum ok]
> 1465827859:1465827859(0)
> win 5840 <mss 1460,nop,nop,sackOK>
> 22:26:39.459314 IP (tos 0x0, ttl 51, id 0, offset 0, flags [DF],
> length: 48) 64
> .34.165.170.80 > 192.168.0.253.1164: S [tcp sum ok]
> 3667852791:3667852791(0) ack
> 1465827860 win 5840 <mss 1452,nop,nop,sackOK>
>
> The tcpdump on the client shows that the mss of the incoming syn reply
> packet is clamped to the ppp interface mtu.
>
> DSL line 2, not working:
>
> 22:03:57.725998 IP (tos 0x0, ttl 64, id 55984, offset 0, flags [DF],
> length: 48
> ) 192.168.0.253.1600 > 64.34.165.170.80: S [tcp sum ok]
> 36968258:36968258(0) win
> 5840 <mss 1460,nop,nop,sackOK>
> 22:03:57.866966 IP (tos 0x0, ttl 51, id 0, offset 0, flags [DF],
> length: 48) 64
> .34.165.170.80 > 192.168.0.253.1600: S [tcp sum ok]
> 2226854208:2226854208(0) ack
> 36968259 win 5840 <mss 1460,nop,nop,sackOK>
>
> The tcpdump on the client shows that the mss of the incoming syn reply
> packet is *NOT* clamped to the ppp interface mtu.
You forgot to mention *how* you're clamping the MSS. Using
TCPMSS? Do you have a rule for incoming packets?
next prev parent reply other threads:[~2007-06-29 11:39 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 [this message]
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
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=4684EF6A.7070109@trash.net \
--to=kaber@trash.net \
--cc=ast@domdv.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.