After you presented all the information I asked for so nicely, I hate to say
it, but ... I can't see the problem. Everything looks right. The NIC both
sends and receives packets. Addresses and routes look okay (assuming there
is a host with IP address 192.168.130.1).
Here are a few more ideas, but they are just fishing, really.
1. What happens if you try to ping the Linux router from one of the Windows
clients?
2. After you try (and fail) to ping a Windows client from the Linux router,
does the Windows host's IP address show up in the Linux host's arp cache
(check /proc/net/arp)?
3. As a last resort -- try running a packet sniffer (tcpdump, sniffit) on
the Linux host and see what is shows happening during a ping (you won't seen
the ping itself, but you should see the arp packets). Also, try a telnet and
see what the sniffer shows.
At 08:28 AM 2/4/00 -0600, Michael Daniels wrote:
[technical details deleted]
a good set of basic networking disgnostics,
>which I will summarize here as:
>
> output of "ifconfig -a"
> output of "route -n"
> actual result of a ping by IP address (include the command line)
> if you are running ipfwadm or ipchains, your ruleset (that is,
> the output of "ipchains -L" or its ipfwadm equivalent)
> physical description of the network
> list of any unusual devices in your Linux host (e.g., an
> unrecognized Winmodem -- this is an IRQ issue)
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
