...
The UBRU IPv4 PingER MA continues to function reliably. Charnsak also has an IPv6 PingER MA working at UBRU. He downloaded the latest version of pinger2.pl and set up a set of IPv6 hosts in <HostList> in pinger.xml. There are a couple of fixes needed to make the node name consistent. At a later stage we will need to figure out how to automatically support IPv6 beacons without messing up MA's that do not have IPv6 capability.
He is using ~ 100 IPv6 targets from Saqib. They are in the<HostList>.
Umar and Charnsak are working on making measurements from UBRU comparing ping/ICMP vs TCP RTTs. Just finished running yesterday after 4 days.
...
IPv6 node in Beijing is up and running for the last 3 weeks but not available from outside China. Does this host have a name or what is its Iv6 Address (is the latter 2001:da8:270:2018:f816:3eff:fef3:bdf3)? Is it possible to make it accessible from say SLAC (134.79.0.0/16)
Saqib has joined the team comparing icmp/ping vs TCP for both IPv4 and IPv6, Umar has sent instructionsrun Umar's scripts to compare ping vs TCP. It took about 4 days and Umar has the results.
Saqib has noted that the RTTs from SLAC to China tend to be gretaer than those from SLAC to S. E. ans South Asia.
PingER at SLAC
Umar looking at extending the comparison IPv6 vs IPv4 ping RTTs and TCP vs ICMP/ping RTTs. See Towards Analysis of ICMP vs TCP Ping Latencies.
...