...
No updates regarding traceroute problem at UTM. However, Saqib thinks the problem is still in CICT firewall or router as tcp traceroute command works fine from UTM.
Les has reviewed the Malaysian Case Study and sent suggestions. Saqib will incorporate. Saqib met with MYREN who have made many topology changes. Saqib will also incoporate these into the Malaysian case study.
Saqib is in discussions with his PhD superviser to get the requirements for a PingER proposal and to see where 's proposal is almost ready however we do not see somewhere (funding agency) to submit it to. The next round of the FRGS may be the next opportunity
UUM
Regarding the monitoring host in UUM, Adib has assigned one student to prepare the configuration/installation plan including how to secure their host from attack. He has a public IP address. He needs to the DNS registration by Sunday 25th May or Monday. He is in the last stage of working with the Computer Center. Adib requested Johari to share the UNIMAS setting so it is easier for the student to follow. No update 6/5/2014, 6/25/2014.
...
- duhs.seecs.edu.pk, Kashif recommends to drop they do not seem interested. This has been done.
- pinger.kohat.edu.pk, System issue, we are sending new motherboard in this week.
- pingerkhi-uok.pern.edu.pk, SFP Connector Problem, We are sending new one in this week.
- sau.seecs.edu.pk, System Issue, New system is ready and will send in this week.
- uaf.seecs.edu.pk, Drop (IP blocked frequently so currently not good as a PingER). Anjum recommended that if we do not have another host in faislabad then this host may be very important. Since Kashif is from Faisalabad, Anjum suggested we try a bit more if there is no other host. Looking at the map (see http://www-wanmon.slac.stanford.edu/wan-mon/viper/pinger-coverage-gmap.html), it appears PK.PERNFSBDPOP.EDU.N1 is nearby. Thus UAF has been dropped.
Raja
Raja has improved improving the GUI for TULIP. In particular visualizing the intersection region (showing both the minimum and maximal circles), showing landmarks, adding Google analytics. Raja has added undns (a tool for guessing the location from the router name) to TULIP and also to VTrace. It is not very successful, its heuristics are outdated (last update 2005)added an optional feature to exclude water areas from the acceptable area. this reduces the error (proportional to area), but sometimes leads to a less accurate centroid. Currently it is only available for N. America. He will update the documentation with examples. The number of working, usable landmarks is now up to 340.
PingER at SLAC
Les requested an update from Yahoo about TULIP's geolocation. They answered "We are very much interested in getting IP triangulation at internet scale, we will have internal sync-up on how we can leverage this initiative if there is rate limit and get back. Regarding opening up yahoo sites for deploying ping server requires some more time to discuss this with relevant stake holders with in yahoo." No word, sent a reminder 5/19/2014. No response 6/4/2014, 6/25/2014. Sent an update on the applicability to visual traceroute..
Les sent email to Google as follows: "I would like to bring to your attention that we have developed a geolocation tool using delay based (using RTTs from known ping server landmarks) distance estimates to triangulate the location of an IP host target. The tool is accessible at: http://www-wanmon.slac.stanford.edu/cgi-wrap/reflex.cgi. We have identified that the accuracy of the geolocation is directly related to the landmark density (e.g. # of landmarks/ million sq km). The higher the density the smaller the error and the fall off is exponential. We currently have over 1000 registered landmarks, of which at any given time ~300 are working. The tool not only finds the location of the target, it also gives an estimated error. To the best of our knowledge it is the only freely available delay based measurement geolocation service publicly available today. A drawback (compared to database methods such as those based on GeoMind) is the time taken to make the measurements. We have worked on this from many directions including parallelization of the ping requests, caching, tiering to get the rough location (i.e. region of the world) then zooming in using all landmarks in the region. We are putting together a publication on this." Les sent an update to his contact at Google 6/23/2014, stressing the applicability to traceroute visualization.
...