...
| Code Block |
|---|
Examples (nb. –s defines the packet size) 123cottrell@pinger:~$/bin/ping6 -n -w 30 -c 2 -i 1 -s 64 ipv6.google.com PING ipv6.google.com(2607:f8b0:4007:80d::200e) 64 data bytes 72 bytes from 2607:f8b0:4007:80d::200e: icmp_seq=1 ttl=51 time=9.88 ms 72 bytes from 2607:f8b0:4007:80d::200e: icmp_seq=2 ttl=51 time=9.78 ms --- ipv6.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1011ms rtt min/avg/max/mdev = 9.780/9.834/9.888/0.054 ms 124cottrell@pinger:~$/bin/ping6 -n -w 30 -c 2 -i 1 -s 65 ipv6.google.com PING ipv6.google.com(2607:f8b0:4007:80d::200e) 65 data bytes 72 bytes from 2607:f8b0:4007:80d::200e: icmp_seq=1 ttl=51 (truncated) 72 bytes from 2607:f8b0:4007:80d::200e: icmp_seq=2 ttl=51 (truncated) --- ipv6.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1011ms rtt min/avg/max/mdev = 9.818/9.834/9.850/0.016 ms 125cottrell@pinger:~$/bin/ping6 -n -w 30 -c 2 -i 1 -s 1000 perfsonar-lt.cern.ch PING perfsonar-lt.cern.ch(2001:1458:301:a7bc::100:15) 1000 data bytes 1008 bytes from 2001:1458:301:a7bc::100:15: icmp_seq=1 ttl=45 time=151 ms 1008 bytes from 2001:1458:301:a7bc::100:15: icmp_seq=2 ttl=45 time=152 ms --- perfsonar-lt.cern.ch ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1152ms rtt min/avg/max/mdev = 151.987/151.996/152.006/0.389 ms |
This resulted in PingER's raw data measurements reporting:
| Code Block |
|---|
pinger.slac.stanford.edu 2620:114:d000:25a1::80 ipv6.google.com 2607:f8b0:4007:802::200e 100 1517962635 10 10 9.617 9.704 9.780
pinger.slac.stanford.edu 2620:114:d000:25a1::80 2607:f8b0:4007:802::200e 2607:f8b0:4007:802::200e 100 1517962640 10 10 9.594 9.648 9.705 |
Thus I added perfsonar-lt.cern.ch to NODEDETAILS. and got:
...