Bug 551861 - Wireless network performance stops with multiple open tabs
Summary: Wireless network performance stops with multiple open tabs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 12
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-02 16:58 UTC by Paul Lambert
Modified: 2010-12-04 00:57 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:57:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
First tcpdump data capture (87.24 KB, text/plain)
2010-01-02 16:58 UTC, Paul Lambert
no flags Details
Second tcpdump data capture (226.45 KB, text/plain)
2010-01-02 16:59 UTC, Paul Lambert
no flags Details

Description Paul Lambert 2010-01-02 16:58:18 UTC
Created attachment 381297 [details]
First tcpdump data capture

Description of problem:
Using FireFox and several open tabs the wireless performance will degrade and eventually stop yielding "server not found" errors in the open tab windows.  Initially, I believed this to be a router problem since I installed a WRT160N which is known to be a lemon.  However, I have upgraded to v3 build 4 and performance improved.  Additionally, the Windows laptop I have does not seem to experience the problem nearly as much as FE-12.  Moreover, I have recently purchased an iPod and it connects up seamlessly with this router.  In fact, while the FireFox on FE-12 is "hanging" on wireless throughput the iPod going through the same router performs fine.  Finally, when performing the same test with FireFox on FE-12 with multiple tabs using an ethernet cable to the router rather than a wireless connection the system performs as expected.  Having said all of this, FireFox on FE-12 using wireless connections to other routers does not demonstrate the same poor performance when going to a WRT54G router.

Version-Release number of selected component (if applicable):
This prolbem has persisted since FE-11

How reproducible: everytime


Steps to Reproduce:
1.open FireFox
2.open several tabs and open web pages
3.observe performance
  
Actual results:
Connectivity to the wireless device shows 3/4 bars but no data throughput

Expected results:
data throughput via wireless connection maintains good performance

Additional info:

I have attached two tcpdump captures.  The first started just after connecting wirelessly to the router up and to when the tabs windows display server not found error.  At this point, I disconnected and then reconnected to the router wirelessly and started surfing multiple tabs again.  This tcp data is captured in the second file.

Comment 1 Paul Lambert 2010-01-02 16:59:32 UTC
Created attachment 381298 [details]
Second tcpdump data capture

Comment 2 Dan Williams 2010-02-09 02:13:36 UTC
Do pings to the default router function normally?  Are there any interesting messages from your wifi device in 'dmesg' ?

Comment 3 Paul Lambert 2010-02-09 04:28:17 UTC
here is one message that might provide a clue to the problem.
wlan0: no probe response from AP 00:18:4d:96:41:4e - disassociating
wlan0: deauthenticated (Reason: 7)
wlan0: authenticate with AP 00:18:4d:96:41:4e
wlan0: authenticated
wlan0: associate with AP 00:18:4d:96:41:4e
wlan0: RX ReassocResp from 00:18:4d:96:41:4e (capab=0x431 status=0 aid=8)
wlan0: associated

I have been using a direct cable from this router and it works just fine.  It's only the wireless that is a problem.  When using ping or arp the repsonses can be many seconds or longer.  When using tcpdump -i wlan0 there are many "whois" queries going out.  It's like the wlan0 device is losing the Mac addresses to IP mapping.  Other computers/IP devices work OK with this wireless router.

Comment 4 Paul Lambert 2010-03-13 14:24:15 UTC
I have retested the wireless ethernet connection on my laptop and found that it now performs as expected.  My suspicion is that the previous software was losing the IP address of the router, and therefore, making multiple lookups at each network transaction.

kernel-2.6.31.12-174.2.22.fc12.x86_64
kernel-2.6.32.9-70.fc12.x86_64
kernel-2.6.32.9-67.fc12.x86_64

I believe this bug can be closed.

Comment 5 Bug Zapper 2010-11-04 02:02:10 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Paul Lambert 2010-11-08 13:03:24 UTC
The performance using multiple open tabs when upgrading to FE-14 and FF 3.6.12 was not observed.  Please close.

Comment 7 Bug Zapper 2010-12-04 00:57:30 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.