From: J A <jake.lists@gmail.com>
To: Askar <askarali@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: IPTables & HTTPD Conflict
Date: Mon, 4 Apr 2005 17:59:14 +0800 [thread overview]
Message-ID: <249c20290504040259680894c@mail.gmail.com> (raw)
In-Reply-To: <a0f69e5050404024079ea9980@mail.gmail.com>
Sorry, when i replied to the thread, i seemed to have copied only
guido, here's a re-send:
Here are our rules (pls refer to the thread for the problem
description), hope you could share us your vasluable insight.
--------------------------------------------------------------------------
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Lokkit-0-50-INPUT - [0:0]
-A INPUT -j RH-Lokkit-0-50-INPUT
-A FORWARD -j RH-Lokkit-0-50-INPUT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 25 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 80 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 21 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 22 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 23 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -i lo -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 0:1023 --syn -j REJECT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 2049 --syn -j REJECT
-A RH-Lokkit-0-50-INPUT -p udp -m udp --dport 0:1023 -j REJECT
-A RH-Lokkit-0-50-INPUT -p udp -m udp --dport 2049 -j REJECT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 6000:6009 --syn -j REJECT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 7100 --syn -j REJECT
COMMIT
--------------------------------------------------------------------------
On Apr 4, 2005 5:40 PM, Askar <askarali@gmail.com> wrote:
> how should we suggest something without watchen your iptables rules set?
>
> regards
>
>
> On Apr 4, 2005 8:11 AM, J A <jake.lists@gmail.com> wrote:
> > Hello All,
> >
> > We're using Redhat 9
> > We've been running a Web Server (Apache & Tomcat), and were told to
> > run a firewall, in this case IPTables. When we enabled IPTables, many
> > of our web sites (BUT not all) could no longer be browsed from the
> > Internet.
> >
> > Could you tell us which specific IPTables parameter is doing this, so
> > we could disable only the specific parameter?
> > Or is it not advisable to run IPTables side-by-side with Web services?
> >
> > Thanks, appreciate your ideas.
> >
> > ---jake
> >
> >
>
> --
> I love deadlines. I like the whooshing sound they make as they fly by.
> Douglas Adams
>
next prev parent reply other threads:[~2005-04-04 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 13:39 MASQUERADE: Route sent us somewhere else Tim Evans
2005-04-04 2:11 ` IPTables & HTTPD Conflict J A
2005-04-04 9:40 ` Askar
2005-04-04 9:59 ` J A [this message]
2005-04-04 11:32 ` Askar
2005-04-05 6:41 ` J A
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=249c20290504040259680894c@mail.gmail.com \
--to=jake.lists@gmail.com \
--cc=askarali@gmail.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