Page History

...

Saqib'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. Anjum and Saqib will discuss where best to fit Saqib's proposal and Anjum will help edit the proposal.

Saqib reports there is a change in traceroute from SLAC to UNIMAS in this month. Previously, it goes via TEIN3. Further, it did not touch the MYREN network.

The ping server at http://

...

pinger.

...

fsktm.

...

um.edu.my/cgi-

...

bin/traceroute.pl?target=www.

...

slac.stanford.

...

edu&function=

...

...

ping gives ping server busy at the moment. Please try again later. Saqib may want to look at that. Maybe it is being hit with a lot of requests simultaneously. If they are coming from SLAC we may want to look at.

Saqib also reports there is a change in traceroute from SLAC to UNIMAS in this month. Previously, it goes via TEIN3. Further, it did not touch the MYREN network.

Les did a binary search (using http://www-wanmon.slac.stanford.edu/cgi-wrap/traceroutearchive.cgi?from=www-wanmon.slac.stanford.edu&to=pinger.unimas.my&date1=2014_06_17&date2=2014_06_18&date3=2014_06_19) it appears the change happened on Wed 2014_06_18 (there is actually no trace route measured that day) . I have no idea of the significance, Saqib may need to check with your contacts in Malaysia.  Traceroute from UM to SLAC:

traceroute to 134.79.197.200 (134.79.197.200), 30 hops max, 140 byte packets

 1  ip254.fsktm.um.edu.my (202.185.107.254)  0.762 ms  0.668 ms  0.588 ms

 2  10.94.253.249 (10.94.253.249)  1.147 ms  1.080 ms  0.963 ms

 3  172.20.2.254 (172.20.2.254)  0.723 ms  0.602 ms  0.531 ms

 4  161.142.24.129 (161.142.24.129)  1.263 ms  1.081 ms  1.009 ms

 5  161.142.5.249 (161.142.5.249)  4.149 ms  4.222 ms  4.146 ms

 6  ix-10-3-4-2011.tcore1.HK2-Hong-Kong.as6453.net (180.87.112.97)  36.242 ms  36.169 ms  36.461 ms

 7  if-3-2.tcore1.TV2-Tokyo.as6453.net (180.87.112.6)  191.692 ms  190.497 ms  204.063 ms

 8  if-9-2.tcore2.PDI-Palo-Alto.as6453.net (180.87.180.17)  202.157 ms  201.441 ms  201.804 ms

 9  if-5-2.tcore2.SQN-San-Jose.as6453.net (64.86.21.1)  189.191 ms  189.030 ms  190.501 ms

10  eqx-sj-tata.es.net (198.129.44.53)  198.634 ms  198.559 ms  198.415 ms

11  * * *

12  slacmr2-ip-b-sunncr5.es.net (134.55.40.14)  196.457 ms  197.480 ms  196.380 ms

13  rtr-border1-p2p-slac-mr2.slac.stanford.edu (192.68.191.246)  198.314 ms  195.649 ms  197.740 ms

14  * * *

The route from SLAC to UNIMAS before (20140617) is:

1 134.79.197.131 (134.79.197.131) [AS3671] 0.435 ms

2 rtr-core2-p2p-serv01-02.slac.stanford.edu (134.79.254.61) [AS3671] 0.344 ms

3 rtr-border1-p2p-core1.slac.stanford.edu (134.79.252.133) [AS3671] 0.406 ms

4 slac-mr2-p2p-rtr-border1.slac.stanford.edu (192.68.191.245) [AS3671/AS38621] 30.412 ms

5 *

6 transpac-1-is-jmb-780.lsanca.pacificwave.net (207.231.246.136) [*] 8.672 ms

7 tokyo-losa-tp2.transpac.org (192.203.116.146) [*] 124.037 ms

8 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) [AS7660] 125.611 ms

9 sg-xe-01-v4.bb.tein3.net (202.179.249.77) [AS24489] 192.946 ms

10 my-pr-v4.bb.tein3.net (202.179.249.70) [AS24489] 200.499 ms

11 (203.80.23.61) [AS24514/AS4788] 242.756 ms

12 (203.80.22.158) [AS24514/AS4788] 243.353 ms

13 (203.80.23.94) [AS24514/AS4788] 241.138 ms

14 (203.80.18.182) [AS24514/AS4788] 241.086 ms

The route after (20140618) is 

1 rtr-servcore1-serv01-webserv.slac.stanford.edu (134.79.197.130) [AS3671] 0.423 ms

2 rtr-core2-p2p-serv01-01.slac.stanford.edu (134.79.254.65) [AS3671] 0.293 ms

3 rtr-border1-p2p-core2.slac.stanford.edu (134.79.252.137) [AS3671] 0.443 ms

4 slac-mr2-p2p-rtr-border1.slac.stanford.edu (192.68.191.245) [AS3671/AS38621] 0.232 ms

5 *

6 eqxsjrt1-ip-a-sunncr5.es.net (134.55.38.146) [AS293] 24.495 ms

7 sj-igw01.tm.net.my (206.223.116.120) [AS4637] 2.668 ms

8 *

9 58.26.240.62 (58.26.240.62) [AS4788] 215.915 ms

However, the traceroute from SLAC to UTM and UM remains the same.

BTW you can examine the geography of the above routes by cutting and pasting them into http://www-wanmon.slac.stanford.edu/cgi-wrap/reflector.cgi?function=vtrace

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. 

...