Bug 546700

Summary:	Latest update killed internet access
Product:	[openSUSE] openSUSE 11.2	Reporter:	Joseph Short <greenpagan13>
Component:	Network	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	coolo, greenpagan13, holler
Version:	Milestone 8
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	output of requested commands (2 zypper and 1 cat)

Description Joseph Short 2009-10-13 22:39:27 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.1 Firefox/3.5.3

The latest update killed my test computer's (IBM A20) access to the internet.  I can access local networked computers by IP address (192.168.0.3, etc.) but not by any normal DNS'd domain address.  Also, update servers are inaccessible.

I have tried ifup and kinternet configurations, as well as DHCP and full manual settings.  Nothing fixes the problem.

When a fix is published, it will need to be made available separate from the repository system, because the repositories are unavailable to the affected machine.

I have four computers connected to the Qwest DSL modem through a Hawking switch and all four can communicate with all others.  The 11.2M8 laptop is the only one that cannot access anything outside the modem/router.

Reproducible: Always

Steps to Reproduce:
1. Run full-system update available 2009-10-12
2. Reboot computer
3. Test access to Internet using a browser, ping from a konsole, etc.
Actual Results:  
Ping for local (192.168.0.x) machines works.  Ping, website browsing, on-line updates, etc. do not work.

Expected Results:  
I should have full access, including website browsing, system updates, ping, etc. to the internet.

The nature of this problem makes repair impossible through the normal repository update system.  It can only be accomplished either through independent download of a repair rpm, or instructions on any possible manual repair.

Comment 1 Stephan Kulow 2009-10-14 18:25:44 UTC

what's "latest update"? factory? what kernel do you run now?

Comment 2 Joseph Short 2009-10-14 18:41:52 UTC

Latest update: Yast2>Software>Software Management, then update all from the menus telling yast to "Update if newer version available" all packages installed.  I did this from the repositories registered in 11.2M8:

http-download-opensuse.org-e2c5e92a
openSUSE11.2-0
openSUSE11.2-Debug
openSUSE11.2-Non-Oss
openSUSE11.2-Oss
openSUSE11.2-Source

Also, that includes what was available 2009-10-12.

I am running 2.6.31-10-defaulti686

Comment 3 Hans-Peter Holler 2009-10-14 19:37:13 UTC

openSUSE11.2-Oss == Factory ?
@Joseph: what's the output of:
- zypper lr -d ?
- zypper se -s networkmanager ?
- cat /etc/resolv.conf ?
Dupe of https://bugzilla.novell.com/show_bug.cgi?id=546213 ?
Maybe https://bugzilla.novell.com/show_bug.cgi?id=544195 is still not resolved ?

Comment 4 Joseph Short 2009-10-14 20:45:16 UTC

Created attachment 322545 [details]
output of requested commands (2 zypper and 1 cat)

Comment 5 Joseph Short 2009-10-14 21:16:00 UTC

URL for openSUSE 11.2-Oss:
http://download.opensuse.org/distribution/11.2/repo/oss/

I ran the three commands with a redirect to file (combined file attached).  The second one, "zypper se -s networkmanager" produces an error message in konsole:
"Failed to download /repodata/repomd.xml from http://download.opensuse.org/update/11.2"
The command then hangs and must be canceled with ctrl-C.
If I run this without the redirect, I get:
-bash: syntax error near unexpected token 'newline'"

I looked at resolv.conf with kwrite and it only has the "# Generated by NetworkManager" message.  This could be a dupe of bug 546213, but it only showed up after the aforementioned update.

I put the nameserver and search lines from my main computer into this one and got it to work, even after a reboot.

It would be fine to merge this with 564213, it looks like the same problem and will help in troubleshooting and fixing it.

The only concern I have is that 564213 is only posted as "Major" where this whole issue is better considered "Critical."  When the network is rendered unusable, it makes it difficult, if not impossible, for many people less experienced to make it work enough to download a repair update.

Comment 6 Will Stephenson 2009-10-15 11:34:53 UTC

Agreed, marking as dupe.  Please indicate there if you ever hand-edited resolv.conf.

*** This bug has been marked as a duplicate of bug 546213 ***