Testing internal MASQ server to MASQ client connectivity

Linux IP Masquerade HOWTO
Prev | Chapter 5. Testing IP Masquerade | Next

# 5.5. Testing internal MASQ server to MASQ client connectivity

- Step Five: Testing internal MASQ server to MASQ client connectivity

  Next from MASQed server, try pinging the IP address of one of the internal MASQ client computers (i.e. ping 192.168.0.10 ). This will verify that TCP/IP is correctly working on both the local server machine and on the MASQ client machine. If this ping doesn't work, make sure that TCP/IP is correctly configured on the MASQed PC as described earlier in Chapter 4 of this HOWTO. Also be sure that the cabling is correct (Ethernet: the NICs connecting the internal MASQ PC and the MASQ server have the "link" light lit up). If the ping does work, the output should look something like the following (hit Control-C to abort the ping):

      ------------------------------------
      masq-server# ping 192.168.0.10
      PING 192.168.0.10 (192.168.0.10): 56 data bytes
      64 bytes from 192.168.0.10: icmp_seq=0 ttl=255 time=0.8 ms
      64 bytes from 192.168.0.10: icmp_seq=1 ttl=255 time=0.4 ms
      64 bytes from 192.168.0.10: icmp_seq=2 ttl=255 time=0.4 ms
      64 bytes from 192.168.0.10: icmp_seq=3 ttl=255 time=0.5 ms
      ^C

      --- 192.168.0.10 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 0.4/0.5/0.8 ms
      ------------------------------------

Prev | Home | Next
Testing internal MASQ server connectivity | Up | Testing External MASQ server Internet connectivity