...
The UNIMAS monitor was down over the new year. The problem was that the pinger2.pl file was moved. It is now working, however it looks like an older version, it does not have the individual ping response just the min/avg/max. This will need investigatingis being investigated.
The tool to enable synchronizing Malaysian monitors is completed. It provides the ability to add, edit and delete nodes. However there are still some errors (wild cards) in the pinger.xml file produced. Johari is working on it.
...
Saqib has finished his thesis. He is applying for a Postgraduate Research assistant-ship at UTM where he plans to work on PingER. He is still waiting to hear the result. Update?
Saqib is working with the IT department in UTM to solve the problems of delays in traceroute. They have a new ISP. Now the pinger server is working with single static IP (161.139.68.188) both for intranet and internet. Previous internet IP 161.139.146.158 is removed.
- No load balancing is involved as UTM is working with single ISP.
- Still the problem of the delay in traceroute is not solved. It appears to be due to the DNS lookup delay.
Saqib emailed a list of Potential PingER remote nodes in S. E Asia. They have been added to the all 3 Malaysian PingER monitors' HostLists. He has started a case study of Malaysian hosts seen from Malaysian Monitors.
...
We have made some mods to the evaluation of min_RTT to eliminate bogus values that have impossible values of Directivity. This was to fix problems Saqib ran into with this Malaysia case study.
There is an upcoming meeting in Burkina Faso in November at which Les is invited to give lectures on the Internet, PingER, the digital Divide. In preparation for this we are looking at making a case study on West Africa using the monitoring host in Burkina Faso and have added Beacons in most West African countries.
Old Items
TULIP
The new beta test TULIP site is up and running and is at http://tulip.slac.stanford.edu. To first order (due to the number of landmarks available) it only works in N. America, Europe and Pakistan. Even then it is only accurate to a hundred or so km. It also will not work for targets that do not respond to pings or are connected via geo-stationary satellites. Its main use at the moment maybe to find roughly the location, i.e. region/country/state, a target is in. This is particularly useful for proxies and for routers (the latter are typically mis-found by GeoIPtools to be in the corporate HQ of the owner (e.g. Berkeley for ESnet routers). It would be really valuable if router owners provided DNS LOC records filled out.
...