Testing IPv6

[Matt Pritchard]

Hi,

We've added IPv6 addresses to some test nodes and updated the GCS config with reference to here:

https://globus.stanford.edu/2023/11/22/ipv6-and-deployment-changes.html

i.e. doing this for each node:

globus-connect-server node update <node_uuid> --ip-address <IPV4_addr> --data-interface <IPV4_addr> --ip-address <IPv6_addr> --data-interface6 <IPv6_addr>

And an adaptation of the API test method suggests that these nodes are responding correctly, i.e.

curl -k --resolve <endpoint_dns>:443:<IPv6_addr> https://endpoint_dns/api/info

returns JSON containing "detail":"success" so all seems good.

But can anyone suggest a way to actually test a transfer that makes use of IPv6?

I'm ware that the ESnet Test DTNs have dual stack IPv4 & IPv6, so should a transfer initiated between one of those, and one of ouř nodes configured as above, result in a transfer done over IPv6? How would we know?

The gridftp.log entry for a test transfer seems to include the IPv4 address, so perhaps still just using IPv4. Is there any way to force IPv6, for a test (other than perhaps removing the data interface using the IPv4 address, using node update?)

Any help appreciated,

Thanks,

Matt 

[Karl Kornel]

Hi Matt, good morning!

I can think of a few things you could do to test:

First up, you can do a DNS lookup of the Endpoint’s DNS name.  The IPv6 address should be included in the results.

If both ends of a transfer can use IPv6, then I believe it should end up using IPv6.  Since you know what port range transfers use, instead of waiting for transfers to show up in the logs, you can start a transfer and then use netstat​ (or ss​) to look at active connections.  That should show you if IPv4 or IPv6 is being used!

~ Karl

To unsubscribe from this group and stop receiving emails from it, send an email to discuss+u...@globus.org.