Hi, I'm new to the list but a long-time lftp user. I have a
question about "masqueraded" clients and servers taling to one
another using lftp.
The basic scenario is this. I have a Linksys BEFSR1 cable/DSL
router/firewall unit which does NAT for my internal network.
I run an FTP server on one machine on the internal network and
I am able to communicate with that server only if I disable
passive mode in my ftp client (e.g. coming from outside my
firewall).
I have a friend with an identical configuration, and I am
trying to grab files form his FTP server. The problem is, my
FTP session gets hung in non-passive mode once I start issuing
commands after the initial "PORT" command I send him. When
lftp sends out the PORT command, it uses my masqueraded
(e.g. un-routeable) IP address of 192.168.1.2. This is with
the FTP server running the Windows FTP server Serv-U.
I have no problem using non-passive FTP with many UNIX
servers, presumably because they apply some sanity checks to
the PORT command which is sent to them (e.g. they ignore the
192.168.1.2, and just connect back to the appropriate port on
the originating IP address). Serv-U doesn't seem to have this
level of intelligence.
Is there any way, or any desire, to add a configuration option
to lftp which says "use this IP address as the local address"?
--
cae at home dot com | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg.
