Re: patched, compiled and no network

["Sancho2k.net Lists" <lists@sancho2k.net>]

tim smith wrote:

>>Could you have somehow (for any reason) lost routes for the directly
>>connected network? What does 'route -n show' give?
>>
>>DS
>>
> 
> the default route is still the same ( as per /etc/mygate), i did run "route
> show" but gave up on it since it couldn't contact the default route and sat
> there forever. 

It probably timed out because it couldn't reverse lookup the addresses 
in the routing table. Feed it the -n switch. Inability to reach the DG 
won't cause it to time out.

> however the routing table shouldn't even come into it becuase
> both machines are on the same subnet ( 192.168.0.0 ) and they should find
> each other via arp anyway right ?

Where they're on the same subnet, I suppose so. But my inital question 
is relevant; if you're machine doesn't have a route for the local subnet 
in its routing table, then you can't contact local machines either (i.e 
not only will you not be able to ping past the DG, but you won't be able 
to even reach the DG.

==========================================
# route -n show
Routing tables:

Internet:
Destination      Gateway            Flags
default          10.0.0.1           UG
10.0.0.0         link#1             U
10.0.0.1         0:5:5e:9f:fc:93    UH
[...]
==========================================

As above, the host that I am viewing the routes from is ipaddr 10.0.0.2. 
Since it has a route (2nd one listed) to the 10.0.0.0 network, it knows 
that any communication with hosts on the 10.0.0.0 network needs be be 
sent out link#1.  Without that route in there, I couldn't even talk to 
hosts on the local subnet (GW included.)

See if your routing table looks correct. If it does, I'd lean towards 
faulty NIC or cable (you can test either/both of them.)

DS