From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Extremely slow upload (and more) from behind NAT
Date: Fri, 12 Aug 2011 15:28:18 -0500 [thread overview]
Message-ID: <4E458CE2.4090804@riverviewtech.net> (raw)
In-Reply-To: <CAKbQEqG3vrDpLBzh7CVBxhezWOtuZRASFPFG4uHTOQDpkyUFtw@mail.gmail.com>
On 08/12/11 11:06, Christian Pernegger wrote:
> The official method for getting one's IP is DHCP, though configuring
> it statically reportedly also works. I tried both, no difference.
> The DHCP server *does* suggest an MTU of 576 bytes instead of the
> ususal 1500 bytes, but that seems to be bogus. Manual PMTU discovery
> via don't-fragment pings to various servers is consistent with an MTU
> of 1500 and anyway, changing it to 576 doesn't have any appreciable
> effect at all, with or without a TCPMSS rule as suggested by the
> iptables man page.
I was going to say that this /really/ seems like an MTU / TCPMSS issue
to me.
For giggles, ssh from one of the clients configuring the ssh client as a
socks proxy. Then have your web browser use the ssh / socks proxy for
testing. If that does work correctly, I'd still really question MTU /
TCPMSS.
What happens if you clamp the MTU / TCPMSS really low just to make sure
you are (way) below any thing interfering.
Have you tried running a network sniffer on any of the traffic to see
what it's doing? Do you have any re-transmissions? Do you see requests
that don't have associated replies?
Do the sniffs on the inside interface match the outside interface (save
for the nated IP address)?
Grant. . . .
prev parent reply other threads:[~2011-08-12 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 16:06 Extremely slow upload (and more) from behind NAT Christian Pernegger
2011-08-12 16:32 ` Tyler J. Wagner
2011-08-12 16:45 ` Christian Pernegger
2011-08-12 19:18 ` Tyler J. Wagner
2011-08-16 13:01 ` Christian Pernegger
2011-08-12 17:34 ` Jan Engelhardt
2011-08-12 20:28 ` Grant Taylor [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=4E458CE2.4090804@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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.