Bug 441868 - test for availability of network by during installation does not work
Summary: test for availability of network by during installation does not work
Status: RESOLVED DUPLICATE of bug 441947
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 4
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-05 15:30 UTC by Freek de Kruijf
Modified: 2008-11-11 09:22 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
saved yast2 log files (1.00 MB, application/x-bzip2)
2008-11-10 23:10 UTC, Freek de Kruijf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Freek de Kruijf 2008-11-05 15:30:51 UTC
During installation of Beta 4, my 2 laptops are wire connected to my network. DHCP is working on that network. So I do not need to configure anything. Still YaST gives the error message that the network is not available. YaST uses a command with curl some parameters and www.suse.com in it. The error message is the www.suse.com can not be resolved.
However pressing <Ctrl><Alt><F2> and giving the command "dig www.suse.com" shows the IP-address of www.suse.com.
Also configuring an IP-address, netmask, gateway and DNS gives the same problem in YaST, but the dig works OK.
I got this on both a 32bit and 64bit laptop.
Comment 1 Freek de Kruijf 2008-11-08 18:27:35 UTC
See also Bug#441947 which is about this problem after installation.
Comment 2 Jan Kupec 2008-11-10 18:10:48 UTC
Please attach also yast logs, see http://en.opensuse.org/Bugs/YaST.

Reducing severity, this is not a critical bug.
Comment 3 Freek de Kruijf 2008-11-10 23:10:51 UTC
Created attachment 251175 [details]
saved yast2 log files

This is the requested tgz file.
Most likely this problem is the same as in Bug#441947 which has to do with the enabling of IPv6 in which case name resolving does not work properly
Comment 4 Jan Kupec 2008-11-11 09:22:18 UTC
Indeed it looks so: name resolution fails, and IPv6 is enabled. Have you tried disabling it just to confirm?

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