Hi Suchandra, I don't have any experience with 'gfal-ls', but I can tell you that directory listing operations with GridFTP make use of the GridFTP control channel. By default, the GridFTP control channel uses TCP port 2811. Below is a link to our GCS firewall doc, which may be of use to you:
https://docs.globus.org/resource-provider-guide/#open-tcp-ports_section If you're just using GridFTP outside of a GCS install / Globus endpoint, then not all of the ports specified in that doc will be relevant to you. I hope the above is useful to you. -Dan ________________________________ From: gt-user-boun...@lists.globus.org [gt-user-boun...@lists.globus.org] on behalf of Suchandra Thapa [ssth...@uchicago.edu] Sent: Wednesday, July 20, 2016 12:23 PM To: gt-user@lists.globus.org Subject: [gt-user] gridftp issue Hi, I'm seeing an odd issue with gridftp that seems to be related to how gridftp uses ports. I have a gridftp server running in a LXC container. If I run gfal-ls on the container, I can get a directory listing. However gfal-ls hangs when run on the host running the container or another machine in the same data center. The issue is probably a firewall or router blocking something but I'm having trouble figuring out what's been blocked. What is the sequence for communications and ports being used when a gfal-ls is run against a gridftp server? If it matters, GLOBUS_TCP_PORT_RANGE is set to 20000,25000 . Thanks, Suchandra Suchandra Thapa sth...@ci.uchicago.edu<mailto:sth...@ci.uchicago.edu> Computation Institute Searle Chemistry Laboratory #201A 5735 South Ellis Avenue Chicago, IL 60637
