Step Two: Testing internal MASQ client to MASQ server
connectivity
Next, from the same internal MASQed computer, try pinging the the IP address of
the Linux MASQ server's INTERNAL interface (i.e. ping
192.168.0.1 ). This will verify that TCP/IP is correctly working
on both the local and Linux MASQ 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 Server as described
by the various Network HOWTOs (URLs can be found in the requirements section
for your
2.4.x kernel in Section 2.6,
2.2.x kernel in Section 2.7, or
2.0.x kernel in Section 2.8). 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). The output should
look something like the following (hit Control-C to abort the ping):
------------------------------------
masq-client# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.8 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.4 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=0.4 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=0.5 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.4/0.5/0.8 ms
------------------------------------