From: Rusty Russell <rusty@linuxcare.com.au>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 and ipmasq modules
Date: Tue, 23 Jan 2001 12:48:20 +1100 [thread overview]
Message-ID: <E14KsZI-0006IU-00@halfway> (raw)
In-Reply-To: Your message of "Sat, 20 Jan 2001 14:46:16 -0800." <20010120144616.A16843@vitelus.com>
In message <20010120144616.A16843@vitelus.com> you write:
> It was great to see that 2.4.0 reintroduced ipfwadm support! I had no
> need for ipchains and ended up using the wrapper around it that
> emulated ipfwadm. However, 2.[02].x used to have "special IP
> masquerading modules" such as ip_masq_ftp.o, ip_masq_quake.o, etc. I
> can't find these in 2.4.0. Where have they gone? Without important
> modules such as ip_masq_ftp.o I cannot use non-passive ftp from behind
> the masquerading firewall.
Hi Aaron,
The entire point of the netfilter kernel architecture is that we can
just ask for packets at certain points, no #ifdefs, special hacks,
etc. Unfortunately, the previous masquerading code (used in 2.0 and
2.2) looked really difficult to extract from the kernel. Netfilter
has changed a little since then (particularly NF_STOLEN), so it might
be possible now.
So I reimplimented 2.2-style masquerading on top of the new NAT
infrastructure: ideally this would mean that it could use the new
helpers, but there were some minor technical problems, and it was
never tested.
Those who berated Aaron for not wanting to upgrade: he is the Debian
maintainer for crashme, gtk-theme-switch, koules, pngcrush, and
xdaliclock. By wasting his time making him convert a perfectly
working system, you are taking away time from those projects. I'd
rather see him spend time on Cool Stuff(TM) which benefits all of us.
Cheers,
Rusty.
--
Premature optmztion is rt of all evl. --DK
-
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-23 1:48 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
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 [this message]
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=E14KsZI-0006IU-00@halfway \
--to=rusty@linuxcare.com.au \
--cc=aaronl@vitelus.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