...
It transpires that pinger6.cs.ubru.ac.th has many IPv6 nodes that are not in NODEDETAILS. We need to identify and work with Charnsak to enter them into NODEDETAILS
We looked in more detail at the first 53 hosts in the <HostList> tag in pinger6.cs.ubru.ac.th’s pinger.xml files (see http://www-iepm.slac.stanford.edu/pinger/pingerworld/pinger6-ubru.txt). Some of the nodes are already in NODEDETAILS. I have added a few hosts with IPv6 addresses to NODEDETAILS.
Many of the nodes have a single name and both an IPv4 and IPv6 address. Since the key of each record in NODEDETAILS is the name and a name can currently only have one IP address, where we already have the name in the database (with an IPv4 address) I have currently left the record as is.
We need to think about how to handle these hosts with both IPv4 and IPv6 addresses. I am leaning towards moving to the future and simply changing the IPv4 addresses to IPv6 addresses. This is the simplest solution. Doing this loses having a historical record of a target with both an IPv4 and IPv6 address. Umar and Les have some scripts that enable comparisons to be made between access to a host via its IPV4 and its IPv6 address without using the PingER data. An alternative would be to also have a pseudo name for such ambiguous hosts, another would be to modify the database schema. Both of the latter two would require changes to the code in several places.
Charnsak is looking at a host in Champasak University, Chan Parsa province in Laos as a potential site for a PingER MA. Charnsak just got approved to make contact with the Champasak University. He expects to set up the MA in the next 4-5 months (say towards end 2018). It also depends on the partner university, and there may be a lot of paperwork.
...