216 | | From R2 you should also be able to ping PC-WashDC. The IP of PC-WashDC is '''"10.1.1.2"'''. |
217 | | {{{ |
218 | | [inki@r2 ~]$ ping 192.168.44.26 -c 5 |
219 | | |
220 | | |
221 | | --- 10.1.1.2 ping statistics --- |
222 | | 5 packets transmitted, 5 received, 0% packet loss, time 4004ms |
223 | | rtt min/avg/max/mdev = 0.218/1.504/2.398/1.037 ms |
| 216 | From R2 you should also be able to ping PC-WashDC. The IP of PC-WashDC is '''"192.68.44.26"'''. |
| 217 | {{{ |
| 218 | [uncusr20@r2 ~]$ ping 192.168.44.26 -c 5 |
| 219 | PING 192.168.44.26 (192.168.44.26) 56(84) bytes of data. |
| 220 | 64 bytes from 192.168.44.26: icmp_req=1 ttl=64 time=52.7 ms |
| 221 | 64 bytes from 192.168.44.26: icmp_req=2 ttl=64 time=52.7 ms |
| 222 | 64 bytes from 192.168.44.26: icmp_req=3 ttl=64 time=52.7 ms |
| 223 | 64 bytes from 192.168.44.26: icmp_req=4 ttl=64 time=52.7 ms |
| 224 | 64 bytes from 192.168.44.26: icmp_req=5 ttl=64 time=52.7 ms |
| 225 | |
| 226 | --- 192.168.44.26 ping statistics --- |
| 227 | 5 packets transmitted, 5 received, 0% packet loss, time 4007ms |
| 228 | rtt min/avg/max/mdev = 52.745/52.754/52.764/0.251 ms |
| 229 | |