You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Neil Aggarwal <ne...@JAMMConsulting.com> on 2007/02/08 04:31:52 UTC
[net-ftp] FTPS timeout when trying to upload a file
Hello:
I downloaded the commons-net-2.0 snapshot jar from
http://people.apache.org/~rwinston/commons-net-2.0/
When I try to upload a file to a server that
requires FTPS, I get a timeout when I call the storeFile
method.
Here is the stacktrace:
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at javax.net.DefaultSocketFactory.createSocket(Unknown Source)
at
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:516
)
at
org.apache.commons.net.ftp.FTPSClient._openDataConnection_(FTPSClient.java:4
69)
at
org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:388)
at
org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1391)
Here is my code:
ftps = new FTPSClient("SSL");
ftps.addProtocolCommandListener(new PrintCommandListener(new
PrintWriter(System.out)));
ftps.connect("admin.quiksilver.com");
ftps.login("neil", "mypass"));
ftps.enterLocalPassiveMode();
FileInputStream inStream = new FileInputStream("myFile.txt");
ftps.storeFile("myFile.txt",inStream);
Here is the output from the protocol command listener:
220 Gene6 FTP Server v3.8.0 (Build 34) ready...
AUTH TLS
234 AUTH command ok; starting SSL connection.
USER neil
331 Password required for neil.
PASS mypass
230 User neil logged in.
PASV
227 Entering Passive Mode (172,20,10,50,27,91)
Any ideas?
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [net-ftp] FTPS timeout when trying to upload a file
Posted by Paul Fremantle <pz...@gmail.com>.
Neil
Maybe try unticking the box:
Change data IP according to client source IP
in the Secure Options settings.
Paul
On 2/8/07, Neil Aggarwal <ne...@jammconsulting.com> wrote:
> Paul:
>
> I just had the vendor check their Gene6 server config.
> They have the public IP in the Redirect PASV IP
> box but the server is still handing out the private
> it.
>
> Any ideas?
>
> Thanks,
> Neil
>
> --
> Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
> FREE! Eliminate junk email and reclaim your inbox.
> Visit http://www.spammilter.com for details.
>
> -----Original Message-----
> From: Paul Fremantle [mailto:pzfreo@gmail.com]
> Sent: Thursday, February 08, 2007 12:19 PM
> To: Jakarta Commons Users List
> Subject: Re: [net-ftp] FTPS timeout when trying to upload a file
>
> Neil
>
> The Gene6 Secure FTP server that your customer is using has a place to
> set up the real IP address of the NAT connection. In the IP Binding
> section of the admin console under the passive mode setup there is a
> box labelled Redirect PASV IP. This is the "IP or hostname for Passive
> mode when the FTP server is behind a firewall".
>
> The server isn't broken, it just hasn't been configured properly. If
> they add the address 66.161.40.76 into that box everything will work.
>
> Paul
>
> On 2/8/07, Neil Aggarwal <ne...@jammconsulting.com> wrote:
> > Steffen:
> >
> > If the server is running on a private IP, how can you
> > expect it to know anything except the private IP?
> > A NAT route is upstream of the server.
> >
> > As I said, I do not control the server. The company
> > that hired me will not accept me telling them the
> > server from their vendor is broken and
> > that my code will not work.
> >
> > Given the discussion below, we need a solution that allows
> > the user to force an override for the IP address used for
> > passive connections.
> >
> > Thanks,
> > Neil
> >
> >
> > --
> > Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
> > FREE! Eliminate junk email and reclaim your inbox.
> > Visit http://www.spammilter.com for details.
> >
> > -----Original Message-----
> > From: Steffen Heil [mailto:lists@steffen-heil.de]
> > Sent: Thursday, February 08, 2007 11:16 AM
> > To: 'Jakarta Commons Users List'
> > Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
> >
> > Hi
> >
> > > I could be on a private subnet which is the same private
> > > subnet as the server. But, we could be in different locations.
> > >
> > > In that case, the solution below won't work.
> > >
> > > How about we do this:
> > >
> > > If (The IP given by the server is a private address)
> > > Always use the IP given by the call to
> > > the connect command.
> > > else
> > > Use the IP given by the server.
> > >
> > > That should fix this problem.
> >
> > I wouldn't do so.
> >
> > That SERVER is broken and needs to be fixed.
> > There is nothing a client can do.
> >
> > Please DO NOT try to handle that on the client. You cannot.
> >
> > First, there are cases where servers actually USE different IPs for
> control
> > and data connections, which is absolutely legal. (It is even essential if
> > you use FXP capabilities, which is basically pure FTP with 2 servers
> > involved.)
> >
> > Second, there ARE cases where servers with public OR private ips are NATed
> > to private IPs. [And maybe even from one private ip to another private
> ip.]
> > If you even happen to be on the same subnet as such a server, you still
> want
> > to be able to connect.
> >
> > Again, the server is broken. Get it fixed. Or reject to use it.
> > DON'T CHANGE THE CLIENT. Especially don't give it any strange semantic
> > rules, that make understanding problems impossible, if there is ever a
> > situation that you didn't expect. If at all, give the use a change to
> > optionally overwrite used IPs.
> >
> > Regards,
> > Steffen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-user-help@jakarta.apache.org
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Paul:
As I mentioned before, I do not control the server.
It is run by a vendor.
I will suggest to them to fix it, but I am not hopeful
they will change it.
I need a solution from the commons net FTP code since
it will not be acceptable if my software does not work
with this server. I was able to get the commons net FTP
client to work by overriding the value myself. It cannot
be more than 5 lines of code to provide a user controlled
override for that.
CoreFTP works with this server without a problem.
In the log, I see that it gets back the private IP
and overrides it with the public IP.
I am positive there will be other people that set up
servers behind NAT and do not set up the public IP
correctly.
In those situations, the commons net ftp code will be
blamed for not working correctly.
There has to be a reasonable workaround for this
situation.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Paul Fremantle [mailto:pzfreo@gmail.com]
Sent: Thursday, February 08, 2007 12:19 PM
To: Jakarta Commons Users List
Subject: Re: [net-ftp] FTPS timeout when trying to upload a file
Neil
The Gene6 Secure FTP server that your customer is using has a place to
set up the real IP address of the NAT connection. In the IP Binding
section of the admin console under the passive mode setup there is a
box labelled Redirect PASV IP. This is the "IP or hostname for Passive
mode when the FTP server is behind a firewall".
The server isn't broken, it just hasn't been configured properly. If
they add the address 66.161.40.76 into that box everything will work.
Paul
On 2/8/07, Neil Aggarwal <ne...@jammconsulting.com> wrote:
> Steffen:
>
> If the server is running on a private IP, how can you
> expect it to know anything except the private IP?
> A NAT route is upstream of the server.
>
> As I said, I do not control the server. The company
> that hired me will not accept me telling them the
> server from their vendor is broken and
> that my code will not work.
>
> Given the discussion below, we need a solution that allows
> the user to force an override for the IP address used for
> passive connections.
>
> Thanks,
> Neil
>
>
> --
> Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
> FREE! Eliminate junk email and reclaim your inbox.
> Visit http://www.spammilter.com for details.
>
> -----Original Message-----
> From: Steffen Heil [mailto:lists@steffen-heil.de]
> Sent: Thursday, February 08, 2007 11:16 AM
> To: 'Jakarta Commons Users List'
> Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
>
> Hi
>
> > I could be on a private subnet which is the same private
> > subnet as the server. But, we could be in different locations.
> >
> > In that case, the solution below won't work.
> >
> > How about we do this:
> >
> > If (The IP given by the server is a private address)
> > Always use the IP given by the call to
> > the connect command.
> > else
> > Use the IP given by the server.
> >
> > That should fix this problem.
>
> I wouldn't do so.
>
> That SERVER is broken and needs to be fixed.
> There is nothing a client can do.
>
> Please DO NOT try to handle that on the client. You cannot.
>
> First, there are cases where servers actually USE different IPs for
control
> and data connections, which is absolutely legal. (It is even essential if
> you use FXP capabilities, which is basically pure FTP with 2 servers
> involved.)
>
> Second, there ARE cases where servers with public OR private ips are NATed
> to private IPs. [And maybe even from one private ip to another private
ip.]
> If you even happen to be on the same subnet as such a server, you still
want
> to be able to connect.
>
> Again, the server is broken. Get it fixed. Or reject to use it.
> DON'T CHANGE THE CLIENT. Especially don't give it any strange semantic
> rules, that make understanding problems impossible, if there is ever a
> situation that you didn't expect. If at all, give the use a change to
> optionally overwrite used IPs.
>
> Regards,
> Steffen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Steffen Heil <li...@steffen-heil.de>.
Hi
> The server isn't broken, it just hasn't been configured
> properly. If they add the address 66.161.40.76 into that box
> everything will work.
Okay. Sorry. I misphrased that a litte.
Writing "the server is broken", I actually ment "the service is broken"
because "the configuration is wrong".
Obviously I didn't want to say anything about "The Gene6 Secure FTP server"s
at all. I don't even know these.
Regards,
Steffen
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Steffen Heil <li...@steffen-heil.de>.
> Okay. Sorry. I misphrased that a litte.
> Writing "the server is broken", I actually ment "the service
> is broken"
> because "the configuration is wrong".
>
> Obviously I didn't want to say anything about "The Gene6
> Secure FTP server"s at all. I don't even know these.
Just wanted to make clear that the problem is SERVER-based.
And no strang logic on the client-side should be used as workaround.
> Regards,
> Steffen
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Paul:
I just had the vendor check their Gene6 server config.
They have the public IP in the Redirect PASV IP
box but the server is still handing out the private
it.
Any ideas?
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Paul Fremantle [mailto:pzfreo@gmail.com]
Sent: Thursday, February 08, 2007 12:19 PM
To: Jakarta Commons Users List
Subject: Re: [net-ftp] FTPS timeout when trying to upload a file
Neil
The Gene6 Secure FTP server that your customer is using has a place to
set up the real IP address of the NAT connection. In the IP Binding
section of the admin console under the passive mode setup there is a
box labelled Redirect PASV IP. This is the "IP or hostname for Passive
mode when the FTP server is behind a firewall".
The server isn't broken, it just hasn't been configured properly. If
they add the address 66.161.40.76 into that box everything will work.
Paul
On 2/8/07, Neil Aggarwal <ne...@jammconsulting.com> wrote:
> Steffen:
>
> If the server is running on a private IP, how can you
> expect it to know anything except the private IP?
> A NAT route is upstream of the server.
>
> As I said, I do not control the server. The company
> that hired me will not accept me telling them the
> server from their vendor is broken and
> that my code will not work.
>
> Given the discussion below, we need a solution that allows
> the user to force an override for the IP address used for
> passive connections.
>
> Thanks,
> Neil
>
>
> --
> Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
> FREE! Eliminate junk email and reclaim your inbox.
> Visit http://www.spammilter.com for details.
>
> -----Original Message-----
> From: Steffen Heil [mailto:lists@steffen-heil.de]
> Sent: Thursday, February 08, 2007 11:16 AM
> To: 'Jakarta Commons Users List'
> Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
>
> Hi
>
> > I could be on a private subnet which is the same private
> > subnet as the server. But, we could be in different locations.
> >
> > In that case, the solution below won't work.
> >
> > How about we do this:
> >
> > If (The IP given by the server is a private address)
> > Always use the IP given by the call to
> > the connect command.
> > else
> > Use the IP given by the server.
> >
> > That should fix this problem.
>
> I wouldn't do so.
>
> That SERVER is broken and needs to be fixed.
> There is nothing a client can do.
>
> Please DO NOT try to handle that on the client. You cannot.
>
> First, there are cases where servers actually USE different IPs for
control
> and data connections, which is absolutely legal. (It is even essential if
> you use FXP capabilities, which is basically pure FTP with 2 servers
> involved.)
>
> Second, there ARE cases where servers with public OR private ips are NATed
> to private IPs. [And maybe even from one private ip to another private
ip.]
> If you even happen to be on the same subnet as such a server, you still
want
> to be able to connect.
>
> Again, the server is broken. Get it fixed. Or reject to use it.
> DON'T CHANGE THE CLIENT. Especially don't give it any strange semantic
> rules, that make understanding problems impossible, if there is ever a
> situation that you didn't expect. If at all, give the use a change to
> optionally overwrite used IPs.
>
> Regards,
> Steffen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [net-ftp] FTPS timeout when trying to upload a file
Posted by Paul Fremantle <pz...@gmail.com>.
Neil
The Gene6 Secure FTP server that your customer is using has a place to
set up the real IP address of the NAT connection. In the IP Binding
section of the admin console under the passive mode setup there is a
box labelled Redirect PASV IP. This is the "IP or hostname for Passive
mode when the FTP server is behind a firewall".
The server isn't broken, it just hasn't been configured properly. If
they add the address 66.161.40.76 into that box everything will work.
Paul
On 2/8/07, Neil Aggarwal <ne...@jammconsulting.com> wrote:
> Steffen:
>
> If the server is running on a private IP, how can you
> expect it to know anything except the private IP?
> A NAT route is upstream of the server.
>
> As I said, I do not control the server. The company
> that hired me will not accept me telling them the
> server from their vendor is broken and
> that my code will not work.
>
> Given the discussion below, we need a solution that allows
> the user to force an override for the IP address used for
> passive connections.
>
> Thanks,
> Neil
>
>
> --
> Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
> FREE! Eliminate junk email and reclaim your inbox.
> Visit http://www.spammilter.com for details.
>
> -----Original Message-----
> From: Steffen Heil [mailto:lists@steffen-heil.de]
> Sent: Thursday, February 08, 2007 11:16 AM
> To: 'Jakarta Commons Users List'
> Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
>
> Hi
>
> > I could be on a private subnet which is the same private
> > subnet as the server. But, we could be in different locations.
> >
> > In that case, the solution below won't work.
> >
> > How about we do this:
> >
> > If (The IP given by the server is a private address)
> > Always use the IP given by the call to
> > the connect command.
> > else
> > Use the IP given by the server.
> >
> > That should fix this problem.
>
> I wouldn't do so.
>
> That SERVER is broken and needs to be fixed.
> There is nothing a client can do.
>
> Please DO NOT try to handle that on the client. You cannot.
>
> First, there are cases where servers actually USE different IPs for control
> and data connections, which is absolutely legal. (It is even essential if
> you use FXP capabilities, which is basically pure FTP with 2 servers
> involved.)
>
> Second, there ARE cases where servers with public OR private ips are NATed
> to private IPs. [And maybe even from one private ip to another private ip.]
> If you even happen to be on the same subnet as such a server, you still want
> to be able to connect.
>
> Again, the server is broken. Get it fixed. Or reject to use it.
> DON'T CHANGE THE CLIENT. Especially don't give it any strange semantic
> rules, that make understanding problems impossible, if there is ever a
> situation that you didn't expect. If at all, give the use a change to
> optionally overwrite used IPs.
>
> Regards,
> Steffen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Steffen:
That is a good idea. I think it is better too.
I will contribute it as a patch to the JIRA I
created.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Steffen Heil [mailto:lists@steffen-heil.de]
Sent: Tuesday, February 13, 2007 2:56 AM
To: 'Jakarta Commons Users List'
Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
Hi
> How about adding a method called:
> forceConnectedHostForPassiveConnections(boolean)
>
> If someone sets the boolean to true, the code will use the
> host specified in the connect call instead of the passive
> host given by the server.
>
> This looks clean to me and will require very little code changes.
I would prefer a solution with an added method called:
overrideHostForPassiveConnections(InetAddress)
That would solve the same, but could also be used in other scenarios.
Regards,
Steffen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Steffen Heil <li...@steffen-heil.de>.
Hi
> How about adding a method called:
> forceConnectedHostForPassiveConnections(boolean)
>
> If someone sets the boolean to true, the code will use the
> host specified in the connect call instead of the passive
> host given by the server.
>
> This looks clean to me and will require very little code changes.
I would prefer a solution with an added method called:
overrideHostForPassiveConnections(InetAddress)
That would solve the same, but could also be used in other scenarios.
Regards,
Steffen
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Rory:
How about adding a method called:
forceConnectedHostForPassiveConnections(boolean)
If someone sets the boolean to true, the code will
use the host specified in the connect call instead
of the passive host given by the server.
This looks clean to me and will require very little
code changes.
If you like it, I am willing to contibute it as a
patch.
Please let me know what you think.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Rory Winston [mailto:rwinston@eircom.net]
Sent: Thursday, February 08, 2007 2:40 PM
To: Jakarta Commons Users List
Subject: Re: [net-ftp] FTPS timeout when trying to upload a file
Neil
I just read your previous email. If you do have an idea in regards to an
elegant solution to the problem, feel free to create a JIRA issue and
patch and I will review. But I really would only consider putting
something in if a) it's elegant and clean and (b) if commons-net is
really the odd one out amongst FTP clients, and is the only one that
cant handle this. But as stated before, this really does seem to be a
server config issue.
Thanks
Rory
Rory Winston wrote:
> Hi guys
>
> Steffen/Paul, thanks for your excellent input on this. I didnt get a
> chance to look at this myself (and I didn't remember when reading the
> email that the IP address was actually a reserved private address).
>
> Neil,the guys are correct - this is a server configuration issue - its
> not even a fault with the server per se, just with the server's
> configuration in regards to NATed clients. There is no real fix for
> this, and I would be hesitant to introduce some kind of hacky
> solution. Your case is the only instance I have seen of this so far.
>
> Thanks
> Rory
>
> Steffen Heil wrote:
>
>> Hi
>>
>>
>>> If the server is running on a private IP, how can you expect it to know
>>>
>> anything except the private IP?
>>
>> Administrators that make SFTP-Servers available to the public
>> internet, NEED
>> to be aware of that problems and as such NEED to configure the server
>> accordingly. Otherwise they are not doing their jobs. SFTP-Servers do
>> have
>> configuration options for this. (Like -P <ip> for pure-ftpd for
>> example.)
>>
>> You wrote:
>>
>>> Given the discussion below, we need a solution that allows the user
>>> to force an override for the IP address used for passive connections.
>>>
>>
>> I wrote:
>>
>>> If at all, give the use a change to optionally overwrite used IPs.
>>>
>>
>> Which matches... And solves the problem without introducing broken
>> logic.
>> If you are ONLY connecting to that server, don't ask at all. You know
>> how to
>> connect.
>>
>> Regards,
>> Steffen
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [net-ftp] FTPS timeout when trying to upload a file
Posted by Rory Winston <rw...@eircom.net>.
Neil
I just read your previous email. If you do have an idea in regards to an
elegant solution to the problem, feel free to create a JIRA issue and
patch and I will review. But I really would only consider putting
something in if a) it's elegant and clean and (b) if commons-net is
really the odd one out amongst FTP clients, and is the only one that
cant handle this. But as stated before, this really does seem to be a
server config issue.
Thanks
Rory
Rory Winston wrote:
> Hi guys
>
> Steffen/Paul, thanks for your excellent input on this. I didnt get a
> chance to look at this myself (and I didn't remember when reading the
> email that the IP address was actually a reserved private address).
>
> Neil,the guys are correct - this is a server configuration issue - its
> not even a fault with the server per se, just with the server's
> configuration in regards to NATed clients. There is no real fix for
> this, and I would be hesitant to introduce some kind of hacky
> solution. Your case is the only instance I have seen of this so far.
>
> Thanks
> Rory
>
> Steffen Heil wrote:
>
>> Hi
>>
>>
>>> If the server is running on a private IP, how can you expect it to know
>>>
>> anything except the private IP?
>>
>> Administrators that make SFTP-Servers available to the public
>> internet, NEED
>> to be aware of that problems and as such NEED to configure the server
>> accordingly. Otherwise they are not doing their jobs. SFTP-Servers do
>> have
>> configuration options for this. (Like -P <ip> for pure-ftpd for
>> example.)
>>
>> You wrote:
>>
>>> Given the discussion below, we need a solution that allows the user
>>> to force an override for the IP address used for passive connections.
>>>
>>
>> I wrote:
>>
>>> If at all, give the use a change to optionally overwrite used IPs.
>>>
>>
>> Which matches... And solves the problem without introducing broken
>> logic.
>> If you are ONLY connecting to that server, don't ask at all. You know
>> how to
>> connect.
>>
>> Regards,
>> Steffen
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [net-ftp] FTPS timeout when trying to upload a file
Posted by Rory Winston <rw...@eircom.net>.
Hi guys
Steffen/Paul, thanks for your excellent input on this. I didnt get a
chance to look at this myself (and I didn't remember when reading the
email that the IP address was actually a reserved private address).
Neil,the guys are correct - this is a server configuration issue - its
not even a fault with the server per se, just with the server's
configuration in regards to NATed clients. There is no real fix for
this, and I would be hesitant to introduce some kind of hacky solution.
Your case is the only instance I have seen of this so far.
Thanks
Rory
Steffen Heil wrote:
> Hi
>
>
>> If the server is running on a private IP, how can you expect it to know
>>
> anything except the private IP?
>
> Administrators that make SFTP-Servers available to the public internet, NEED
> to be aware of that problems and as such NEED to configure the server
> accordingly. Otherwise they are not doing their jobs. SFTP-Servers do have
> configuration options for this. (Like -P <ip> for pure-ftpd for example.)
>
> You wrote:
>
>> Given the discussion below, we need a solution that allows
>> the user to force an override for the IP address used for
>> passive connections.
>>
>
> I wrote:
>
>> If at all, give the use a change to optionally overwrite used IPs.
>>
>
> Which matches... And solves the problem without introducing broken logic.
> If you are ONLY connecting to that server, don't ask at all. You know how to
> connect.
>
> Regards,
> Steffen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Steffen Heil <li...@steffen-heil.de>.
Hi
> If the server is running on a private IP, how can you expect it to know
anything except the private IP?
Administrators that make SFTP-Servers available to the public internet, NEED
to be aware of that problems and as such NEED to configure the server
accordingly. Otherwise they are not doing their jobs. SFTP-Servers do have
configuration options for this. (Like -P <ip> for pure-ftpd for example.)
You wrote:
> Given the discussion below, we need a solution that allows
> the user to force an override for the IP address used for
> passive connections.
I wrote:
> If at all, give the use a change to optionally overwrite used IPs.
Which matches... And solves the problem without introducing broken logic.
If you are ONLY connecting to that server, don't ask at all. You know how to
connect.
Regards,
Steffen
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Steffen:
If the server is running on a private IP, how can you
expect it to know anything except the private IP?
A NAT route is upstream of the server.
As I said, I do not control the server. The company
that hired me will not accept me telling them the
server from their vendor is broken and
that my code will not work.
Given the discussion below, we need a solution that allows
the user to force an override for the IP address used for
passive connections.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Steffen Heil [mailto:lists@steffen-heil.de]
Sent: Thursday, February 08, 2007 11:16 AM
To: 'Jakarta Commons Users List'
Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
Hi
> I could be on a private subnet which is the same private
> subnet as the server. But, we could be in different locations.
>
> In that case, the solution below won't work.
>
> How about we do this:
>
> If (The IP given by the server is a private address)
> Always use the IP given by the call to
> the connect command.
> else
> Use the IP given by the server.
>
> That should fix this problem.
I wouldn't do so.
That SERVER is broken and needs to be fixed.
There is nothing a client can do.
Please DO NOT try to handle that on the client. You cannot.
First, there are cases where servers actually USE different IPs for control
and data connections, which is absolutely legal. (It is even essential if
you use FXP capabilities, which is basically pure FTP with 2 servers
involved.)
Second, there ARE cases where servers with public OR private ips are NATed
to private IPs. [And maybe even from one private ip to another private ip.]
If you even happen to be on the same subnet as such a server, you still want
to be able to connect.
Again, the server is broken. Get it fixed. Or reject to use it.
DON'T CHANGE THE CLIENT. Especially don't give it any strange semantic
rules, that make understanding problems impossible, if there is ever a
situation that you didn't expect. If at all, give the use a change to
optionally overwrite used IPs.
Regards,
Steffen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Steffen Heil <li...@steffen-heil.de>.
Hi
> I could be on a private subnet which is the same private
> subnet as the server. But, we could be in different locations.
>
> In that case, the solution below won't work.
>
> How about we do this:
>
> If (The IP given by the server is a private address)
> Always use the IP given by the call to
> the connect command.
> else
> Use the IP given by the server.
>
> That should fix this problem.
I wouldn't do so.
That SERVER is broken and needs to be fixed.
There is nothing a client can do.
Please DO NOT try to handle that on the client. You cannot.
First, there are cases where servers actually USE different IPs for control
and data connections, which is absolutely legal. (It is even essential if
you use FXP capabilities, which is basically pure FTP with 2 servers
involved.)
Second, there ARE cases where servers with public OR private ips are NATed
to private IPs. [And maybe even from one private ip to another private ip.]
If you even happen to be on the same subnet as such a server, you still want
to be able to connect.
Again, the server is broken. Get it fixed. Or reject to use it.
DON'T CHANGE THE CLIENT. Especially don't give it any strange semantic
rules, that make understanding problems impossible, if there is ever a
situation that you didn't expect. If at all, give the use a change to
optionally overwrite used IPs.
Regards,
Steffen
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Steffen:
I just realized something:
I could be on a private subnet which is the same
private subnet as the server. But, we could be
in different locations.
In that case, the solution below won't work.
How about we do this:
If (The IP given by the server is a private address)
Always use the IP given by the call to
the connect command.
else
Use the IP given by the server.
That should fix this problem.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Neil Aggarwal [mailto:neil@jammconsulting.com]
Sent: Thursday, February 08, 2007 9:13 AM
To: 'Jakarta Commons Users List'
Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
Steffen:
I am running FTPSClient. I do not have control on
the server.
I think you are correnct in your assumption that the
server is running behind a NAT. It is on 172.20.10.50
and the public IP address that is mapped to it is 66.161.40.76.
According to RFC 1918:
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
The IP address is not a routable address and therefore the
connection to it will fail.
How about we do this in the FTPS Client when we get back
an IP address from the server:
if( we are on the same subnet as the server )
Use the IP provided by the server
else
if( the IP address given by the server is a private IP )
Overwrite the IP with the original IP address used to
connect to the server. We should know that from when
we connected to the server.
else
Use the IP provided by the server
That should solve this problem.
I am positive there will be others who will run into this problem
and blame FTPSClient as being broken.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Steffen Heil [mailto:lists@steffen-heil.de]
Sent: Thursday, February 08, 2007 2:42 AM
To: 'Jakarta Commons Users List'
Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
Hi
Warning: Wild guessing ahead:
> When my FTP client ...
So you have the client on your side.
> But, admin.quiksilver.com is 66.161.40.76, not 172.20.10.50.
Note, this IP is a private address, which is not even suppost to be routed.
> ... FTPSClient ...
And that is using ftpS.
So I guess the Server itself actually HAS 172.20.10.50 and is behind some
NAT router, which inspects protocolls to replace the internal ip
172.20.10.50 with the external one 66.161.40.76. I also suppose, this works
fine for FTP and external systems never see the internal address.
However, FTPS is SSL-encrypted and as such the NAT-router cannot change or
even see, what's inside the packet. So you get the original reply.
There is nothing you can do about that, except if you can reconfigure the
server.
SFTP doesn't play well behind nat routers, if not configured especially. For
example pure-ftps has an option to specify another ip address for answers as
that one and to ignore the servers ip address. The only other option would
be to enable the nat router to decrypt the ssl connection, which would be
both very cpu-consuming and insecure.
Regards,
Steffen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Steffen:
I am running FTPSClient. I do not have control on
the server.
I think you are correnct in your assumption that the
server is running behind a NAT. It is on 172.20.10.50
and the public IP address that is mapped to it is 66.161.40.76.
According to RFC 1918:
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
The IP address is not a routable address and therefore the
connection to it will fail.
How about we do this in the FTPS Client when we get back
an IP address from the server:
if( we are on the same subnet as the server )
Use the IP provided by the server
else
if( the IP address given by the server is a private IP )
Overwrite the IP with the original IP address used to
connect to the server. We should know that from when
we connected to the server.
else
Use the IP provided by the server
That should solve this problem.
I am positive there will be others who will run into this problem
and blame FTPSClient as being broken.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Steffen Heil [mailto:lists@steffen-heil.de]
Sent: Thursday, February 08, 2007 2:42 AM
To: 'Jakarta Commons Users List'
Subject: RE: [net-ftp] FTPS timeout when trying to upload a file
Hi
Warning: Wild guessing ahead:
> When my FTP client ...
So you have the client on your side.
> But, admin.quiksilver.com is 66.161.40.76, not 172.20.10.50.
Note, this IP is a private address, which is not even suppost to be routed.
> ... FTPSClient ...
And that is using ftpS.
So I guess the Server itself actually HAS 172.20.10.50 and is behind some
NAT router, which inspects protocolls to replace the internal ip
172.20.10.50 with the external one 66.161.40.76. I also suppose, this works
fine for FTP and external systems never see the internal address.
However, FTPS is SSL-encrypted and as such the NAT-router cannot change or
even see, what's inside the packet. So you get the original reply.
There is nothing you can do about that, except if you can reconfigure the
server.
SFTP doesn't play well behind nat routers, if not configured especially. For
example pure-ftps has an option to specify another ip address for answers as
that one and to ignore the servers ip address. The only other option would
be to enable the nat router to decrypt the ssl connection, which would be
both very cpu-consuming and insecure.
Regards,
Steffen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Steffen Heil <li...@steffen-heil.de>.
Hi
Warning: Wild guessing ahead:
> When my FTP client ...
So you have the client on your side.
> But, admin.quiksilver.com is 66.161.40.76, not 172.20.10.50.
Note, this IP is a private address, which is not even suppost to be routed.
> ... FTPSClient ...
And that is using ftpS.
So I guess the Server itself actually HAS 172.20.10.50 and is behind some
NAT router, which inspects protocolls to replace the internal ip
172.20.10.50 with the external one 66.161.40.76. I also suppose, this works
fine for FTP and external systems never see the internal address.
However, FTPS is SSL-encrypted and as such the NAT-router cannot change or
even see, what's inside the packet. So you get the original reply.
There is nothing you can do about that, except if you can reconfigure the
server.
SFTP doesn't play well behind nat routers, if not configured especially. For
example pure-ftps has an option to specify another ip address for answers as
that one and to ignore the servers ip address. The only other option would
be to enable the nat router to decrypt the ssl connection, which would be
both very cpu-consuming and insecure.
Regards,
Steffen
Re: [net-ftp] FTPS timeout when trying to upload a file
Posted by Rory Winston <rw...@eircom.net>.
Neil
What IP address is 172.20.10.50? Or is it your default gateway?
Thanks
Rory
> Hello all:
>
> I think I found something:
>
> When my FTP client switches to passive mode, it gets back
> this string from the server:
> 227 Entering Passive Mode (172,20,10,50,27,91)
> Which tells the FTP client to connect to 172.20.10.50
> port 7003.
>
> But, admin.quiksilver.com is 66.161.40.76, not
> 172.20.10.50.
>
> I when to the FTPSClient code and forced the
> method __parsePassiveModeReply to set the
> __passiveHost to "66.161.40.76"
> and tried it again.
>
> Everything worked fine.
>
> So, the server is giving out a bogus IP
> address in the passive reply. If we force it
> to be the IP address of the server, things work
> fine.
>
> Is there a way to countermand the incorrect behavior
> of the server?
>
> Thanks,
> Neil
>
> --
> Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
> FREE! Eliminate junk email and reclaim your inbox.
> Visit http://www.spammilter.com for details.
>
> -----Original Message-----
> From: Neil Aggarwal [mailto:neil@jammconsulting.com]
> Sent: Wednesday, February 07, 2007 9:32 PM
> To: commons-user@jakarta.apache.org
> Subject: [net-ftp] FTPS timeout when trying to upload a file
>
> Hello:
>
> I downloaded the commons-net-2.0 snapshot jar from
> http://people.apache.org/~rwinston/commons-net-2.0/
>
> When I try to upload a file to a server that
> requires FTPS, I get a timeout when I call the storeFile
> method.
>
> Here is the stacktrace:
>
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at javax.net.DefaultSocketFactory.createSocket(Unknown Source)
> at
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:516
> )
> at
> org.apache.commons.net.ftp.FTPSClient._openDataConnection_(FTPSClient.java:4
> 69)
> at
> org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:388)
> at
> org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1391)
>
> Here is my code:
>
> ftps = new FTPSClient("SSL");
> ftps.addProtocolCommandListener(new PrintCommandListener(new
> PrintWriter(System.out)));
> ftps.connect("admin.quiksilver.com");
> ftps.login("neil", "mypass"));
> ftps.enterLocalPassiveMode();
> FileInputStream inStream = new FileInputStream("myFile.txt");
> ftps.storeFile("myFile.txt",inStream);
>
> Here is the output from the protocol command listener:
>
> 220 Gene6 FTP Server v3.8.0 (Build 34) ready...
> AUTH TLS
> 234 AUTH command ok; starting SSL connection.
> USER neil
> 331 Password required for neil.
> PASS mypass
> 230 User neil logged in.
> PASV
> 227 Entering Passive Mode (172,20,10,50,27,91)
>
> Any ideas?
>
> Thanks,
> Neil
>
> --
> Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
> FREE! Eliminate junk email and reclaim your inbox.
> Visit http://www.spammilter.com for details.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [net-ftp] FTPS timeout when trying to upload a file
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Hello all:
I think I found something:
When my FTP client switches to passive mode, it gets back
this string from the server:
227 Entering Passive Mode (172,20,10,50,27,91)
Which tells the FTP client to connect to 172.20.10.50
port 7003.
But, admin.quiksilver.com is 66.161.40.76, not
172.20.10.50.
I when to the FTPSClient code and forced the
method __parsePassiveModeReply to set the
__passiveHost to "66.161.40.76"
and tried it again.
Everything worked fine.
So, the server is giving out a bogus IP
address in the passive reply. If we force it
to be the IP address of the server, things work
fine.
Is there a way to countermand the incorrect behavior
of the server?
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: Neil Aggarwal [mailto:neil@jammconsulting.com]
Sent: Wednesday, February 07, 2007 9:32 PM
To: commons-user@jakarta.apache.org
Subject: [net-ftp] FTPS timeout when trying to upload a file
Hello:
I downloaded the commons-net-2.0 snapshot jar from
http://people.apache.org/~rwinston/commons-net-2.0/
When I try to upload a file to a server that
requires FTPS, I get a timeout when I call the storeFile
method.
Here is the stacktrace:
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at javax.net.DefaultSocketFactory.createSocket(Unknown Source)
at
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:516
)
at
org.apache.commons.net.ftp.FTPSClient._openDataConnection_(FTPSClient.java:4
69)
at
org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:388)
at
org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1391)
Here is my code:
ftps = new FTPSClient("SSL");
ftps.addProtocolCommandListener(new PrintCommandListener(new
PrintWriter(System.out)));
ftps.connect("admin.quiksilver.com");
ftps.login("neil", "mypass"));
ftps.enterLocalPassiveMode();
FileInputStream inStream = new FileInputStream("myFile.txt");
ftps.storeFile("myFile.txt",inStream);
Here is the output from the protocol command listener:
220 Gene6 FTP Server v3.8.0 (Build 34) ready...
AUTH TLS
234 AUTH command ok; starting SSL connection.
USER neil
331 Password required for neil.
PASS mypass
230 User neil logged in.
PASV
227 Entering Passive Mode (172,20,10,50,27,91)
Any ideas?
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org