Try loading two additional netfilter modules to do conection tracking for your
ftp conection called "ip_conntrack_ftp" and "ip_nat_ftp" this should sort out
your problem
Regards
Corne Alberts
Information Architect
Quoting Francisco Castillo <[EMAIL PROTECTED]>:
>
> Hello,
>
> I has a proftpd
Hello,
I has a proftpd server on a linux debian woody with a NAT sheeme. So my
proftpd is listening on the 192.168.0.X private ip and my router has
mapping the ports from 4 to 40010 from the public ip to the
192.168.0.X ip in order to allow pasive port transfers from internet. So
i has this c
Ce jour Mon, 15 Nov 2004, Francisco Castillo a dit:
>
>
> Hello,
>
>
> when i connect from a cuteftp client from a 192.168.0.Y ip the client get
> the correct pasive port to get data (4) from the proftpd server but
> if i try to access from a public client ip (with cuteftp too) the server
Hello,I has a proftpd server on a linux debian
woody with a NAT sheeme. So myproftpd is listening on the 192.168.0.X
private ip and my router hasmapping the ports from 4 to 40010 from the
public ip to the192.168.0.X ip in order to allow pasive port transfers from
internet. Soi has this c
Hello,
I has a proftpd server on a linux debian woody with a NAT sheeme. So my
proftpd is listening on the 192.168.0.X private ip and my router has
mapping the ports from 4 to 40010 from the public ip to the
192.168.0.X ip in order to allow pasive port transfers from internet. So
i has this
5 matches
Mail list logo