From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: XXmas@gmx.at
Cc: netfilter@lists.netfilter.org
Subject: Re: bandwidth problems [Linux 2.4.20] [iptables 1.2.7a]
Date: Tue, 10 Feb 2004 13:01:04 -0500 [thread overview]
Message-ID: <1076436064.2016.35.camel@ca.gts.nexusmgmt.com> (raw)
In-Reply-To: <E1Aqbgf-0000sd-OV@vishnu.netfilter.org>
On Tue, 2004-02-10 at 12:28, root@scheuchenstuel.com wrote:
> Hi!
>
> My configuration:
> =================
>
> O-------------o O-----------------------o
> | WinXP | | eth0 | eth1 |
> | 10.10.1.100 |----| 10.10.1.254 | D H C P |----INTERNET
> | | | | |
> O-------------o O-----------------------o
> My Computer My NAT-Computer
>
> NAT-Computer:
> Linux 2.4.20-4GB
> load average: 0.08, 0.05, 0.06
> iptables v1.2.7a
> All the NICs I use are 3com 3C905-TX
>
> When I do some bandwidth tests on the NAT-Computer
> (provider's service page) my bandwidth is about 1MBit/second
> When I do the same on my computer I only get about 100kbit/second
>
> Now I wonder if there are any problems with my configuration...?
> Would be nice if you could help me...
>
> Thanks in advance
> Florian St.
>
> Root(AT)scheuchenstuel(DOT)com
>
>
> My iptables-configuration:
> ==========================
>
> ############################################################################
> ######
>
> #!/bin/bash
> #
>
> modprobe iptable_nat
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> ########## CLEARING TABLES
> iptables -F
> iptables -t nat -F
> iptables -t mangle -F
> iptables -X
>
> ########## SETTING POLICIES
> iptables -P INPUT DROP
> iptables -P OUTPUT ACCEPT
> iptables -P FORWARD DROP
>
> ########## NAT
> iptables -A INPUT -i eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
>
> ########## LOOPBACK SETTINGS
> iptables -A INPUT -i lo -j ACCEPT
> iptables -A INPUT -s 127.0.0.1/32 -j ACCEPT
>
> ########## EXTERNAL OPEN PORTS
> iptables -A INPUT -i eth1 -p tcp --dport 80 -j ACCEPT
>
> ########## INTERNAL OPEN PORTS
> iptables -A INPUT -s 10.10.1.100/32 -j ACCEPT
>
> ######### NAT FORWARDING
> iptables -A FORWARD -s 10.10.1.100/32 -j ACCEPT
> iptables -A FORWARD -d 10.10.1.100/32 -j ACCEPT
>
> ############################################################################
> ######
The rules look a little unusual; in fact, they look downright
dangerous. You may want to read a good iptables tutorial such as the
one by Oskar Andreasson. You can find a link to it on the netfilter.org
web site. You can also find some slide shows in the training section at
http://iscs.sourceforge.net
However, I do not think your rules would create a throughput problem.
How are you measuring your throughput?
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-02-10 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 17:28 bandwidth problems [Linux 2.4.20] [iptables 1.2.7a] root
2004-02-10 18:01 ` John A. Sullivan III [this message]
2004-02-10 19:43 ` AW: " root
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=1076436064.2016.35.camel@ca.gts.nexusmgmt.com \
--to=john.sullivan@nexusmgmt.com \
--cc=XXmas@gmx.at \
--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