Changes between Version 53 and Version 54 of NikySandbox/TridentCommTut

Timestamp:

06/08/12 07:27:40 (12 years ago)

Author:

nriga@bbn.com

Comment:

--

NikySandbox/TridentCommTut

@@ -214 +214 @@
 }}}
 
-From R2 you should also be able to ping PC-WashDC. The IP of  PC-WashDC is '''"10.1.1.2"'''.
-{{{
-[inki@r2 ~]$ ping 192.168.44.26 -c 5
-
-
---- 10.1.1.2 ping statistics ---
-5 packets transmitted, 5 received, 0% packet loss, time 4004ms
-rtt min/avg/max/mdev = 0.218/1.504/2.398/1.037 ms
+From R2 you should also be able to ping PC-WashDC. The IP of  PC-WashDC is '''"192.68.44.26"'''.
+{{{
+[uncusr20@r2 ~]$ ping 192.168.44.26 -c 5
+PING 192.168.44.26 (192.168.44.26) 56(84) bytes of data.
+64 bytes from 192.168.44.26: icmp_req=1 ttl=64 time=52.7 ms
+64 bytes from 192.168.44.26: icmp_req=2 ttl=64 time=52.7 ms
+64 bytes from 192.168.44.26: icmp_req=3 ttl=64 time=52.7 ms
+64 bytes from 192.168.44.26: icmp_req=4 ttl=64 time=52.7 ms
+64 bytes from 192.168.44.26: icmp_req=5 ttl=64 time=52.7 ms
+
+--- 192.168.44.26 ping statistics ---
+5 packets transmitted, 5 received, 0% packet loss, time 4007ms
+rtt min/avg/max/mdev = 52.745/52.754/52.764/0.251 ms
+
 }}}
 
 Now let's try and ping the PC-WashDC from source. Login to source the same way you logged in to R2 and run: 
 {{{
-ping 10.1.1.2 -c 5 -w 5
+ping 192.168.44.26 -c 5 -w 5
 }}}
 
 The ping should work. Run a traceroute to see how your packets are routed:
 {{{
-traceroute 10.1.1.2
+traceroute 192.168.44.26
 }}}
 
@@ -246 +252 @@
 }}} 
 
-Now try to ping again from source. The ping should time out
-{{{
-[inki@source ~]$ ping 10.10.4.2 -c 5 -w 5
+Now try to ping again from source. The ping should time out.
+{{{
+[inki@source ~]$ ping 192.168.44.26 -c 5 -w 5
 }}}