...
UTM
After revision the FRGS proposal was submitted to RMC. It is under review, expect feedback at the end of October.
Saqib is updating the case study from time to time. It just need some formatting. He will send it out in the coming week. This is needed for the workshop.
pinger.fsktm.utm.my can't traceroute.pl or ping_data.pl
...
was not accepted. We need to update it again in order to fulfill the requirements of the grant.
Saqib has updated the case study and is available in Google drive for review. Further it needs some updates from UNIMAS (on Raspberry Pi), UM (on big data) and UUM.
http://pinger.fsksm.utm.my/cgi-bin/traceroute.pl?function=ping work. traceroute problem regarding maximum reachable hops ( i.e. 11 hopes ) is still unresolved. The traceroute looks as below.
Executing exec(traceroute -m 30 -q 3 134.79.197.197 140)
traceroute to 134.79.197.197 (134.79.197.197), 30 hops max, 140 byte packets
1 161.139.68.250 (161.139.68.250) 0.974 ms 1.293 ms 1.524 ms
2 10.110.1.67 (10.110.1.67) 1.135 ms 1.495 ms 1.447 ms
3 161.139.248.254 (161.139.248.254) 3.468 ms 3.360 ms 3.269 ms
4 161.139.245.254 (161.139.245.254) 4.889 ms 4.876 ms 4.968 ms
5 * * *
6 * * *
7 203.80.23.153 (203.80.23.153) 17.659 ms 17.623 ms 17.573 ms
8 203.80.22.137 (203.80.22.137) 16.069 ms 15.098 ms 16.090 ms
9 203.80.23.242 (203.80.23.242) 12.634 ms 12.791 ms 12.831 ms
10 202.179.249.85 (202.179.249.85) 22.090 ms 21.950 ms 22.124 ms
11 jp-pop-sg-v4.bb.tein3.net (202.179.249.78) 88.761 ms 88.710 ms *
12 * * *
13 * * *Saqib has root access to the pinger monitor at UM. However IP address of hop 6 from UM to UNISAM is not pingable. thus he can't look at time series of RTT to see if there are good and bad periods.
NUST
We are unable to ping (or get data from):
...