[Bug 395477] New: knetworkmanager is too slow and fails often

newer
[Bug 382010] New: DHCP client NOT...

bugzilla_noreply＠novell.com

29 May 2008 29 May '08

15:33

https://bugzilla.novell.com/show_bug.cgi?id=395477 Summary: knetworkmanager is too slow and fails often Product: openSUSE 10.3 Version: Final Platform: i386 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: peebhat@gmail.com QAContact: qa@suse.de Found By: Other (My experience of this application has been with broadcom wireless chip.I cannot say this is not due to the bugs in the driver) In similar circumstances,while Gnome network applet can connect to wireless network,knetworkmanager fails more and when successfully connects,takes too long. Any signal strength below 65%- 70% is not good enough to connect.With the same signal strength,Gnome network applet connects.(Tested with Ubuntu)Windows XP connects without a complaint. While knetworkmanager takes longer than other such applications to connect,even when fail is apparent,knetworkmanager takes longer time to hangup. As my most comparisons are with Gnome network applet,I believe this is not a driver issue,but more a bug in the application. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

1 Jun 1 Jun

07:48

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |hschaa@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

2 Jun 2 Jun

19:51

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c1 JP Rosevear changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |peebhat@gmail.com --- Comment #1 from JP Rosevear 2008-06-02 13:51:44 MDT --- Please attach /var/log/NetworkManager with a failing connection (especially if you can can capture a working nm-applet one to the same AP). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Jun 5 Jun

23:29

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User peebhat@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c2 Parameshwara Bhat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|peebhat@gmail.com | --- Comment #2 from Parameshwara Bhat 2008-06-05 17:29:02 MDT --- Created an attachment (id=220576) --> (https://bugzilla.novell.com/attachment.cgi?id=220576) Networkmanager log The attachment shows all connections - failed and succeeded since March 2008.eth0 is wireless connection.eth1 is wired connection. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23:31

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 Parameshwara Bhat changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #220576|application/octet-stream |application/text-plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

6 Jun 6 Jun

06:00

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #220576|application/text-plain |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

9 Jun 9 Jun

12:16

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User peebhat@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c3 --- Comment #3 from Parameshwara Bhat 2008-06-09 06:16:22 MDT --- Created an attachment (id=220996) --> (https://bugzilla.novell.com/attachment.cgi?id=220996) knetworkmanager fails in repeated attempts. One more pattern in the knetworkmanager working is,if it starts failing,it keeps failing endlessly.You reboot and chances are,it comes up with connection ON. This attachment captures the pattern in action today evening. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:26

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c4 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |peebhat@gmail.com --- Comment #4 from Helmut Schaa 2008-06-09 06:26:30 MDT --- The log indicates that KNetworkManager is behaving correctly. In both cases, the succeeded attempt and the failed attempt, KNetworkManager sends the same data to NeworkManager. Are you sure nm-applet is behaving better? Could you please attach /var/log/NetworkManager after a successful connection with KNetworkManager and again after a successful connection with nm-applet? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:47

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User peebhat@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c5 Parameshwara Bhat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|peebhat@gmail.com | --- Comment #5 from Parameshwara Bhat 2008-06-09 09:47:11 MDT --- Created an attachment (id=221063) --> (https://bugzilla.novell.com/attachment.cgi?id=221063) knetworkmanager - nm_applet comparison Hi, Find the comparison you asked for.What I vaguely felt is now corroborated with facts.Nm-applet connects each time consistently in 8 secs whereas knetworkmanager is 200% slower in success.But that can go to 350% slowness as well. Interestingly,each time I logged into Ubuntu,my wlan was connected.Each time I logged into Opensuse,knetworkmanager was not connected. Also,before getting knetworkmanager to connect,I had to lash it repeatedly. The location,angle signal strength nothing changes in between.Like Windows,I can use nm-applet to connect to a lower strength ESSID from a lower floor(Unencrypted).I could never get knetworkmanager to connect to the same network. Both use the same NetworkManager.So wide divergence in performance!It is either a broken NetworkManager in Opensuse or a buggy knetworkmanager. But the former option must be discounted because,if I use knetworkmanager in Kubuntu,I get the same result as Opensuse.In-fact,if Kubuntu is installed,nm-applet shows some bugginess.If alone,Ubuntu gives no reason to complain. Between Ubutnu 7.10 and OS10.3,there was no difference in NetworkManager versions.Both were 0.6.5.Even then this difference existed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11 Jun 11 Jun

08:34

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c6 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tambet@novell.com Status|NEW |NEEDINFO Info Provider| |peebhat@gmail.com --- Comment #6 from Helmut Schaa 2008-06-11 02:34:32 MDT --- Thanks for these detailed test results. Did you try nm-applet and KNetworkManager both with OS 10.3? Or did you try nm-applet only on Ubuntu? (In reply to comment #5 from Parameshwara Bhat)

...

Between Ubutnu 7.10 and OS10.3,there was no difference in NetworkManager versions.Both were 0.6.5.Even then this difference existed.

It is not only the NeworkManager version which could make a difference here but also wpa_supplicant, dhcpcd or dhclient, the driver etc. Nevertheless I do not understand how you measured the time nm-applet and KNM needed to bring the connection up. The first attempt using nm-applet starts at 18:17:00 and is finished at 18:17:12 => 12 seconds whereas the dhcp-request takes 6 seconds The first successful connection using KNM starts at 18:48:22 and is finished at 18:48:38 => 16 seconds whereas the dhcp-request takes 10 seconds ==> The DHCP request makes the biggest difference and that is nothing KNetworkManager can control. That even depends on your networks latency and workload. (In reply to comment #5 from Parameshwara Bhat)

...

Interestingly,each time I logged into Ubuntu,my wlan was connected.Each time I logged into Opensuse,knetworkmanager was not connected.

The first auto connect failed due to NetworkManager not being able to start wpa_supplicant. That's not KNetworkManagers fault either. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13 Jun 13 Jun

13:43

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User peebhat@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c7 Parameshwara Bhat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|peebhat@gmail.com | --- Comment #7 from Parameshwara Bhat 2008-06-13 07:43:53 MDT --- (In reply to comment #6 from Helmut Schaa)

...

Thanks for these detailed test results.

I love Suse.

...

Did you try nm-applet and KNetworkManager both with OS 10.3? Or did you try nm-applet only on Ubuntu?

I tried nm-applet only on ubuntu. I have no Gnome on OS 10.3.Tried installing.It was strangely trying to remove poppler and poppler-qt breaking kdegraphics.

...

(In reply to comment #5 from Parameshwara Bhat)

...
Between Ubutnu 7.10 and OS10.3,there was no difference in NetworkManager versions.Both were 0.6.5.Even then this difference existed.

It is not only the NeworkManager version which could make a difference here but also wpa_supplicant, dhcpcd or dhclient, the driver etc.

You know better.I see your point.I wish I had Gnome on 10.3 to get to the real culprit.

...

Nevertheless I do not understand how you measured the time nm-applet and KNM needed to bring the connection up.

The first attempt using nm-applet starts at 18:17:00 and is finished at 18:17:12 => 12 seconds whereas the dhcp-request takes 6 seconds

The first successful connection using KNM starts at 18:48:22 and is finished at 18:48:38 => 16 seconds whereas the dhcp-request takes 10 seconds

==> The DHCP request makes the biggest difference and that is nothing KNetworkManager can control. That even depends on your networks latency and workload.

Network latency cannot apply partisan on OS 10.3,right?Because what happens on OS 10.3 is regular and consistent.

...

(In reply to comment #5 from Parameshwara Bhat)

...
Interestingly,each time I logged into Ubuntu,my wlan was connected.Each time I logged into Opensuse,knetworkmanager was not connected.

The first auto connect failed due to NetworkManager not being able to start wpa_supplicant. That's not KNetworkManagers fault either.

I am not saying the whole fault should lie in knetworkmanager package.But it manifests in knetworkmanager. But you have obviously missed the other point I made in the beginning.I had observed the same problem with Kubuntu knetworkmanager.There was a huge difference between Kubuntu and Ubuntu in connection,both at version 7.10.But I upgraded to Ubuntu 8.04,not planning to install Kubuntu as I am waiting for OS 11,to be installed on the same partition. If I am not wrong,knetworkmanager codebase lies with OpenSuse.Also,with wired network,knetworkmanager behaves consistently good,which suggests there is no problem around DHCP/DHC client.I suspect there is something in the interaction between knetworkmanager and wpa-supplicant.My suspicion is 'intelligence' born of behaviour,not of code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18 Jun 18 Jun

16:24

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c8 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |peebhat@gmail.com --- Comment #8 from Helmut Schaa 2008-06-18 10:24:25 MDT --- Could you please verify if OpenSUSE and Ubuntu are using the same driver as there are two drivers for broadcom chipsets around (bcm43xx and b43)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19 Jun 19 Jun

12:44

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User peebhat@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c9 --- Comment #9 from Parameshwara Bhat 2008-06-19 06:44:33 MDT --- No, OS 10.3 uses bcm43xx,Ubuntu 8.04 uses b43. I did mention this aspect in the first report. However,I plan to install OS 11.0 by this weekend,which I xpect to come with b43 and brand new networkmanager as well.I will report the result here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

21 Jun 21 Jun

21:36

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User cgoncalves@opensuse.org added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c10 Carlos Gonçalves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cgoncalves@opensuse.org Status|NEEDINFO |NEW Info Provider|peebhat@gmail.com | --- Comment #10 from Carlos Gonçalves 2008-06-21 15:36:15 MDT --- Removing NEEDINFO... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Jun 25 Jun

10:50

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User peebhat@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c11 --- Comment #11 from Parameshwara Bhat 2008-06-25 04:50:21 MDT --- Attaching the NetworkManager log from OS 11.0 below.Now knm is able to connect in 10 secs.Great improvement from earlier times.Also,it can connect to networks at much lower signal strengths than earlier.In all probability,the problem lay in the bcm43xx driver. ------NetworkManager log follows----------------------- Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0) starting connection 'linksys_jindal' Jun 25 15:39:28 linux-ect8 NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 25 15:39:28 linux-ect8 NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0/wireless): connection 'linksys_jindal' requires no security. No secrets needed. Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Config: added 'ssid' value 'linksys_jindal' Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Config: added 'scan_ssid' value '1' Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 25 15:39:28 linux-ect8 NetworkManager: <info> Config: set interface ap_scan to 1 Jun 25 15:39:28 linux-ect8 NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0 Jun 25 15:39:28 linux-ect8 NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2 Jun 25 15:39:29 linux-ect8 NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3 Jun 25 15:39:29 linux-ect8 NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 0 Jun 25 15:39:30 linux-ect8 NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4 Jun 25 15:39:30 linux-ect8 NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 7 Jun 25 15:39:30 linux-ect8 NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'linksys_jindal'. Jun 25 15:39:30 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 25 15:39:30 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Jun 25 15:39:30 linux-ect8 NetworkManager: <info> (wlan0): device state change: 5 -> 7 Jun 25 15:39:30 linux-ect8 NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. Jun 25 15:39:30 linux-ect8 NetworkManager: <info> dhclient started with pid 3095 Jun 25 15:39:30 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jun 25 15:39:30 linux-ect8 NetworkManager: <info> DHCP: device wlan0 state changed (null) -> preinit Jun 25 15:39:37 linux-ect8 NetworkManager: <info> DHCP: device wlan0 state changed preinit -> bound Jun 25 15:39:37 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... Jun 25 15:39:37 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... Jun 25 15:39:37 linux-ect8 NetworkManager: <info> address 192.168.1.104 Jun 25 15:39:37 linux-ect8 NetworkManager: <info> netmask 255.255.255.0 Jun 25 15:39:37 linux-ect8 NetworkManager: <info> gateway 192.168.1.1 Jun 25 15:39:37 linux-ect8 NetworkManager: <info> nameserver '218.186.1.38' Jun 25 15:39:37 linux-ect8 NetworkManager: <info> nameserver '202.156.1.68' Jun 25 15:39:37 linux-ect8 NetworkManager: <info> nameserver '202.156.1.48' Jun 25 15:39:37 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Jun 25 15:39:37 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. Jun 25 15:39:37 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Jun 25 15:39:38 linux-ect8 NetworkManager: <info> (wlan0): device state change: 7 -> 8 Jun 25 15:39:38 linux-ect8 NetworkManager: <info> Clearing nscd hosts cache. Jun 25 15:39:38 linux-ect8 NetworkManager: <info> Policy set (wlan0) as default device for routing and DNS. Jun 25 15:39:38 linux-ect8 NetworkManager: <info> Activation (wlan0) successful, device activated. Jun 25 15:39:38 linux-ect8 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. -----------------End of Log-------------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:58

New subject: [Bug 395477] knetworkmanager is too slow and fails often

https://bugzilla.novell.com/show_bug.cgi?id=395477 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395477#c12 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #12 from Helmut Schaa 2008-06-25 04:58:00 MDT --- Closing as FIXED in 11.0 due to comment #11. Nevertheless thanks for the report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5788

Age (days ago)

5815

Last active (days ago)

List overview

Download

15 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 395477] New: knetworkmanager is too slow and fails often

tags

participants (1)