From: Sven Schuster <schuster.sven@gmx.de>
To: s <xperience@interia.pl>
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT PPPOE & MTU problems
Date: Sat, 14 Jun 2003 21:36:48 +0200 [thread overview]
Message-ID: <3EEB7950.5000000@gmx.de> (raw)
In-Reply-To: 000801c325de$f89fde60$1800a8c0@ckznak.pl
s wrote:
> I've got a problem with NAT connections on PPPOE.
> My box is connected to internet via DSL, and I have some computers
> behind NAT.
> I changed MTU on internal interfaces to 1492 and configured iptables with:
>
> iptables -A FORWARD -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS
> --clamp-mss-to-pmtu
> also I have squid cache installed for local workstations.
> When I surfing net without squid everything works fine, no timeouts or
> something. Is good.
> But when I use squid as a cache sometimes when squid uses POST method
> with huge amount of parameters, connection hangs. On tcpdump I see
> that one packet is repeated few times (5) and I got timeout message.
> What's wrong ? Repeated packet has 1492 bytes lenght. But there's no
> answer from www server.
>
> Pozdraviam
> Przemyslaw Borkowski
I think the problem here is that squid will establish a connection
locally from your box. So when your computers on the internal
net surf directly, the MSS will be clamped to PMTU via your
FORWARD rule. When your clients surf via your squid proxy,
the SYN pakets MSS aren't clamped to PMTU.
So, you'll need the same rule to clamp the MSS for your OUTPUT
rule.
Hope this helps
Sven
prev parent reply other threads:[~2003-06-14 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 12:36 NAT PPPOE & MTU problems s
2003-06-12 4:49 ` Greg Stark
2003-06-14 19:36 ` Sven Schuster [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=3EEB7950.5000000@gmx.de \
--to=schuster.sven@gmx.de \
--cc=netfilter@lists.netfilter.org \
--cc=xperience@interia.pl \
/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.