From: Michael <mutk@ozemail.com.au>
To: Daniel Curry <dcurry@cariocas.com>,
IPtables Users <netfilter@lists.samba.org>
Subject: Re: IPTables not available
Date: Thu, 27 Jun 2002 03:09:35 +1000 [thread overview]
Message-ID: <3D19F54F.2070404@ozemail.com.au> (raw)
In-Reply-To: 731E36372B5FD248AF790189519A32C19E4F88@mailhub.cgtime.com
An easy way, exclusively to Redhat as root in terminal:
type setup , select system services scroll down, you will find (if
bog standard RH install) both ipchains and iptables checked. Uncheck
ipchains, and leave iptables as is.
Precautionary, do
service ipchains stop as well...
BTW, IPtables is actually iptables , note lower case,
ipchains seems to take presedence over iptables, default RH feeble fire
wall is ipchains based. Expect that to change !!!
Cheers,
Michael
Daniel Curry wrote:
>On fresh RH7.2 and RH7.3 installs IPTables executables are installed,
>but will not execute. I get Kernel errors. Can someone please direct
>me to a listing of what steps and option I need to enable this? I wish
>to put firewalling with NAT services on a machine running an Apache web
>server, with PHP and Perl scripts connecting to a localhosted MySQL DB,
>as well as offering sendmail, POP(S)/IMAP(S), ftp, and PPTP VPN
>services. Or a compatible ipchains script for this would also be
>appreciated.
>
next prev parent reply other threads:[~2002-06-26 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 15:20 IPTables not available Daniel Curry
2002-06-25 15:28 ` Tom Eastep
2002-06-26 17:09 ` Michael [this message]
[not found] <20020625174406.9A4D9489B@lists.samba.org>
2002-06-26 2:32 ` jesse.linux
2002-06-26 11:53 ` Razham, Razak
2002-06-26 12:55 ` George Georgalis
2002-06-26 13:37 ` Benny Butler
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 17:19 Bailey Kong
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=3D19F54F.2070404@ozemail.com.au \
--to=mutk@ozemail.com.au \
--cc=dcurry@cariocas.com \
--cc=netfilter@lists.samba.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