Bug 114901

Summary:	kinternet doesn't establish wireless connection
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Glenn Holmer <gholmer>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 4
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	output of lsmod \| grep ipw, ifconfig, iwconfig ifcfg-wlan... from /etc/sysconfig/network

Description Glenn Holmer 2005-09-02 02:10:39 UTC

IBM ThinkPad T40 model 2373 19U, Intel ipw2100 wireless.

When I click the kinternet icon, it shows connected, but a ping results in
"Destination Host Unreachable." At one point, I was able to connect by
right-clicking kinternet and manually entering the default key (2 of 4); this
was repeatable, but after a reboot it didn't work. On-board Ethernet was
configured successfully with ifplugd but remained unplugged throughout these tests.

Comment 1 Glenn Holmer 2005-09-02 02:11:42 UTC

Created attachment 48554 [details]
output of lsmod | grep ipw, ifconfig, iwconfig

Comment 2 Glenn Holmer 2005-09-02 02:13:38 UTC

Created attachment 48555 [details]
ifcfg-wlan... from /etc/sysconfig/network

Comment 3 Glenn Holmer 2005-09-03 00:10:19 UTC

Doesn't work with "ifup eth1" either.

Comment 4 Glenn Holmer 2005-09-03 11:24:25 UTC

It's hard to tell what's causing this, but I'm wondering now if SCPM is
involved. After having the machine at work all day on my "work" profile, I
started it at home with the "home" profile.  The interface checkbox in kinternet
was not selected (showed eth1). When I selected it and connected, it worked.

I am not sure what logs to send, as this seems fairly complicated (multiple
interfaces + kinternet + SCPM).

Comment 5 Glenn Holmer 2005-09-10 15:13:03 UTC

Same with RC1.  Configuring on-board Ethernet as ifplugd and on-board wireless
as "started manually" (i.e. with kinternet) works out of the box.  But as soon
as I create profiles and try to switch, it takes a lot of fiddling about to get
it working again.  SCPM seems to be the main culprit.

Comment 6 Joachim Gleissner 2005-09-14 09:10:36 UTC

I guess one reason whhy scpm and kinternet do not work well together is 
because scpm may restart smpppd which breaks the connection from kinternet to 
it. Do you encounter that problem? 
 
Another issue is that smpppd didn't considered association status for 
interface status. But this should have improved in RC2.

Comment 7 Glenn Holmer 2005-09-14 10:34:41 UTC

Yes, I sometimes get a red badge on the kinternet icon after switching 
profiles.  But restarting kinternet doesn't help.

Comment 8 Stephan Kulow 2006-05-07 11:31:56 UTC

please use knetworkmanager in 10.1 - we won't fix kinternet bugs anymore