Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Rudi Starcevic <tech@wildcash.com>
To: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: Port-forwarding Perfomance
Date: Thu, 24 Feb 2005 06:29:03 -0800	[thread overview]
Message-ID: <421DE4AF.6040702@wildcash.com> (raw)
In-Reply-To: <1109156169.11713.2.camel@nostromo.bgsecm.com>

Hi,

Still having trouble with port-forwarding performance.

As much as I look I can't find anything wrong.

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 on the Windows machine is around 15K/s using DNAT 
and Masq/Forwarding.

I'm very disappointed and did not expect to see anything like this, I 
had more like 10% in mind ...

The linux box is not under heavy load and there is only 431 connections 
being tracked.

Hmm .. I must have a problem else where, it just too hard to believe 
those download rate numbers.


Jose Maria Lopez Hernandez wrote:

>El mié, 23-02-2005 a las 17:33 -0800, Rudi Starcevic escribió:
>  
>
>>Hi,
>>
>>I have www port-forwarding setup and running OK.
>>
>>However I wonder if they way I have configured it is not the most 
>>optimal for speed and performance.
>>
>>I have a default policy of DROP with a total of about 30 rules.
>>
>>These rules below do my www port-forwarding, can you see if there is a 
>>better way to do this ?
>>
>># ENABLE FORWARDING / NAT / MASQUERADING
>>echo "1" > /proc/sys/net/ipv4/ip_forward
>>
>># NAT Forwarding Setup
>>$IPTABLES --table nat --append POSTROUTING --out-interface $ETH0 -j 
>>MASQUERADE
>>    
>>
>
>The only thing I can say about your rules it's that if you
>know the firewall IP it's much better to use SNAT than
>MASQUERADE, because you gain some speed with it.
>
>  
>
>>$IPTABLES -A FORWARD -i $ETH1 -j ACCEPT
>>$IPTABLES -A FORWARD -i $ETH0 -j ACCEPT
>>$IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
>>
>># http Port-Forwarding setup
>>$IPTABLES -t nat -A PREROUTING -i $ETH0 -p tcp --dport 80 -d $MEDIA1_IP 
>>-j DNAT --to $MEDIA1_LO:80
>>    
>>
>
>The rule it's OK, I don't know how you can do it better to achieve
>more speed.
>
>  
>
>>Many thanks,
>>Kind regards
>>Rudi
>>    
>>
>
>Regards.
>
>  
>



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005



  reply	other threads:[~2005-02-24 14:29 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 [this message]
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

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=421DE4AF.6040702@wildcash.com \
    --to=tech@wildcash.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox