From: Aaron Lehmann <aaronl@vitelus.com>
To: Daniel Stone <daniel@kabuki.eyep.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 and ipmasq modules
Date: Sat, 20 Jan 2001 16:08:43 -0800 [thread overview]
Message-ID: <20010120160843.A17947@vitelus.com> (raw)
In-Reply-To: <20010120144616.A16843@vitelus.com> <E14K7UY-0004hB-00@kabuki.eyep.net> <20010120153403.A17269@vitelus.com> <E14K83B-0004lQ-00@kabuki.eyep.net>
In-Reply-To: <E14K83B-0004lQ-00@kabuki.eyep.net>; from daniel@kabuki.eyep.net on Sun, Jan 21, 2001 at 11:08:00AM +1100
On Sun, Jan 21, 2001 at 11:08:00AM +1100, Daniel Stone wrote:
> > That option seems to conflict with "ipfwadm (2.0-style) support".
> > Preferably, I'd like to stay with friendly old ipfwadm rather than
> > switching firewalling tools _again_.
>
> "I'd rather stay with my friendly old pushbike than my car!"
> So don't complain when you can't use cruise control.
ipfwadm used to support the modules. Why have the modules for ipfwadm
been removed from the kernel source?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-21 0:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 22:46 2.4 and ipmasq modules Aaron Lehmann
2001-01-20 23:32 ` Daniel Stone
2001-01-20 23:34 ` Aaron Lehmann
2001-01-21 0:08 ` Daniel Stone
2001-01-21 0:08 ` Aaron Lehmann [this message]
2001-01-21 0:22 ` Doug McNaught
2001-01-24 12:37 ` Harald Welte
2001-01-21 7:47 ` Paul Jakma
2001-01-24 12:38 ` Harald Welte
2001-01-21 1:55 ` [OT] " J Sloan
2001-01-21 2:24 ` John Jasen
2001-01-23 1:48 ` Rusty Russell
2001-01-23 2:01 ` Aaron Lehmann
2001-01-23 7:29 ` Daniel Stone
2001-01-23 16:18 ` Martin Josefsson
2001-01-23 16:56 ` Aaron Lehmann
2001-01-24 12:41 ` Harald Welte
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=20010120160843.A17947@vitelus.com \
--to=aaronl@vitelus.com \
--cc=daniel@kabuki.eyep.net \
--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 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.