After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 595066 - NetworkManager manages to connect to 5GHZ N band router but fails to send or receive packets
NetworkManager manages to connect to 5GHZ N band router but fails to send or ...
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.7.x
Other Linux
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2009-09-13 11:33 UTC by car.insurance3
Modified: 2009-11-29 20:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Network Manager running in debug mode connecting to 5Ghz N band network (13.07 KB, text/plain)
2009-09-13 11:33 UTC, car.insurance3
Details
Wireshark packet capture of failure to connect to www.google.co.uk (29.51 KB, application/octet-stream)
2009-09-13 11:38 UTC, car.insurance3
Details
Wireshark packet capture of connection to www.google.co.uk working on the ABG network (23.84 KB, application/octet-stream)
2009-09-13 11:39 UTC, car.insurance3
Details
Package list (rpm -qa) (48.30 KB, text/plain)
2009-09-14 19:12 UTC, car.insurance3
Details

Description car.insurance3 2009-09-13 11:33:19 UTC
Created attachment 143100 [details]
Network Manager running in debug mode connecting to 5Ghz N band network

Sony Vaio laptop VGN-TZ31WN
Wireless Router: linksys WRT610N
laptop wireless chipset: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron]
Network Connection (rev 61)
OS: Fedora Core 11 fully updated as of today Sunday 13th September 2009

I have a 5GHZ N band network in my home and when I try and connect to it, the
conneciton takes a significant amount of time. However, when connected, no
sites are browsable. Also the connection speed is listed as 60Mbps, which drops
to 34Mbps a few seconds later.

The system is dual booting, and booting to WinXP allows the laptop to connect
to the 5GHZ N band network with a connection speed of 300Mbps. A "Mac Book Air"
also connects to the N band router and packets freely.

I include the NetworkManager debug trace, as well as two packet captures. One
where I attempt to connect to http://www.google.co.uk on the N band network,
and another when I attempt to connect on the abg network.
Comment 1 car.insurance3 2009-09-13 11:38:38 UTC
Created attachment 143101 [details]
Wireshark packet capture of failure to connect to www.google.co.uk
Comment 2 car.insurance3 2009-09-13 11:39:27 UTC
Created attachment 143102 [details]
Wireshark packet capture of connection to www.google.co.uk working on the ABG network
Comment 3 Dan Williams 2009-09-14 05:38:37 UTC
Hmm, sounds more like driver problems; there are still some issues with 802.11n support in the kernel at this time.  Not all the features are supported (like wide channels) and it may be hit-or-miss.

What *specific* kernel version are you using, and are the iwlagn drivers the ones that came with that kernel, or did you rebuild them from elsewhere?

uname -a

from a terminal will tell you the specific kernel name.  Thanks!
Comment 4 car.insurance3 2009-09-14 19:11:49 UTC
Hi,

Thanks for the reply. I have found that changing the encryption to TKIP has got the connection up and running but it still only connects @ G speeds. The uname -a displays:

[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.30.5-43.fc11.i686.PAE #1 SMP Thu Aug 27 21:34:36 EDT 2009 i686 i686 i386 GNU/Linux

I have used vanilla kernel drivers. I also include an rpm -qa to show all packages that I have.

I have the channel set to automatic for wide (20/40) on the router.
Comment 5 car.insurance3 2009-09-14 19:12:47 UTC
Created attachment 143184 [details]
Package list (rpm -qa)
Comment 6 Dan Williams 2009-09-18 17:07:24 UTC
Yeah; invalid connections don't get cleared for wired devices on cable plug/unplug, which should really happen; that's getting fixed soon for 0.8 and we may be able to backport to 0.7.x.  Also, we should be retrying failed DHCP connections periodically which is also work-in-progress.

*** This bug has been marked as a duplicate of bug 511581 ***
Comment 7 Dan Williams 2009-09-18 17:09:20 UTC
Sorry, wrong bug, reopening...
Comment 8 Pekka Pietikainen 2009-09-18 17:16:50 UTC
I've had similar problems, Intel 5300 here though. Forcing channel settings on the Linksys helped, but now with 2.6.31 it's happy with wide + auto etc. too.

Both (forcing channels and trying 2.6.31) are worth a shot, I suppose, unfortunately rawhide kernels probably won't trivially go into F11 due to the new initrd things :(
Comment 9 car.insurance3 2009-11-29 20:59:09 UTC
2.6.31 does indeed seem to fix it. Running it fine on FC12