...
After revision the FRGS proposal was submitted to RMC. It was not accepted. We need to update it again in order to fulfill the requirements of the grant. Is there an update?
Saqib has updated the case study and is available in Google drive as a "Shared-PingER" document for review at https://drive.google.com/folderview?id=0B-NEKleLll79ZFNmUnhiVGJ0Nmc&usp=sharing_eid (thanks to Bebo who will notify all of how to access). Further it needs some updates from UNIMAS (on Raspberry Pi), UM (on big data) and UUM.
The traceroute problem regarding maximum reachable hops ( i.e. 11 hopes ) may be since the Unix/Linux/OSX traceroute uses UDP to send the requests. The first request is sent to a particular port (33434), with a ttl to tell it how many hops to go to. The ttl starts at 1 is incremented as it tries the next hop, also the port is incremented (up to 33465). It looks like the first few UDP ports are enabled and then they are blocked. The Windows traceroute uses ICMP to send the probes so does not see the problem..
NUST
We are unable to resolve the name of the hosts: pinger.uet.edu.pk
...