From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: Rudi Starcevic <tech@wildcash.com>
Cc: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: Port-forwarding Perfomance
Date: Tue, 08 Mar 2005 11:12:48 +0000 [thread overview]
Message-ID: <422D88B0.9070905@dsl.pipex.com> (raw)
In-Reply-To: <421E6E14.5020905@wildcash.com>
Rudi Starcevic wrote:
> Hi,
>
>
> I'm still seeing slow performance with my port-forwarding but
> have found something interesting that may be problematic.
>
> Just to re-cap:
>
> I have one Linux 66.283.12.21 box and one Windows box 192.168.0.10
> I can download a file of the linux box at around 140K/s
> That very same file download on the Windows machine is around 15K/s
> using DNAT and Masq/Forwarding.
>
> However we can upload to the Windows box at 140k/s.
>
> So it is only slow, 15K/s, when the data is coming from Windows then
> through the Linux Iptables Masq/Forwarding Firewall.
>
> I contacted an earlier Admin for the Windows machine and was informed
> the TCP window size has been manually increased.
>
> Could this affect Forwarding in Iptables ?
>
> The default maximum TCP window size in Win2000 is 17520 bytes (12
> segments).
> The current value is set at 131400.
Max window size is 64k without scaling - so I assume they have turned
scaling on aswell - there have been problems with scaling, one of the
linux kernel releases set it to 7 which confused buggy peers. AIUI they
turned it back down to workaround.
You could tcpdump so you can can see what's going on.
>
> 90% of the traffic being port-forwarded are Digital video files.
> These range in size from 2MB to 200MB.
>
> So I assume with large files like these Windows would opt for it's
> largest TCP window size.
>
> I guess the next step is to lower these to their default values and see
> if it affect bandwidth.
>
> Your thoughts on that would be much appreciated.
>
> Thanks.
> Regards,
> Rudi
>
>
>
>
prev parent reply other threads:[~2005-03-08 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 1:33 Port-forwarding Perfomance Rudi Starcevic
2005-02-23 10:56 ` Jose Maria Lopez Hernandez
2005-02-24 14:29 ` Rudi Starcevic
2005-02-23 20:56 ` Maxime Ducharme
2005-02-23 21:10 ` Jason Opperisano
2005-02-24 16:09 ` Rudi Starcevic
2005-02-24 0:07 ` R. DuFresne
2005-02-25 0:15 ` Rudi Starcevic
2005-02-24 12:53 ` Daniel
2005-03-08 11:12 ` Andy Furniss [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=422D88B0.9070905@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=netfilter@lists.netfilter.org \
--cc=tech@wildcash.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 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.