From: Grant Taylor <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: IP Tables slows network response times
Date: Mon, 15 Aug 2005 00:42:50 -0500 [thread overview]
Message-ID: <43002B5A.4000909@riverviewtech.net> (raw)
In-Reply-To: <200508142133.57867.michael@networkstuff.co.nz>
I've not run in to or heard of this problem my self before. But I suspect that there is a support protocol being used that we are aware of. How knows you may have a few things configured to use the Ident (Auth) protocol to find out the name of the user on the system that is requesting the web pages from. If this is indeed the case and you do not have a statefull packet inspection allowing returning outbound traffic back in you may be dropping some returning traffic that is sent out from a high port. In either case I would add the following rules to the end of your list to help diagnose this problem.
iptables -A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT
iptables -A INPUT -p tcp -j LOG
The second rule is probably the most important as it will log the traffic that is getting dropped and thus you will have an idea what you need to modify your firewall to allow in.
Grant. . . .
Michael Hallager wrote:
> Hello all.
>
> I have spent rather a lot of time trying to find an answer for this one.
>
> I have a Slackware Linux box, 2.4.29 kernel running IP Tables. I have the bare
> number of needed modules compiled into the custom kernel.
>
> I start IP Tables using the following batch file:
>
> iptables -P INPUT DROP
> iptables -A INPUT -p tcp --destination-port 22 -j ACCEPT
> iptables -A INPUT -p tcp --destination-port 25 -j ACCEPT
> iptables -A INPUT -p tcp --destination-port 53 -j ACCEPT
> iptables -A INPUT -p udp --destination-port 53 -j ACCEPT
> iptables -A INPUT -p tcp --destination-port 80 -j ACCEPT
> iptables -A INPUT -p tcp --destination-port 110 -j ACCEPT
> iptables -A INPUT -p tcp --destination-port 443 -j ACCEPT
>
> This works except it makes webpages and email served from this box SLOW to
> respond. (Several seconds).
>
> Any ideas please? Questions welcomed.
>
> Michael Hallager
> networkStuff ltd
> www.networkstuff.co.nz | p.09.839.1000 | m.029.638.7883
next prev parent reply other threads:[~2005-08-15 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 9:33 IP Tables slows network response times Michael Hallager
2005-08-14 9:49 ` Eric Leblond
2005-08-14 9:54 ` Michael Hallager
2005-08-15 5:42 ` Grant Taylor [this message]
2005-08-15 6:14 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2005-08-14 17:39 Gary W. Smith
2005-08-14 18:00 ` Nikolai Geogriev
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=43002B5A.4000909@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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.