From: Filip Sneppe <filip.sneppe@gmail.com>
To: Mario Ohnewald <mario.Ohnewald@gmx.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: ftp contrack
Date: Tue, 25 Jan 2005 13:15:30 +0100 [thread overview]
Message-ID: <9151ac2a05012504156caf097b@mail.gmail.com> (raw)
In-Reply-To: <22793.1106524634@www29.gmx.net>
On Mon, 24 Jan 2005 00:57:14 +0100 (MET), Mario Ohnewald
<mario.Ohnewald@gmx.de> wrote:
> Hello List!
>
> I am trying to redirect (NAT) to a internal ftp box (but both have a public
> ip).
> I am using those rules:
>
> modprobe ip_conntrack_ftp ports=21,2121
> modprobe ip_nat_ftp
Hi Mario,
Add "ports=21,2121" to the "modprobe ip_nat_ftp" command.
That should do the trick.
modprobe ip_nat_ftp ports=21,2121
Regards,
Filip
next prev parent reply other threads:[~2005-01-25 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 23:57 ftp contrack Mario Ohnewald
2005-01-25 12:15 ` Filip Sneppe [this message]
2005-01-25 12:53 ` Jose Maria Lopez
2005-01-25 9:50 ` Mario Ohnewald
2005-01-25 13:43 ` Filip Sneppe
2005-01-25 10:20 ` Mario Ohnewald
2005-01-25 15:25 ` Filip Sneppe
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 20:04 Piszcz, Justin Michael
2005-01-26 13:29 ` Jose Maria Lopez
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=9151ac2a05012504156caf097b@mail.gmail.com \
--to=filip.sneppe@gmail.com \
--cc=mario.Ohnewald@gmx.de \
--cc=netfilter@lists.netfilter.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