Testing internal MASQ client PC connectivity

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

# 5.2. Testing internal MASQ client PC connectivity

- Step Two: Testing internal MASQ client PC connectivity

  From an internal MASQed computer, try pinging its local IP address (i.e. ping 192.168.0.10 ). This will verify that TCP/IP is correctly working on the local machine. Almost ALL modern operating systems have built-in support for the "ping" command. 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. The output should look something like the following (hit Control-C to abort the ping):

      ------------------------------------
      masq-client# 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
Loading up the rc.firewall ruleset | Up | Testing internal MASQ client to MASQ server connectivity