From: Toby <tobia.conforto@linux.it>
To: netfilter@lists.netfilter.org
Subject: Re: iptables / FTP masquerading: Port command illega
Date: Wed, 23 Mar 2005 18:09:50 +0100 [thread overview]
Message-ID: <20050323170950.GC25754@ikkoku.ath.cx> (raw)
In-Reply-To: <1111590778.4241877a4e631@webmail.telus.net>
amateurguy@telus.net wrote:
> When i look at the packets, I see the client sending a Port cmd using
> its non-routable IP. This then passes through a firewall, and the
> source IP gets translated to a public IP.
The source IP does, but probably the IP inside the PORT command doesn't.
You need to load ip_nat_ftp in THAT firewall and tell it to monitor port
29 (you do that in the "modprobe ip_nat_ftp" commandline.)
Either that, or more simply configure the client ftp software and tell
it what its real ip address is.
I don't know if you can do anything on the server side.
As for that other problem (port 21 working differently than port 29) I
don't know, it could be anything.
Cheers
Toby
next prev parent reply other threads:[~2005-03-23 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 15:12 iptables / FTP masquerading: Port command illega amateurguy
2005-03-23 17:09 ` Toby [this message]
2005-03-23 17:35 ` Jason Opperisano
2005-03-23 19:31 ` amateurguy
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=20050323170950.GC25754@ikkoku.ath.cx \
--to=tobia.conforto@linux.it \
--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 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.