Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Tyler J. Wagner" <tyler@tolaris.com>
To: Christian Pernegger <pernegger@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Extremely slow upload (and more) from behind NAT
Date: Fri, 12 Aug 2011 20:18:04 +0100	[thread overview]
Message-ID: <4E457C6C.7080808@tolaris.com> (raw)
In-Reply-To: <CAKbQEqG5kBPrqBqdMpyufWpioeE6A0_zpXgEPnYeCuPk3JmpxA@mail.gmail.com>

On 2011-08-12 17:45, Christian Pernegger wrote:
>> Please post your iptables / iptables-restore script.
> 
> I did, in a way. It's really just that one line, "iptables -t nat -A
> POSTROUTING -s 192.168.0.0/24 -o eth1 -j MASQUERADE", at the moment,
> executed as a post-up command from /etc/network/interfaces.

I doubt that's the problem, then. I would write it without the "-s
192.168.0.0/24" statement, as it is not needed if you have no other
networks or interfaces. But I very much doubt it is the cause of the
problem.

You said the problem only happens to NAT'ed traffic. What if it's not
NAT, but eth0, that's the issue? Try swapping eth0 and eth1 and see if
the problem affects traffic to/from the router as well.

I recently had a problem with one server (with an old cheap Via chipset)
that ran fine on Ubuntu 8.04. But when I reformatted it for Ubuntu
10.04, eth0 started having serious issues with throughput that I
eventually concluded was an IRQ issue. Since it had two interfaces, I
renamed them and used the other one.

Regards,
Tyler

-- 
"Offending fundamentalists isn't my goal – but if it is an inevitable
side-effect of defending human rights, so be it."
   -- Johann Hari

  reply	other threads:[~2011-08-12 19:18 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 [this message]
2011-08-16 13:01       ` Christian Pernegger
2011-08-12 17:34 ` Jan Engelhardt
2011-08-12 20:28 ` Grant Taylor

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=4E457C6C.7080808@tolaris.com \
    --to=tyler@tolaris.com \
    --cc=netfilter@vger.kernel.org \
    --cc=pernegger@gmail.com \
    /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