[KLUG Members] no route to local network?

[Mike Williams]

>
> Subject:
> Re: [KLUG Members] no route to local network?
> From:
> Adam Tauno Williams <awilliam at whitemice.org>
>
>
>>> I'm trying to set up an old 500mhz box as a cable modem gateway running 
>>> Suse 9.2.  It gets a DHCP address just fine from the cable modem, but 
>>> doesn't work on the internal LAN.  It seemed to work fine internally 
>>    
>>
>
>So you have two NICs?
>  
>
Sorry.  Yes, it has an old Netgear FA312 (MacPhyter, whatever that 
means) and a newer RTL 8139. 

>  
>
>>> until I gave it a static IP, then it completely chokes.  It can ping 
>>> itself by IP address, but reports "no route to host" when i try to ping 
>>> anything else, even an adjacent IP.  This occurs even when I disable the 
>>> outside NIC.  Anybody have a clue what could cause this?  Here's the 
>>> routing table, which looks fine to me.  What am I missing?
>>> Destination            gateway               mask            
>>> flags        interface
>>> 192.168.41.0      *      255.255.255.0     U   eth0
>>> link-local        *      255.255.0.0           eth0
>>> loopback          *      0.0.0.0           U   eth0
>>> default           *      0.0.0.0           UG  eth0
>>    
>>
>
>Where is a reference to eth1?  The first line looks like it might be the
>route to the LAN, is the LAN hooked into eth0?  You're certain the your
>firewall isn't blocking ICMP?
>  
>
That test was run with the rtl 8139 (which was going to be outside) 
disabled, which is why there's no eth1 showing.  At the time I ran these 
tests, the cable-modem hadn't arrived yet so eth1 couldn't get an IP 
anyway.  I've also tried it with the firewall disabled in YAST, and 
nothing changes.  How would an IPtables problem produce "no route to 
host" messages anyway?

I might just start over and build this thing around SuSE 9.3, since I 
just got a copy of that.