I've setup a LINUX PC running SUSE 9.2 that has one leg in the Internet and the other on a 192.168.0.0 Intranet (home network). I have my a laptop also running the same OS as the gateway PC, which is connected directly to the 192.168.0.1 NIC via a crossover cable.

I can ping the 192.168.0.1 interface just fine. Could someone tell me please, why can I not ping the 64.x.x.x NIC that's going to my DSL modem and out to the Internet?

When I run tcpdump to show a ping action to my Intranet NIC via the laptop:
15:53:22.862725 IP fignux.site > 192.168.0.40: icmp 64: echo reply seq 2
15:53:23.862664 IP 192.168.0.40 > fignux.site: icmp 64: echo request seq 3
Versus the same way to the other NIC on the gateway going to the Internet:
15:53:42.017753 IP 192.168.0.40 > adsl-64-1xx-xx-1.dsl.pacbell.net: icmp64: echo request seq 2
I will not receive the echo reply sequence.

My routing on the gateway machine:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
64.1xx.xx.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 64.1xx.xx.1 0.0.0.0 UG 0 0 0 eth1
My routing on my laptop client connected via crossover cable to the gateway machine:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

On the SuSEFirewall2 I have:
FW_ROUTE = yes
FW_MASQUERADE=yes

Everything else is set to the default in /etc/sysconfig Editor.
Once I can ping the external card, then I know I can get the clients attached to the
Gateway Firewall box to the Internet.

Thanks in advance,
danfiggolfer

I found out when following this web doc: http://portal.suse.de/sdb/en/2002/07/masq80.html
that I only get a ping response if I ping directly to my host -
and get no response if I do the broadcast ping:


If the network card tests have been successful, proceed now to test if the clients can be reached from the gateway. Use the command ping for this purpose. At least some clients should react to the command ping -c 3 -b 192.168.0.255. The output should be similar to:


WARNING: pinging broadcast address
PING 192.168.0.255 (192.168.0.255) from 192.168.0.1 : 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.774 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=1.19 ms (DUP!)
64 bytes from 192.168.0.3: icmp_seq=1 ttl=255 time=1.30 ms (DUP!)
64 bytes from 192.168.0.4: icmp_seq=1 ttl=64 time=1.57 ms (DUP!)

--- 192.168.0.255 ping statistics ---
2 packets transmitted, 2 received, +3 duplicates, 0% loss, time 1010ms
rtt min/avg/max/mdev = 0.325/1.033/1.573/0.438 ms


In this example, the machines with the IP addresses 192.168.0.1 (gateway) and 192.168.0.2 to 192.168.0.4 (clients) have replied. If you know the IP address of a client, ping it directly to test the connection.