Re: [Globus-discuss] Controlling client-side TCP port range withglobus-url-copy

[Michael Link <mlink@mcs.anl.gov>]

Karen,

Use GLOBUS_TCP_SOURCE_RANGE=min,max to control the outbound ports. 
 GLOBUS_TCP_PORT_RANGE only controls listening ports.

Mike

Karen Loughran wrote:
> I'm trying to control the port range used by globus-url-copy (version
> 3.6 from GT3.2.1) on the client side.
>
> On the server side I have been able to successfully restrict the data
> channel port ranges by setting GLOBUS_TCP_PORT_RANGE=50000,50100 in the
> /etc/xinetd.d/grid-ftp configuration file. And by monitoring the TCP
> traffic between client and server I can see that it is in fact using
> port 50,000 for transfer. 
> On the client side I have tried setting the environment variable
> GLOBUS_TCP_PORT_RANGE=50000,50100 but it still chooses an arbitrary port
> outside this range.
>
> I have also separately tried using The Java Cog Kit version 1.1 and set
> the following within the cog.properties file:
>
> tcp.port.range=50000,50100
>
> But globus-url-copy still chooses an arbitrary port outside this range
> on the client side.
>
> Is it possible to successfully restrict the port range used on the
> client side of a GridFTP globus-url-copy file transmission ?  Please can
> anyone explain how they do this ?
>
> Thanks in advance,
>
> Karen Loughran
>
> PS. I'm using Red Hat Linux Version 9
>
> Belfast e-Science Centre
> School of Computer Science
> Queen's University Belfast
>
>  
> -
> To Unsubscribe: send mail to majordomo@globus.org
> with "unsubscribe discuss" in the body of the message
-
To Unsubscribe: send mail to majordomo@globus.org
with "unsubscribe discuss" in the body of the message