[
Next-in-Thread ]
[
Next Message ]
Network unreachable == routing problem
-
Forum:
PCMCIA Network Adapter Issues
Re:
Question:
Destination Host Unreachable (David Walden)
Date: 1999, Nov 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>
|
Your "netstat -r" may show a route to your gateway, but there must still be a problem with your routing info. "Network unreachable" always means a routing problem. Perhaps your gateway address isn't on the same subnet as your own IP address. If you can't sort it out, post the actual "netstat -rn" output.
-- Dave
|
[
Next-in-Thread ]
[
Next Message ]
Messages
Inline:
[
0 ]
[
1 ]
-
Re:
Network unreachable == routing problem (David Hinds)
Date: 1999, Nov 17
From: David Walden Walden
|
Here is my routing table. To me everything works fine.
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
195.175.107.118 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
195.175.107.0 0.0.0.0 255.255.255.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 195.175.107.65 0.0.0.0 UG 0 0 0 eth0
|
|
-
Re:
RE: Network unreachable == routing problem (David Walden)
Date: 2000, Jan 05
From: John Jervis JohnJ
|
I don't agree that "network unreachable" is *always* due to routing problems, though this is the common reason. My Olicom GoCard multifunction eth/modem card gives this, but /var/log/messages shows the following when pinging an external address (i.e. not itself):
<date> <node> kernel: eth0: timeout waiting for Tx RDC.
<date> <node> kernel: eth0: pcnet_reset_8390() did not complete
and repeats this ad infinitum.
Is this why the Olicom card is no longer in the latest list of supported cards?
|
|
Network unreachable == routing problem
[
Add Message ]
to: "Network unreachable == routing problem"
[
Members ]
[
Subscribe ]
[
Admin Mode ]
[
Show Frames ]
[
Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]