From: Elikster <elik@webspires.com>
To: linux-kernel@vger.kernel.org
Subject: Re[2]: Darren's ipfilter ported to linux
Date: Wed, 10 Mar 2004 00:26:32 -0700 [thread overview]
Message-ID: <187223550.20040310002632@webspires.com> (raw)
In-Reply-To: <20040310061359.GL1653@mea-ext.zmailer.org>
Greetings folks,
*Groans* Do we need another revision here again? It is pain in the butt going from ipf to ipchains and then to Iptables. Just going over to ipfilter from Iptables is just asking for suicide among lot us if we going to be using the new filter system.
Just improve on Iptables and stick with it. :) I don't feel like learning another ip filtering system all over again after going though 3 changes. :)
Although, it would be nice if we can add the natural language filtering system to the IPtables, something akin to this line:
REJECT 32.31.38.83:80 INPUT, which make it lot easier than the IPTables setup, but it is just me wishing. :)
Tuesday, March 9, 2004, 11:13:59 PM, you wrote:
MA> On Tue, Mar 09, 2004 at 09:16:53PM -0800, Mike Fedyk wrote:
>> Jett Tayer wrote:
>> >Hi,
>> >
>> >When will this be integrated to the kernel???
>>
>> Why should it be?
>> What does it gain us?
>> Is it GPL?
MA> It is (probably) "Darren Reed's ipfilter", aka BSD ipf(ilter).
MA> Having used ipf, ipchains, iptables, etc. in different system,
MA> I take iptables any day. YMMV, etc.
MA> /Matti Aarnio
MA> -
MA> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
MA> the body of a message to majordomo@vger.kernel.org
MA> More majordomo info at http://vger.kernel.org/majordomo-info.html
MA> Please read the FAQ at http://www.tux.org/lkml/
--
Best regards,
Elikster mailto:elik@webspires.com
prev parent reply other threads:[~2004-03-10 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 5:09 Jett Tayer
2004-03-10 5:16 ` Mike Fedyk
2004-03-10 6:13 ` Matti Aarnio
2004-03-10 7:26 ` Elikster [this message]
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=187223550.20040310002632@webspires.com \
--to=elik@webspires.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®