mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: Daniel Stone <daniel@kabuki.eyep.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 and ipmasq modules
Date: Wed, 24 Jan 2001 13:37:40 +0100	[thread overview]
Message-ID: <20010124133740.W6055@coruscant.gnumonks.org> (raw)
In-Reply-To: <20010120144616.A16843@vitelus.com> <E14K7UY-0004hB-00@kabuki.eyep.net> <20010120153403.A17269@vitelus.com> <E14K83B-0004lQ-00@kabuki.eyep.net> <20010120160843.A17947@vitelus.com>
In-Reply-To: <20010120160843.A17947@vitelus.com>; from aaronl@vitelus.com on Sat, Jan 20, 2001 at 04:08:43PM -0800

On Sat, Jan 20, 2001 at 04:08:43PM -0800, Aaron Lehmann wrote:
> 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?

If you look at the code, you will discover, that a certain core-layer of 
netfilter and iptables are used all the time, regardless if you choose to
use iptables, ipchains or ipfwadm backwards compatibility.

The backwards compatibility (either ipfwadm or ipchains) modules are built
on top of this core. The frontend (setsockopt/getsockopt to userspace 
config tool) looks the same, the backend is totally different.

This is the reason why - of course - the old ip_masq_XXX helpers don't
work anymore. They are written for a kludgy old backend which isn't present
anymore.

There is no particular reason why the current ipchains / ipfwadm emulation
modules don't use the new ip_conntrack_XXX / ip_nat_XXX stuff, just nobody
got around implementing it. (there are comments at the respective position
inside the code).

If you or somebody else wants to volunteer writing this, we'll appreciate
any patches.

btw: it's probably a good idea to move this discussion to 
netfilter@lists.samba.org

-- 
Live long and prosper
- Harald Welte / laforge@gnumonks.org                http://www.gnumonks.org
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M- 
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
-
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/

  parent reply	other threads:[~2001-01-24 12:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-20 22:46 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
2001-01-21  0:22       ` Doug McNaught
2001-01-24 12:37       ` Harald Welte [this message]
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=20010124133740.W6055@coruscant.gnumonks.org \
    --to=laforge@gnumonks.org \
    --cc=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 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®