Bug 3387

Summary: client library doesn't respect GLOBUS_HOSTNAME
Product: GridFTP Reporter: Mike Link <mlink@mcs.anl.gov>
Component: GridFTPAssignee: Mike Link <mlink@mcs.anl.gov>
Status: NEW    
Severity: normal CC: allcock@mcs.anl.gov, bacon@mcs.anl.gov
Priority: P3    
Version: 4.0.0   
Target Milestone: ---   
Hardware: PC   
OS: All   

Description From 2005-05-19 20:30:52
Client/control lib no longer allow the local pasv address to be controlled by 
GLOBUS_HOSTNAME, required for a client that is behind a nat'ing firewall.  The 
local pasv address is forced to be the same interface that the control channel 
connection is on.  Seems to have been broken with the ipv6 updates.
------- Comment #1 From 2009-03-17 13:01:07 -------
An ALCF user is trying to run a command like:
client-host$ g-u-c gsiftp://alcf.host/file file:///local/file

It is failing because client-host is really sitting behind a NAT.  He sets
GLOBUS_HOSTNAME to the external name of his NAT to try to make it succeed, but
-dbg shows that the PASV command is being set for 192.168.0.4, his internal IP.

Is that this bug?  Is there any workaround?