From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: Re: migrating ipchains to iptables
Date: Tue, 1 Apr 2003 05:23:46 +0200 [thread overview]
Message-ID: <20030401052346.09c2ea8e.arnt@c2i.net> (raw)
In-Reply-To: <F78G1vzGbjkJ3FvTFnQ00016fee@hotmail.com>
On Mon, 31 Mar 2003 21:27:54 -0500,
"John Lumby" <johnlumby@hotmail.com> wrote in message
<F78G1vzGbjkJ3FvTFnQ00016fee@hotmail.com>:
> I'm running a 2.4.18-3 kernel but for strange reasons have always used
..you want 2.4.18-27.7|8.x|0.etc. _Now_.
http://rhn.redhat.com/errata/rh72-errata.html or
http://rhn.redhat.com/errata/rh73-errata.html or
http://rhn.redhat.com/errata/rh8-errata.html
> ipchains. Now want to switch to iptables. Wondering if anyone has
> ever written a script which will read an ipchains file as created by
>
> /etc/rc.d/init.d/ipchains save
..the easy way is use the 'setup' utility, then choose firewall setup.
> and either convert it to /etc/rc.d/init.d/iptables save format or set
> up the "corresponding" iptables chains directly.
..first however, "ipchains-save"(?), then ' service ipchains stop
&& rpm -e ipchains','rpm -ivh iptables-$the-newest.rpm', and 'setup'
as above. Tweaks: put in the equivalent of your ipchains settings,
plus bonus stateful firewalling.
..another _good_ option: combine Shorewall(.net) and Webmin(.com),
to control iptables.
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next prev parent reply other threads:[~2003-04-01 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 2:27 migrating ipchains to iptables John Lumby
2003-04-01 3:23 ` Arnt Karlsen [this message]
[not found] <F27pMHi0SYNIPukg3nO0000612d@hotmail.com>
2003-04-02 12:16 ` Arnt Karlsen
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=20030401052346.09c2ea8e.arnt@c2i.net \
--to=arnt@c2i.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox