...
In addition we cannot gather data from sau.seecs.edu.pk for all of January and have been unable to gather data from pinger.pern.edu.pk since Jan 13. So we recovered 2 and lost 2.
TULIP - Raja
We have sent a reminder email to Yahoo giving them an update on TULIP and how it might be extended to meet their needs. There has been no response. Sent a follow up 1/31/2013They have responded, they appear to be interested. We are trying to interest them in providing landmarks.
Raja uses the options feature of traceroute.pl to reduce the time for the PingER/perfSONAR landmarks to make the pings by a factor of 5. Given this we probably need to review the timeouts. Also we are now using caching and nightlty we populate the caches by a cronjob tracerouting to the PingER targets. THis also help speed things up.
Raja has used TULIP's geolocation to provide a Visual traceroute. It can be accessed via http://www.slac.stanford.edu/comp/net/tulip/. It also shows the route as seen GeoIPTools and other methods. Several features have been added to speed it up: provide caching of router locations vs IP address, populate the cache by tracerouting to PingER nodes each night, the caching, and not bothering with regions where there are insufficient landmarks etc.
...
Raja has also re-written the historical traceroute facility that takes nightly traceroutes and allows one to retrieve and compare them. He then extended it to use the reverse traceroute facility to provide histories for NUST, CERN, ICTP and UNIMAS UM as well as SLAC. See When the UNIMAS and UTM traceroutes work, we can include them. See for example http://www-wanmon.slac.stanford.edu/cgi-wrap/traceroutearchive.cgi?from=maggie1.seecs.edu.pk&to=pinger.cern.ch&date1=2014_01_29&date2=2014_01_30&date3=2014_01_31.
...