From: J Sloan <jjs@pobox.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [OT] Re: 2.4 and ipmasq modules
Date: Sat, 20 Jan 2001 17:55:17 -0800 [thread overview]
Message-ID: <3A6A4185.AF34DBA7@pobox.com> (raw)
In-Reply-To: <20010120144616.A16843@vitelus.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Aaron Lehmann wrote:
> 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.
It's working here for me - the netfilter modules are named differently:
# lsmod
Module Size Used by
<snip>
iptable_filter 1824 0 (autoclean) (unused)
ip_nat_ftp 3280 0 (unused)
iptable_nat 13120 1 [ip_nat_ftp]
ip_conntrack_ftp 2016 0 (unused)
ip_conntrack 13408 2 [ip_nat_ftp iptable_nat ip_conntrack_ftp]
ip_tables 10784 4 [iptable_filter iptable_nat]
<snip>
[-- Attachment #2: Type: text/html, Size: 2053 bytes --]
next prev parent reply other threads:[~2001-01-21 1:55 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 ` J Sloan [this message]
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=3A6A4185.AF34DBA7@pobox.com \
--to=jjs@pobox.com \
--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