NAT-MCH Users Manual Version 1.16
NAT-MCH Users Manual Version 1.16
NAT-MCH Users Manual Version 1.16
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>NAT</strong>-<strong>MCH</strong> – <strong>Users</strong> <strong>Manual</strong><br />
root@natcg2# ping 132.147.160.47<br />
PING 132.147.160.47 (132.147.160.47) 56(84) bytes of data.<br />
64 bytes from 132.147.160.47: icmp_seq=1 ttl=64 time=0.232 ms<br />
64 bytes from 132.147.160.47: icmp_seq=2 ttl=64 time=0.193 ms<br />
64 bytes from 132.147.160.47: icmp_seq=3 ttl=64 time=0.195 ms<br />
--- 132.147.160.47 ping statistics ---<br />
� packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 0.193/0.206/0.232/0.024 ms<br />
Appendix B 6 Test3: ping between control host and <strong>MCH</strong>:<br />
This test shows whether the control host can communicate with the <strong>MCH</strong> and vice versa<br />
using the ‘ping’ tool.<br />
Ping the <strong>MCH</strong> from the control host:<br />
control:~$ ping 192.168.0.134<br />
PING 192.168.0.134 (192.168.0.134) 56(84) bytes of data.<br />
64 bytes from 192.168.0.134: icmp_seq=1 ttl=254 time=4.73 ms<br />
64 bytes from 192.168.0.134: icmp_seq=2 ttl=254 time=0.382 ms<br />
64 bytes from 192.168.0.134: icmp_seq=3 ttl=254 time=0.342 ms<br />
64 bytes from 192.168.0.134: icmp_seq=4 ttl=254 time=0.346 ms<br />
--- 192.168.0.134 ping statistics ---<br />
4 packets transmitted, 4 received, 0% packet loss, time 3000ms<br />
rtt min/avg/max/mdev = 0.342/1.450/4.732/1.895 ms<br />
and a network sniffer dump gives:<br />
No. Time Source Destination Prot Info<br />
25 5.616704 132.147.160.47 192.168.0.134 ICMP Echo (ping) request<br />
26 5.616755 192.168.0.70 192.168.0.134 ICMP Echo (ping) request<br />
27 5.616939 192.168.0.134 192.168.0.70 ICMP Echo (ping) reply<br />
28 5.616953 192.168.0.134 132.147.160.47 ICMP Echo (ping) reply<br />
Note that a ping request issued from the control host is received by the gateway and then<br />
delivered to <strong>MCH</strong>, the ping response is first sent to the gateway and then delivered to the<br />
control host. In both cases network address translation is performed by the gateway.<br />
Ping the the control host from the <strong>MCH</strong>:<br />
nat> ping 132.147.160.47<br />
192.168.0.134->132.147.160.47 Echo Request (56 bytes) seq 0<br />
132.147.160.47->192.168.0.134 Echo Reply (56 bytes) seq 0 ttl 63<br />
192.168.0.134->132.147.160.47 Echo Request (56 bytes) seq 1<br />
132.147.160.47->192.168.0.134 Echo Reply (56 bytes) seq 1 ttl 63<br />
192.168.0.134->132.147.160.47 Echo Request (56 bytes) seq 2<br />
132.147.160.47->192.168.0.134 Echo Reply (56 bytes) seq 2 ttl 63<br />
<strong>Version</strong> <strong>1.16</strong> © N.A.T. GmbH 85
Change language