At least you conclude by asking the right question. Generally speaking,
summaries of command results aren't as helpful as the actual results ...
suppose you're wrong in interpreting something ... how would we be able to
spot it from summaries?
So ... what we need to see is:
1. The actual output of "ifconfig -a". (BTW, if the NIC is on IRQ 3, it
probably is conflicting with a serial port, even if /proc/interrupts doesn't
*show* the conflict.) Run this twice, both before and after you try a ping
(you want to see if the TX and RX counts change.)
2. The actual output of "route -n". (This is the same as "netstat -n", BTW.)
Routing problems are common causes of connectivity problems, and you say you
don't understand the output (BTW, did you read the man page?).
3. Information on the physical seup of your LAN. I'll guess it uses UTP
wiring through a hub, but correct me if I am wrong.
4. One specific note. You wrote:
>Whenever I try to ping I get the message Destination Host Unreachable. I
>think it is sending packets out because the two lights on my hub (one for
>linux box and one for pinged box) both flash.
This sounds like the Linux host is sending out an arp request and the host
being pinged is receiving it, but not acknowledging it. (Non-pinged hosts
should be receiving this too -- arp requests are broadcast -- so you can see
what's up by comparing the pinged host with a non-pinged host on the same
LAN.) You may have a problem on the destination host, not the Linux host.
5. See if you can ping the following from the Linux host
localhost
the Linux host's own IP address
6. If you can remember the "other things", tell us about them. But that is
not as important as including 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)
At 10:46 AM 2/3/00 -0600, Michael Daniels wrote:
>Hello All,
> I am experiencing a network problem on my home LAN. I have asked some
>friends that use Linux, but they were unable to fix my problem. I figure
>that with all of the experts on this list I should get the help I need. I
>am running a RedHat 6.1 system with a 3Com 3C509B-TPO NIC. I have tried
>many different things, but still get the same error message. Here is a list
>of things that I have tried.
>1. Verified there were no IRQ conflicts in /proc/interrupts
>2. In ifconfig -a the eth0 device seems to be correctly setup
>3. Ran netstat -n but am not sure what to look for.
>4. Restarted the network using the /etc/rc.d/init.d/network restart command
>and the eth0 device initializes [OK]
>5. Other things that I cannot remember
>
>Whenever I try to ping I get the message Destination Host Unreachable. I
>think it is sending packets out because the two lights on my hub (one for
>linux box and one for pinged box) both flash.
>
>What information do you need from me to help me tackle this problem?
------------------------------------"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
