10.2 upgrade; lan works, wan doesn't

Nd4Spd · 10-02-2005, 04:14 PM

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.

Thanks.

pnellesen · 10-02-2005, 09:49 PM

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.

Next time I upgrade, I'm keeping notes

Good Luck!

Nd4Spd · 10-03-2005, 07:35 AM

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.

Thanks.

pnellesen · 10-03-2005, 09:11 AM

This might help a little: http://wiki.linuxquestions.org/wiki/...roubleshooting

They do mention checking the /etc/HOSTNAME file - I THINK I had to modify that one, but that might be due to something I myself changed during my attempts at getting reconnected...

cyanidebm · 10-03-2005, 12:15 PM

Greetings,

How does route look? Is there a gateway route for the interface?

Check with:

Code:

route -n

You should a gw route to 192.168.x.1 or whatever gateway is, if there isnt add it with:

Code:

route add default gw 192.168.x.1

With no gateway will be unable to reach outside network.

Good Luck,

-cyanidebm

Nd4Spd · 10-04-2005, 07:02 AM

Haha! You're a genius! Many thanks. That did it! The

Code:

route -n

command gave me a destination of 192.168.1.0 and a gateway of 0.0.0.0. I ran the command

Code:

route add default gw 192.168.1.1.

Now, running route -n gives me

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.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         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

Now it's working A-OK.
Thanks again!

pnellesen · 10-04-2005, 08:55 AM

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...

Nd4Spd · 10-04-2005, 09:10 AM

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

pnellesen · 10-04-2005, 09:18 AM

Quote:

Originally posted by Nd4Spd
I wonder if they are using slapt-get to do the upgrade. I know 2 of my machines using slapt-get have done this.

Just as a point of interest, In my case, I use the procedure outlined in "UPGRADE.TXT" when I upgrade... When I upgraded from 10.0 to 10.1, this didn't happen.

hunterfighter · 10-09-2005, 12:40 AM

Now my turn

I had my WAN Server IP but I does not have Client IP
How?

Nd4Spd · 10-10-2005, 11:00 AM

I'm sorry, I'm not quite sure i understand your question. Are you saying you have an IP address for you WAN from your ISP but you're unable to assign an IP address on your LAN to your machine?

run:

Code:

 netconfig

on the CL and it will step through the process.

Kahless · 10-20-2005, 12:35 AM

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.

hunterfighter · 10-20-2005, 03:13 AM

I think should be my NIC or Router problem

jaos · 10-20-2005, 09:33 AM

Quote:

Originally posted by pnellesen
Just as a point of interest, In my case, I use the procedure outlined in "UPGRADE.TXT" when I upgrade... When I upgraded from 10.0 to 10.1, this didn't happen.

Users upgrading with slapt-get should also observe the steps outlined in UPGRADE.TXT especially when it comes to changes in the init scripts.

planoru · 10-21-2005, 01:47 AM

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.