Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I upgraded my working install of 10.1 to 10.2 via slapt-get. After a reboot I can no longer get outside my network. I can ping local addresses but not anything on the internet. ifconfig shows eth0 as being up and with the static IP address it is supposed to. /etc/networks, etc/resolv.conf and /etc/rc.d/rc.inet1.conf all look good.
Any thoughts on this one? I've got 2 systems that I upgraded the same way and both are exhibiting the same behavior.
I had this exact same thing happen. I was able to access all the other machines on my network by name, but couldn't get internet. I ran netconfig at least once after I upgraded, and I know I had to specify an external DNS server before I could get Internet access (my router's IP address wasn't enough...) But to be honest, I'm not 100% sure I know exactly what gave me access again.
I've done the same thing. The DNS name servers I have listed are the external DNS servers for my account. I may try changing them to the router's address and seeing if I can get it to assign the DNS to the system like it does for DHCP clients (a shot in the dark, but why not).
Will post if/when I get this figured out. I've got 1 testing server down and a desktop because I can't figure this out. Any other ideas are certainly welcome.
Ahh... Thanks for that, I hate not knowing how I REALLY solved a problem (I do recall seeing my default gateway was set to 0.0.0.0 as well) So now the question becomes, is there something in the Slackware 10.2 install/upgrade process that's causing the Gateway to be reset to 0.0.0.0? I've seen at least 2 other threads in this forum where this exact same thing happened, seems to be a trend...
I tend to wonder if that's not the case. I wonder if they are using slapt-get to do the upgrade. I know 2 of my machines using slapt-get have done this. A Slapt-get issue or a 10.2 upgrade issue. I still have a 10.1 machine. I should compare the 2 host files, gateway setups, etc. and see what the differences are
Distribution: Slackware / Debian / *Ubuntu / Opensuse / Solaris uname: Brian Cooney
its handy to keep a list of 2-3 ip addresses on the internet on hand so when somthing like this happens, you can tell if its a routing problem, or a dns problem by pinging by a hard ip address.
if you can ping by address but not by name, its a dns problem. if you cant ping by address, its a routing problem, a problem with your card, a network cable came out, or somthing else internal and stupid.
I had the same problem. After upgradeing the base(a) packages except "etc" package with slackpkg . I think I fixed it with manual editing rc.inet1.conf(I'm not sure, I've made a few modifications and changed to realtek LAN card) . The "netconfig" did not work for me. The gateway adress is the problem.