From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: 'stephane durieux' <durieux42@yahoo.fr>, netfilter@lists.netfilter.org
Subject: RE: speed connection problem
Date: Mon, 26 Jul 2004 21:41:25 -0700 [thread overview]
Message-ID: <SERVER7RQXPAhp6R47w00000001@server7.bandwidthco.com> (raw)
In-Reply-To: <41051990.9070208@yahoo.fr>
How can I solve this problem. Is it due to my heavy configuration ?
I am afraid it will be worse if I install DMZ servers (http, ftp, postfix,
dns)
Have you got any suggestion ?
Thanks a lot.
Here is my (heavy) configuration
This is not what I would call a heavy load Stephane. Your rig should handle
this without a blink. My netfilter/iptables firewall is also directly
connected to the internet via dsl (albeit with a static IP), with five
subnets behind it, including a DMZ with a mail relay, DNS server, web
server, squid proxy, etc, etc, blah, blah. My rule set stands at
approximately 2000 and my machine does not blink. So I suggest the slow down
might be something else. Suggestions and questions:
1. Run your firewall (temporarily of course) with no rules loaded and all
your default policies set to default so you can make some rate comparisons:
set_default_policy()
{
$IPT -F
$IPT -X
$IPT -P INPUT ACCEPT
$IPT -P FORWARD ACCEPT
$IPT -P OUTPUT ACCEPT
}
2. Your FTP rules need a little tuning. I can see these giving you some
problems with your ftp communication. Are you using ip_conntrack_ftp?
3. I notice you seem to favor source port 1024 on you output rules. I find
this a little hard to understand. Is there a reason for this?
prev parent reply other threads:[~2004-07-27 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 14:47 speed connection problem stephane durieux
2004-07-26 13:06 ` Brent Clark
2004-07-26 13:27 ` Antony Stone
2004-07-27 4:41 ` Mark E. Donaldson [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=SERVER7RQXPAhp6R47w00000001@server7.bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=durieux42@yahoo.fr \
--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 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.