Bug 131625

Summary:	Yast wireless config does not set up gateway or dns information.
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	John Grange <joker>
Component:	YaST2	Assignee:	Martin Vidner <mvidner>
Status:	RESOLVED DUPLICATE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Critical
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	This should contain the information you need from yast during the configuration of the wireless network. hwinfo --network

Description John Grange 2005-10-31 18:50:52 UTC

When configuring wireless on my HP DV1000 with the ipw2200 through yast, it will connect to the access point, and receive a proper ip address through dhcp, but it will not set the gateway or the dns, i have tried this on 2 different networks, one with WPA-PSK, and one using WEP, both have the same results. Incedentily if i configure the WEP network using the kinternet dialog, it works fine. The wep network is a Netgear 302, and the WPA network is a Linksys WAP54G, both dhcp servers are Windows server 2003. BTW, this has existed since 9.3.

Comment 1 John Grange 2005-10-31 19:30:54 UTC

I discovered, killing dhcpcd and restarting it manualy on the command line it fixes the problem. So i would suspect that something is not being run corectly by the init scripts.

Comment 2 Michael Gross 2005-11-02 15:31:35 UTC

Please attach the yast2-logiles after you tried to set up your wireless card, thanks. Also attach the output of `hwinfo --network'. Thanks.

Comment 3 Stefan Brüns 2005-11-05 00:09:06 UTC

I had this problem too - there was a dhcpcd running on the wired interface, and the second on the wireless refused to set the default gateway and the dns.

This is intended behaviour, see /etc/sysconfig/network/ifcfg.template

Comment 4 John Grange 2005-11-05 07:19:49 UTC

Created attachment 56544 [details]
This should contain the information you need from yast during the configuration of the wireless network.

If this is not what you need please let me know.

Comment 5 John Grange 2005-11-05 07:23:18 UTC

Created attachment 56545 [details]
hwinfo --network

Here is the hwinfo that you needed as well.

Comment 6 John Grange 2005-11-05 07:31:47 UTC

(In reply to comment #3)
> I had this problem too - there was a dhcpcd running on the wired interface, and
> the second on the wireless refused to set the default gateway and the dns.
> 
> This is intended behaviour, see /etc/sysconfig/network/ifcfg.template
> 
Thank you for this tibit of information, this helps partially solve the problem, though i feel as almost that if the network cable is not pluged into to the other card it should not be trying to run dhcpcd on it? perhaps there is a way of doing this?

Comment 7 Michael Gross 2005-11-07 18:13:02 UTC

Martin: Is this something for you?

Comment 8 Martin Vidner 2005-11-08 09:25:58 UTC

Yes, two dhcp clients fighting over the default route is a known problem. We have one solution already in 10.1 Alpha, using ifplugd which only keeps one interface up. (bug 115448)
Also, we will be using NetworkManager on the desktop to that same end.

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