From: James Courtier-Dutton <James@superbug.co.uk>
To: root@chaos.analogic.com
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Marc Ballarin <Ballarin.Marc@gmx.de>,
Linus Torvalds <torvalds@osdl.org>,
netfilter-devel@lists.netfilter.org,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] Warn people that ipchains and ipfwadm are going away.
Date: Wed, 22 Sep 2004 12:52:04 +0100 [thread overview]
Message-ID: <41516764.8030205@superbug.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.53.0409220735080.2066@chaos.analogic.com>
Richard B. Johnson wrote:
> On Wed, 22 Sep 2004, Rusty Russell wrote:
>
>
>>On Tue, 2004-09-21 at 22:36, Marc Ballarin wrote:
>>
>>>On Tue, 21 Sep 2004 09:09:02 +1000
>>>"Rusty Russell (IBM)" <rusty@au1.ibm.com> wrote:
>>>
>>>
>>>>Name: Warn that ipchains and ipfwadm are going away
>>>>Status: Trivial
>>>>Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
>>>
> What replaces the firewall stuff? It can't just "go away"!
>
> Cheers,
> Dick Johnson
ipchains and ipfwadm are very old firewall implementations.
The current linux firewall code is called "iptables" and that has been
present for a long time time, and that is staying.
So, the linux kernel still has firewall features, even with ipchains and
ipfwadm removed.
James
next prev parent reply other threads:[~2004-09-22 11:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 23:09 [PATCH] Warn people that ipchains and ipfwadm are going away Rusty Russell (IBM)
2004-09-21 12:36 ` Marc Ballarin
2004-09-21 21:58 ` Rusty Russell
2004-09-21 21:58 ` Rusty Russell
2004-09-21 22:36 ` Marc Ballarin
2004-09-21 22:36 ` David S. Miller
2004-09-21 22:36 ` David S. Miller
2004-09-21 23:35 ` Marc Ballarin
2004-09-22 0:16 ` Patrick McHardy
2004-09-22 0:16 ` Patrick McHardy
2004-09-22 13:37 ` Marc Ballarin
2004-09-22 13:58 ` Jesper Juhl
2004-09-22 14:13 ` Richard B. Johnson
2004-09-22 11:36 ` Richard B. Johnson
2004-09-22 11:47 ` Martin Josefsson
2004-09-22 11:47 ` Martin Josefsson
2004-09-22 12:05 ` Richard B. Johnson
2004-09-22 12:41 ` Gene Heskett
2004-09-23 14:56 ` Martijn Lievaart
2004-09-22 14:19 ` Fao, Sean
2004-09-22 15:31 ` William Stearns
2004-09-22 15:31 ` William Stearns
2004-09-22 16:03 ` Richard B. Johnson
2004-09-22 16:27 ` William Stearns
2004-09-22 11:52 ` James Courtier-Dutton [this message]
2004-09-22 11:55 ` Marc Ballarin
2004-09-21 17:57 ` Bill Davidsen
[not found] <2GFBZ-61e-11@gated-at.bofh.it>
[not found] ` <2GSfS-6eW-5@gated-at.bofh.it>
[not found] ` <2H0ZO-49v-13@gated-at.bofh.it>
[not found] ` <2HdDL-48z-53@gated-at.bofh.it>
[not found] ` <2HdNp-4eJ-27@gated-at.bofh.it>
2004-09-22 12:15 ` Andi Kleen
2004-09-22 14:04 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-09-23 18:07 Albert Cahalan
2004-09-23 19:33 ` Chris Friesen
2004-09-23 19:36 ` Albert Cahalan
2004-09-23 19:57 ` Andy Lutomirski
2004-09-23 19:57 ` David S. Miller
2004-09-23 23:08 ` Matthew Garrett
2004-09-23 23:25 ` David S. Miller
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=41516764.8030205@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=Ballarin.Marc@gmx.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=root@chaos.analogic.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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.