From: Dmitry Labutcky <avl@strace.net>
To: netfilter@lists.netfilter.org
Cc: Holger Burmann <H.Burmann@gmx.de>
Subject: Re: DF reset / MSS clamp pmtu
Date: Tue, 27 Jul 2004 09:09:17 +0300 [thread overview]
Message-ID: <200407270909.18426.avl@strace.net> (raw)
In-Reply-To: <000001c47314$908a0100$0a00020a@burmann.local.tld>
Hello,
> Hello !
> Windows 2000 Server drop icmp messages "fragmentation needed". I can
> only get stupid answers from Microsoft about routers who drop the packes
> - but the problem is Microsoft.
>
> So I add
>
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS
> --clamp-mss-to-pmtu
>
> To my Linux router. It works fine for outgoing traffic but not on
> incomming.
>
> Example:
> 1) Windows Client --- mss 1460 -> Linux box ---ppp mss 1452 --->
> 2) Windows Client <-- mss 1460 -- Linux box <--ppp mss 1460 ---
> 3) Windows Client -- 1500 Bytes --> Linux box
> 4) Windows Client <-- icmp max 1492 Bytes -- Linux box
> 5) Windows Client -- 1500 Bytes --> Linux box
> 6) Windows Client <-- icmp max 1492 Bytes -- Linux box
> ...
>
> I guess the "clamp-mss-to-pmtu" hack only work for the destination
> network - or is that a bug ? The second packed comming from the ppp-IF
> go throu without change.
>
> One solutin is to reset the DF-Bit - but how ?
>
> The other way is always sutract 100-200 bytes from the mss
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss
> 800:899 -j TCPMSS --set-mss 700
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss
> 900:999 -j TCPMSS --set-mss 800
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss
> 1000:1099 -j TCPMSS --set-mss 900
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss
> 1100:1199 -j TCPMSS --set-mss 1000
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss
> 1200:1299 -j TCPMSS --set-mss 1100
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss
> 1300:1399 -j TCPMSS --set-mss 1200
> iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1400:
> -j TCPMSS --set-mss 1300
>
>
> Any other idea ?
>
> Mit freundlichen Grüßen
>
> Holger Burmann
I have same problem some time later. My uplink not pass tcp-packets whith
length more then 1496 bytes. I solve this by cleaning DF-bit in all outgoing
tcp-packets. Linux by default not allow clear Df-bit and I'm wrote small
kernel modules and patch for iptables for clearning DF-bit. Downdload from
here:
http://mordor.strace.net/iptables/ipt_DF.tgz - for 2.4 kernels
http://mordor.strace.net/iptables/ipt_DF-2.6.tgz - for 2.6 kernels
http://mordor.strace.net/iptables/iptables-1.2.7.DF-patch.diff.bz2
http://mordor.strace.net/iptables/iptables-1.2.9.DF-patch.diff.bz2
Use:
for clear DF on outgoing packets:
iptables -t mangle -A POSTROUTING -j DF --clear
for clean DF on incoming packets:
iptables -t mangle -A PREROUTING -j DF --clear
And also other iptables options is allowning.
--
/bye
----------------------------------------------------------------------
Dmitry U.Labutcky System administrator of Swift Trace
mail to: avl@strace.net Simferopol, Crimea, Ukraine
phone: +380-652-516546 Yaltinskaya 20, office 502
next prev parent reply other threads:[~2004-07-27 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 13:29 DF reset / MSS clamp pmtu Holger Burmann
2004-07-27 6:09 ` Dmitry Labutcky [this message]
2004-07-27 10:51 ` Thomas Lußnig
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=200407270909.18426.avl@strace.net \
--to=avl@strace.net \
--cc=H.Burmann@gmx.de \
--cc=netfilter@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.