M8 to RC1 - now no network apps but network is connected

I just did the upgrade from Milestone 8 to RC1. After reboot, ALL applications requiring internet access cannot access the network. This includes Firefox, Thunderbird, OpenSUSE software update, Liferea, etc.

Both my wireline (eth0) and wireless connections are both active according to the system. However, I can’t ping an outside address. I can ping the 192. addresses. So, no DNS lookup and won’t work with IP addresses.

I am running Gnome as the desktop.

Does anyone know what scripts are modified or retired by this upgrade and how I can get my network access back?

Sounds like the same problem in this thread:

Resolving URLs problem since upgrade to 11.2 RC1 - openSUSE Forums

PROBLEM SOLVED

Yes, I read this post before starting my own. However, this person had Skype working(??).

In addition, I DID delete the /etc/resolv.conf file. and rebooted to make sure everything got restarted properly. This change did nothing.

By the way, I looked in the original resolv.conf file and the resolv.conf.netconfig and both of them were empty files!? Curious.

So, I did the first step mentioned which was to run:
sudo /sbin/netconfig update -f

THAT DID IT!! I NOW HAVE WORKING NETWORK CONNECTIONS.

How did this get changed from the original configuration in M8??

Anyway thank you to all for the quick solution.

Funny. All I did was delete /etc/resolv.conf and reboot and my network started working again. This was on my MacBook with RC1 installed as a guest in VirtualBox. On my Linux box, I didn’t have this problem at all.

No network apps here also. In addition terminal went down so no zypper. Helpless ! Will stay with m8 until rc2. I liked what I had working though.

I had this same problem when upgrading M8 to RC1. I downloaded and burnt the KDE4 live CD. This worked with full internet connection, despite warning me that I had not enough memory. (I have an old, 2003, Athlon 2200 with 512MB ram and on-board graphics). I then selected install which went fine (with another low memory warning). The installed system works well as far as I have tested. There has been a problem loading MS fonts which failed but otherwise all seems good.

the

sudo /sbin/netconfig update -f

command, solved my problem, thanks again ! :wink:
But, i dont understand one thing, why we had to do this… ? :sarcastic:

I feel the same way. As I posted, I solved my problem using the netconfig command but I would still like to know what went wrong in the upgrade and what got overwritten?

It would be nice to learn from these experiences and build up some knowledge of what can go wrong and where to look.

On 10/17/2009 12:46 PM, mglowy wrote:
>
> I feel the same way. As I posted, I solved my problem using the
> netconfig command but I would still like to know what went wrong in the
> upgrade and what got overwritten?
>
> It would be nice to learn from these experiences and build up some
> knowledge of what can go wrong and where to look.

If you have the resolv.conf problem, then the network is working, but
DNS is not. This situation is easy to test with a three-step process.

(1) Ping your router/gateway.

(2) If that works, ping 216.83.154.106

(3) If that works, ping www.samba.org

If 1 and 2 work, but not 3, then the problem is with DNS.

If 1 works, but not 2 and 3, then your router cannot get to the Internet.

If #1 fails, then check for a problem with routing.

When I was trying to get things going I tried all the steps: 1, 2, & 3.

My system would only do step 1. It failed on step 2 and 3.

What does this mean? How did the upgrade from M8 to RC1 affect the router link? My other computer continued to work, so I assume the router was not affected but the RC1 was not getting an assigned address? Does this make sense and if so what causes this to happen? Where in Suse is this “request mechanism” controlled? Or is there a totally different issue since running the netconfig command seems to resolve the internal error?

On 10/18/2009 09:46 AM, mglowy wrote:
>
> When I was trying to get things going I tried all the steps: 1, 2, & 3.
>
>
> My system would only do step 1. It failed on step 2 and 3.
>
> What does this mean? How did the upgrade from M8 to RC1 affect the
> router link? My other computer continued to work, so I assume the
> router was not affected but the RC1 was not getting an assigned address?
> Does this make sense and if so what causes this to happen? Where in
> Suse is this “request mechanism” controlled? Or is there a totally
> different issue since running the netconfig command seems to resolve the
> internal error?

I assume that you mean an IP number as the “assigned address”. If step
1 worked, then you have an IP number, and a default route established.
Please post the output from the commands below:

/sbin/route -n
/sbin/ifconfig eth0

mglowy wrote:

>
> I just did the upgrade from Milestone 8 to RC1. After reboot, ALL
> applications requiring internet access cannot access the network. This
> includes Firefox, Thunderbird, OpenSUSE software update, Liferea, etc.
>
> Both my wireline (eth0) and wireless connections are both active
> according to the system. However, I can’t ping an outside address. I
> can ping the 192. addresses. So, no DNS lookup and won’t work with IP
> addresses.
>
> I am running Gnome as the desktop.
>
> Does anyone know what scripts are modified or retired by this upgrade
> and how I can get my network access back?
>
>
Just to let you no, my 11.2 RC1 I installed a couple of hours ago get to
internet. All four browsers I have work (Konqueror [4.3.2], Opera
[Version 10.00, Build 4585, Qt library 4.5.3, Java Java Runtime
Environment installed], Google-Chrome and FireFox [3.5.3]. I use the KDE
desktop so I cannot help with Gnome