perfsonar-user - [perfsonar-user] perfSONAR v4 and IPv6
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Charley Kneifel <>
- To: "" <>
- Subject: [perfsonar-user] perfSONAR v4 and IPv6
- Date: Fri, 30 Jun 2017 01:13:06 +0000
- Accept-language: en-US
- Authentication-results: oit.duke.edu; spf=none
- Authentication-results: internet2.edu; dkim=none (message not signed) header.d=none;internet2.edu; dmarc=none action=none header.from=duke.edu;
- Ironport-phdr: 9a23:REVS4xL4b0W9FcwWBNmcpTZWNBhigK39O0sv0rFitYgUKvvxwZ3uMQTl6Ol3ixeRBMOAtKIC1rKempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBWB6kG1uHQKFw/xLg1zL/6wB5Xfley20fy/4Zvef18OiTagK/smNBisox7WsMAMxJZ5J7wZyx3Vr2FOdvgMg25kOATAsQz745Kb/Jd59ylB89En+s9OXKGyK684RKZcASVgMGY45cPmsTHPUAiCoHYQTzNFwVJzHwHZ4USiDd/KuSzgu78l1Q==
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Hello All,
I am unable to get IPv6 tests to work.
I can ping a remote IPv6 node:
ping6 sdsc-pt1-v6.es.net
I have added an IPv6 host to a PS4 node and confirmed that it is set for IPv6
PING sdsc-pt1-v6.es.net(sdsc-pt1-v6.es.net) 56 data bytes 64 bytes from sdsc-pt1-v6.es.net: icmp_seq=1 ttl=48 time=107 ms 64 bytes from sdsc-pt1-v6.es.net: icmp_seq=2 ttl=48 time=106 ms 64 bytes from sdsc-pt1-v6.es.net: icmp_seq=3 ttl=48 time=105 ms 64 bytes from sdsc-pt1-v6.es.net: icmp_seq=4 ttl=48 time=104 ms ^C --- sdsc-pt1-v6.es.net ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3726ms rtt min/avg/max/mdev = 104.495/105.886/107.681/1.283 ms name services are resolving properly [root@ps-node-c pscheduler]# nslookup -type=aaaa sdsc-pt1-v6.es.net
Server: 192.168.202.5 Address: 192.168.202.5#53 Non-authoritative answer: sdsc-pt1-v6.es.net has AAAA address 2001:400:1101:1150::3
I see no tests with the hostname (sdsc-pt1-v6) in the pscheduler logs and no tests with --ip-version=6 in the logs either.
I do have a private v4 address, but have a public V6 address that is exposed for icmpv6.
Anyone have any suggestions?
Charley
|
- [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/28/2017
- Re: [perfsonar-user] Trouble after upgrade, Andrew Lake, 06/28/2017
- Re: [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/29/2017
- [perfsonar-user] perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- Re: [perfsonar-user] RE: perfSONAR v4 and IPv6, Andrew Lake, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- RE: [perfsonar-user] Trouble after upgrade, Garnizov, Ivan (RRZE), 06/30/2017
- Re: [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/30/2017
- Re: [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/29/2017
- Re: [perfsonar-user] Trouble after upgrade, Andrew Lake, 06/28/2017
Archive powered by MHonArc 2.6.19.