LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

RE: How to NAT The FTP-DATA Connection?

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: How to NAT The FTP-DATA Connection?
From: "Robinson, Eric" <eric.robinson@xxxxxxxxxx>
Date: Fri, 22 Dec 2006 13:55:00 -0800
Joe said:
>The usual reasons are in the HOWTO. Did you read it yet?

In read it back in July when I first implemented our load balancers. At
that time, I ran into some trouble with FTP and LVS-NAT. You suggested
that I make sure the ftp helper module was running. I read the HOWTO and
learned that the helper module is only required for passive FTP, so that
line of discussion ended. Not much later, I discovered that the real
problem was a bug in ldirectord where it was using -a to add a rule
where it should have been using -e to edit an existing one. Horms
patched ldirectord and I've been happy as a clam ever since. That is,
until I recently realized what was going on with FTP-DATA connections
not being NATed.

So I read sections 4 and 13 again just now, but I'm no closer to
understanding what to do next. You must admit, those sections or the
HOWTO are pretty fragmented and difficult to digest. As far as I can
tell, everything is configured correctly. I'm not using passive FTP (it
is not an option) so the ftp helper question is moot. Also, vsftp
running on my RealServers is using source port 20 for FTP-DATA, just as
it should, so problems related to using unpriviledged ports are also
ruled out. 

It's certainly possible that I'm missing something in the HOWTO, and I'd
be delighted if you pointed out the error of my ways. :-)

--Eric


Disclaimer - December 22, 2006 
This email and any files transmitted with it are confidential and intended 
solely for LinuxVirtualServer.org users mailing list.. If you are not the named 
addressee you should not disseminate, distribute, copy or alter this email. Any 
views or opinions presented in this email are solely those of the author and 
might not represent those of Physician Select Management (PSM) or Physician's 
Managed Care (PMC). Warning: Although the message sender has taken reasonable 
precautions to ensure no viruses are present in this email, neither PSM nor PMC 
can accept responsibility for any loss or damage arising from the use of this 
email or attachments.

<Prev in Thread] Current Thread [Next in Thread>