|
OK I got it working!
I did have persistence on though :-{}
>TCP 172.24.1.240:ftp wlc persistent 360
> -> 192.168.1.20:ftp Masq 1 2 1
I'm using guildftp as the server.
I had to go into the admin menu => options and under the
Advanced settings tab use DNS (which gives the rip...)
to resolve the ip in pasv.
ncftp worked, @#$%^&% windows programs... :^D
Thanks Rutger and Joseph for your help
-----Original Message-----
From: Joseph Mack [mailto:mack.joseph@xxxxxxx]
Sent: Thursday, October 24, 2002 8:11 AM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx; R.vanOosten@xxxxxxxxxxx;
tim@xxxxxxxxxxxxxxx
Subject: Re: lvs-NAT ftp (Kernel 2.4.19)
Rutger van Oosten wrote:
>
> > I had an issue with lvs_nat and ftp as well.
> fails for me too on 0.9.4/2.4.9 with ncftp using PASV, but works fine
> for the standard active mode command line ftp client.
just found that PASV ftp (via ncftp) works for NAT if you make the service
ftp
persistent or if you make all ports (port 0) persistent.
This is the method used to get ftp to work with LVS-DR and LVS-Tun.
If I then add in a non-persistent service (like telnet) to mimic Tim's
setup (with non-persistent http), PASV ftp still works. Presumably
then Tim's setup should work, although it doesn't.
Ultimately the problem appears to be with the ftp helper.
Joe
--
Joseph Mack PhD, Senior Systems Engineer, SAIC contractor
to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
