Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of bselack@digipixart.com
 designates 207.176.38.14 as permitted sender)
From: "Barrie Selack" <bselack@digipixart.com>
To: "Daniel F. Savarese" <dfs@savarese.org>,
	"Commons User" <commons-user@jakarta.apache.org>
Subject: Re: FTPClient occasionally opens port to self instead of server 
Date: Fri, 4 Nov 2005 08:43:12 -0500
Message-Id: <20051104134312.19195@mail.digipixart.com>
In-Reply-To: <200511040428.jA44SDGr010568@gandalf.savarese.org>
References: <20051103141327.16298@mail.digipixart.com>
 <200511040428.jA44SDGr010568@gandalf.savarese.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In the ftp log (pureFTPd) it never shows a PASV command for
24.www.xxx.yy, on for 10.2.1.10 (the local address behind a firewall). 

Could it be a firewall problem (SonicWall) getting the IP wrong. I hadn't
thought too much about that, but if it's the one rewriting the 10.2.1.10
address to the public IP, then it may be the one with the problem. Any
thoughts or experiences with that? The firewall is set up in one-to-one
NAT so 10.2.1.10 -> 207.www.xxx.yy

Barrie

>
>In message <20051103141327.16298@mail.digipixart.com>, "Barrie Selack"
writes:
>>PASV
>>227 Entering Passive Mode (24.www.xxx.yy,253,112)
>
>Okay, so that would mean it's not a bug in FTPClient.  The FTP server
>is sending back 24.www.xxx.yy as the IP address for the data connection
>instead of the 207.www.xx.yy it should be sending.  I couldn't see any
>way in the code for FTPClient to cause a local IP to be used, so that's
>consistent.  Unfortunately, it means your FTP server is at fault (or
>some library it depends on, maybe getsockname is buggy).
>
>>happens much more. Just FYI, I switched the code to use edtFTPj and
>>tested several times with no problems.
>
>If edtFTPj is working, then it won't work with FTP servers that have
>have multiple interfaces/IP addresses because it must not be parsing the
>PASV reply.
>
>I'm not sure how to proceed.  I'm hesitant to special-case a workaround
>for a buggy FTP server.  Any suggestions?
>
>daniel
>
>-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
>    s a v a r e s e      # In distant lands, I hear the call of my home.
>   software research     # Yet my work is not done.  My journey's just begun.
>http://www.savarese.com/ #  -- http://www.sleepandthetraveller.com/
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org