On Fri, Aug 27, 2004 at 10:15:10PM -0700, Ray Hauge wrote:

>>Hello All,
>>
>>I've been running Slackware 10.0 (was 9.1 but I upgraded with Swaret)  
>>That went just fine a while back.  I hadn't restarted in a while, so 
>>maybe some package caused the problem (I only use the official servers, 
>>not linuxpackages.net or anything like that).  Just this night I was 
>>installing the new kernel, and when I restarted, my network went down.  
>>When I did ifconfig, it was just blank.  I had to manually bring up the 
>>interface, but even then nothing is really working other than ifconfig.  
>>I can't ping anything anymore. 
>>
>>So, I booted back to my old kernel thinking I missed the support for my 
>>network card, but now my network doesn't work on my working kernel 
>>configuration.  I checked /etc/rc.d and now there's a bunch of .new 
>>files.  There's also an rc.S and rc.M.  rc.inet1 was not executable, and 
>>that was the file that was set to bring up the network on the boot.  I 
>>made that executable, and when I boot I get eth0 and loopback, but I 
>>still can't ping anywhere. I checked dmesg and there didn't seem to be 
>>any weird errors other than eth0 is running in permiscuous mode now.  
>>Another odd thing that happens now is that ldconfig is run on the boot.  
>>When I ran make modules_install, did that screw around with my rc files 
>>like this?
>>
>>Thanks everyone!
>>
>>Ray Hauge
>>    
>>
>Wes Bateman wrote:
>Ray:
>
>Check your routing tables:
>
>route -n
>
>See if you have a default route (starts with 0.0.0.0 in the leftmost
>column.
>
>From your description it sounds like your eth0 is now up (not sure about
>why it's in promisc mode...you have snort or such running?).  Can you
>ping the local subnet, just not outside on the internet?  That would be
>default route.
>
>I'm not familiar with how things are done in Slackware, but compiling
>and installing a kernel and modules wouldn't be related to your rc
>scripts I'm sure.  Must have been some other package(s) that were
>upgraded?
>
>Wes
>
>  
>

I checked the route this morning and there were two set for eth0.  Both 
of them had a default gateway of 0.0.0.0  I removed everything and added 
them back.  I couldn't set the gateway though, I had to instead use

route add default gw <gateway address>

Now I can at least attempt to ping places.  Before I couldn't ping 
anything.  It was saying "Connect: invalid argument"  Now it all the 
pings just fail, even to 127.0.0.1.

Thanks again,
Ray
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change  you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss