Well I guess I got it mostly wrong, as you said
they're running their ftpd on 864, which as you
found, makes it nearly certain that everyone with
a firewall will fail to be able to reach them.
What it has to do with NAT is this, and I'll try
to keep it simple:
- The ip_nat_ftp module on Bering or
the ip_masq_ftp module on Dachstein/Oxygen
watches for traffic destined for port 21 and
further searches those packets for the ftp client
command "PORT aaa.bbb.ccc.ddd.eee.fff"
- You're asking it to watch for traffic destined to
21 and 864, now.
- When it finds the PORT command in that traffic, it'll
translates the private address in the PORT command
(the aaa.bbb.ccc.ddd part) into your public eth0 ip address.
In my case, my PORT commands look like this before and after:
PORT 10.1.1.1.234.12
PORT 63.193.214.179.234.12
Something like that :)
- Then dude's ftpd will see your valid public IP and
a valid port and will try to send the file there,
rather than try to send it to the private 192.168.1.x
type of address, which is impossible, a 501.
best,
matthew
Joris Kempen wrote:
> Hi people,
>
> I got it working.
>
> Just opened port 864 by using
>
> IP_MASK_FTP port=21,864
>
> his FTP is just running at this port. still don't know what it has to do
> with IP-NAT
>
> but thanks for all suggestions
>
> Met vriendelijke groet,
>
> Joris Kempen
> St. Ursulahof 47
> 5995 CB Kessel
>
> email: [EMAIL PROTECTED]
> tel. nr.: 06 1257 4228
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
