perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

What type of tests are you trying to run? There is a known issue with rtt tests and two hostnames that only have AAAA records detailed here: https://github.com/perfsonar/pscheduler/issues/431

We also just pushed out 1.0.0.3 of pscheduler a couple weeks ago with some IPv6-related fixes for throughput tests so may be good to make sure you are running those. 

Thanks,

Andy

On May 30, 2017 at 8:12:12 AM, Bill Owens () wrote:

I believe this is a known bug that was closed last fall without being resolved: https://github.com/perfsonar/pscheduler/issues/233

 

I’ve tried to get some attention to it but haven’t had time to dig into it.

 

Bill.

 

From: <> on behalf of Charley Kneifel <>
Date: Saturday, May 27, 2017 at 8:31 PM
To: "" <>
Subject: [perfsonar-user] Re: Lookup Service CentOS 7

 

Is there anything special I need to do to get IPv6 working?

 

I have a privately IP'ed host that I can ping6 to IPv6 addresses such as:

 

perf-lax.sinet.ad.jp

 

or

 

nersc-pt1-v6.es.net

 

but I don't get any test results when I add them.

 

If I add perf-lax.sinet.ad.jp and check the IPv4 and IPv6 check boxes, then I get:

 

May 27 19:04:21 ps-node-a runner INFO     673928: With ping: rtt --count 10 --dest perf-lax.sinet.ad.jp --interval PT1S --ip-version 4 --source 192.168.202.151 --length 1000 --ttl 255

 

in my /var/log/messages file but nothing with an --ip-version 6 and nothing when it's just IPv6 checked.  I have several other hosts that I am trying to check via direct IPv6 addresses including two on the local network.

 

The PS node hosts show the v6 addresses in ifconfig and in the PS dashboard

 

What am I missing?

 

Charley