802.11n (5Ghz) / UK / Performance

Hi,
I have an Airport Extreme upstairs and 2 x Airport Expresses downstairs (one is extending the network, the other is an ethernet bridge).
When I try and setup the extreme as 802.11n (5GHz only) I get dreadful coverage to downstairs (my MacBook and Expresses can't see it at all). I can connect in the same room via my MacBook but that's about it. With b/g compatibility all is fine again but I really want to boost my internet speed to the lounge where the expresses reside (by boosting the household wireless overall).
I saw old posts about changing country so you can use wide channels etc ... and I've tried some other country settings but the same problem with coverage. Is this a UK restriction - the lack of wide channels means a lack of coverage / performance under 802.11n only?
Thanks in advance for any advice ...

Higher frequency 5 GHz signals are absorbed by any obstructions, walls, etc much more quickly than 2.4 GHz signals. You really almost need line-of-sight between the computer and AirPort Extreme because the 5 GHz signals have much less penetration and distance power.

Similar Messages

  • New Mac Mini and 802.11n 5Ghz - Does it work?

    Does anyone know if this works? It states that it is 802.11a compatible which uses 5Ghz so I am guessing it does. I don't want to have to use a third party internal card like I do now with a separate external antenna. Thanks.

    I have a mac mini I purchased last week (late 2009). I run 5Ghz 802.11n only (there is a g access point in the house, but that's on another part of the LAN). I have an iMac and MacBookPro that connect to the 802.11n and the performance is great - almost half as fast as a direct USB connection - it simply flies.
    However, the mac mini is abysmal. It connects fine - everything works, but I get hardly 1Mbyte per second., despite having full signal strength. This is the info in System Profiler:
    en1:
    Card Type: AirPort Extreme (0x14E4, 0x90)
    Firmware Version: Broadcom BCM43xx 1.0 (5.10.91.19)
    Locale: ETSI
    Country Code: IE
    Supported PHY Modes: 802.11 a/b/g/n
    Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140
    Wake On Wireless: Supported
    Status: Connected
    Current Network Information:
    MyHomeNetwork:
    PHY Mode: 802.11n
    BSSID: 0:23:6c:be:92:08
    Channel: 44,1
    Network Type: Infrastructure
    Security: WPA2 Personal
    Signal / Noise: -52 dBm / -94 dBm
    Transmit Rate: 270
    MCS Index: 15
    If I can't fix this soon, I'm going to have to run a cable to it, which wasn't the idea in my living room!

  • 802.11n 5GHz no longer works on one Macbook

    Good evening,
    Our household has two Macs connected to an Airport Extreme 802.11n (July 2007), both are MacBooks (Late 2006). For well over a year, both have happily connected to the AE using 802.11n 5GHz. A few weeks ago, however, my wife's Macbook stopped connecting. I've tried a number of things (reconfiguring, restarts, reinstalling the last combo updates, etc.) and the only thing that appears to work is dropping the AE to 2.4GHz (I still keep it at 802.11n-only). My Macbook continues to be able to connect just fine at 5GHz, when I enable that on the AE.
    Considering that this drops our available bandwidth from 300Mbps to 130Mbps, I'm not a happy camper, but I'm also tapped out of ideas. I can only guess that there's a hardware malfunction on my wife's Macbook. Her Applecare doesn't expire until 2010, so I may just take it in ...
    Any ideas? One note: my wife is still clinging to Tiger, while I'm on Leopard ... in case that matters.
    Thanks,
    Brice

    Not that I can tell. Suspiciously, we did run a salvo of updates from Software Update and the problems started immediately after, but none of those appeared to be directly related to Airport functionality (firmware or otherwise). Just to be sure, I took the "safe" steps of repairing permissions, re-downloading the last combo update & re-applying it. I also searched for any firmware updates related to Airport. What's odd to me is that the firmware reported on her machine is different than that on mine. They're both Late 2006 Macbook models, so that strikes me as odd (but maybe it isn't). I wasn't able to find any updates that her Macbook was lacking, however.
    My (working) firmware is: [type] AirPort Extreme (0x168C, 0x87), [version] 1.4.8.0
    Her (not-working) firmware is: [type] AirPort Extreme (0x168C, 0x87), [version] 1.4.4
    Based on the card type, it doesn't appear that they're different chipsets, so I'm not at all clear on why the firmware versions differ. Was there a firmware update for Leopard that wasn't available/needed for Tiger?
    Also, I know for sure that there were no firmware updates performed during the last set of updates ... that's a more involved process, if I recall, not handled through the standard updater, I think.
    Thanks for the response!

  • 802.11n 5ghz Connection Problem with OS X 10.4.11 Tiger

    I've searched the communities for answer to this vexing issue to no avail, so I am trying a post.
    Situation:
    I have a dual-band 1TB TC at home set up with three networks: 802.11g/b/a, 802.11n ((5ghz), and Guest Network (g/b).  There are four Macs accessing it: (2) mid-2009 15" MacBook Pros, 2009 MacBook Air, mid-2006 24" iMac.  All are running Snow Leopard 10.6.7 except the 24" iMac (Core 2 Duo) running 10.4.11.
    All Macs can connect to to all networks EXCEPT the iMac which has a problem with the 802.11n (5ghz) connection ONLY.  The iMac has the n-enabler installed (can see it registered when looking at Network Utility).  In fact, the iMac will connect but any attempt to access to the Internet or TC disk stalls the system.  Switch back to 802.11g and everything is fine.
    I've looked at the Console for guidance but cannot find anything problematic (to my eyes, anyway).  I booted this iMac to Snow Leopard from an external disk and the problem cannot be duplicated, so I am assuming this is not a hardware issue with the iMac.  I also, did a fresh install of Tiger and updated it to 10.4.11 plus all Airport updates and n-ebabler on an external drive, booted from this drive and have the same issue with the 5 ghz n-connection.
    By the way, when connected to 802.11n (5ghz) network with the iMac, I have full bars on the menubar fan, but then one bar drops after a minute or so.  When this happens, I cannot access the Internet nor the TC disk.
    I've tried various tweaks as described in the many, many discussion threads here: resets, establish new locations, clear/repair the keychain, and many others.
    I did not have this problem in the past with this iMac, so don't know what has changed with the system configuration.  The g-connection is rock-solid, so Internet access is fine, but file transfer speeds ober the network are obviously much slower now than with the 5ghz n-connection.
    Anyone have any ideas?  Without suggesting an upgrade to 10.6...clearly that should do the trick.  I have other reasons for running Tiger on the iMac.
    Thanks.

    I wonder if all the activity was too much for the hard drive and it failed....you might contact Apple about this repair extension program to see if you qualify...
    http://www.apple.com/support/macbook/hd/repairextension/

  • 802.11n (5Ghz only) network and Remote App.

    I have a Time Capsule set up 802.11n (5Ghz only). iMac, MacBook & New Airport Express all connected to its network. Transmit rate is 270.
    My question is, if my iPod Touch is g rated only, then how can the Remote App control my Airtunes if it cannot connect to my N network. Because it is.

    My Time Capsule
    Wireless Mode=Create a wireless network
    Radio Mode=802.11n only (5GHz)
    My Time Capsule is connected to my Netgear (g only) router via ethernet.
    I have the router broadcasting a g network for my iPod Touch. The Macs & AAE or all connected wirelessly to my Time Capsule N-only Network.
    So the Touch should not be able to connect to my Airport Express as I understand it.

  • AEBS 802.11n 5GHz gives "invalid password" - need a solution!

    After an update to 7.2.1 I've been trying for the past 4 hours to get back on my 5GHz network, but no success. I hope someone can resolve this, because it's getting extremely annoying.
    - 802.11n (b/g compatible) 2.4GHz, pass or no pass -> works
    - 802.11n only 2.4GHz, pass or no pass -> works
    - 802.11n 5GHz, no password -> works
    - 802.11n 5GHz, WPA2 Personal pass -> invalid password
    I tried everyting. First setting it to b/g compatible at 2.4GHz (when it works in Leopard), then to 5GHz -> invalid password. Added it to my preferred networks, hard reset of the AEBS, downgrade to 7.1.1 and a hard reset, new names for the networks, different passwords, deleted everything from the keychain to avoid any mixups, countless reboots...
    No results. I just cannot connect to a 5GHz network, because Leopard claims the password is invalid.
    I have no clue what to do next. It worked fine until I upgraded to 7.2.1, and now even when I downgraded to 7.1.1, it still won't work. And 5GHz works fine without a password. But as soon as you set a WPA2 Personal (this or WPA2 Enterprise, which I don't want), Leopard says invalid password.
    I also noticed that when I setup a preferred network in Leopard, and insert a WPA2 Personal password, it changes it to simple WPA, without the 2, when I save it. Although this is strange, it shouldn't matter. Because when I setup a 802.11n 2.4GHz instead of 5GHz network with a WPA2 Personal password, it works great with my WPA(no 2)-preferred-network settings.
    I'm completely lost here. Who can help me out?
    (Just a tip: do not, I repeat, do not ! update to 7.2.1).

    Hi guys. "Good" to know we're not the only ones. I reported it also, let's hope an update follows soon.
    I still don't know where the problem lies exactly. Mainly because it did work for me in Leopard, after I did a completely clean install last friday. It just picked up the network and it worked. I tried 7.0, 7.1, 7.1.1 and 7.2.1 about 5 times each now. All along with complete hard resets, powerdowns and all the possible settings I could think of, nothing works. First I'd say it's probably the AE firmware, but since nothing works anymore, I'm leaning towards Leopard now...
    Maybe the password isn't being sent correctly to the AE, or the respons of the AE doesn't get received properly. There already was a Keychain update right after the release, maybe there are still more updates in that area, and they'll be included with the next big update.
    If anyone finds a way to fix it, let us know! I'll keep trying, although I don't think it'll do much good

  • Cisco Aironet AIR-SAP2602I-E-K9 WAP -ERROR: VLAN 1000 doesn't exist on 'Radio1-802.11N 5GHZ' (see Services VLAN)

    Hey guys,
    I'm configuring my access points with two SSID's through the GUI. The first is a corporate SSID and the second a guest SSID. The corporate SSID needs to be attached to native VLAN 1000. The guest SSID needs to be attached to VLAN 1234. Both SSID's / VLAN's are to use WPAv2 AES CCMP with a PSK. Although I'm getting an error message indicating that my VLAN's don't exist on ‘Radio1-802.11N 5GHZ’ .  Here are steps I take from start to error...
    Create SSID’s with no security. CORP not to broadcast. Set CORP to use native VLAN 1000. Set guest to use VLAN1234.
    Within security encryption manager > Set encryption mode cipher to AES CCMP on both VLAN 1000 and VLAN1234.
    Within services > VLAN check that both VLAN’s have Radio0-802.11N 2.4GHZ and Radio1-802.11N 5GHZ selected. They do.
    Within Security > SSID Manager – set client authenticated key management to mandatory, enable WPA – WPAv2. Set pre-shared key. Hit apply > “ERROR: VLAN 1000 doesn’t exist on ‘Radio1-802.11N 5GHZ’ (see Services > VLAN).
    I get the same error for both SSID’s. Radio1-802.11N 5GHZ is "checked" against both VLAN's. Am I missing something? Both Radio0-802.11N 2.4GHZ and Radio1-802.11N 5GHZ are enable interfaces and are "up".
    I'm pretty customed to switch and router IOS although have absolutely no exposure to WAP CLI.
    Any assistance appreciated.

    I've resolved this myself. The GUI is basically terrible and very buggy. I used the CLI and was able to add WPA through the CLI.

  • Airport Express - forcing 802.11n 5Ghz setup

    I've just bought a Linksys WRT160NL 802.11n wireless router and and attempting to force the Airport Express to use 802.11n rather than g. When I configure the AE, I join the existing network. There seems to be no way that I can configure it to use n/5Ghz.
    Any suggestions?

    Welcome to the discussions!
    From your post, it sounds like you might have an older "g" AirPort Express. Might that be the case? If so, it would not be able to join an "n" wireless network.
    To confirm, open AirPort Utility and click on Manual Setup for the Express. Then click on the Wireless tab to display the settings page. Hold down the option key while you click on the Radio Mode selection box. If you do not see any "n" options, you have a "g" Airport Express.
    Are you trying to "extend" the wireless network created by the Linksys? I'm afraid this won't work even if you do have an "n" Express because it will only "extend" a wireless network created by other compatible Apple base stations.

  • How do I tell if my MacBook Pro supports 802.11n 5GHz?

    As I wait for my Apple Extreme Base Station, I was wondering if it would make sense to create two different SSID networks. One Mixed b/g for 2.4GHz devices and another one solely for 5GHz. I know my ATV2 supports 802.11n in 5GHz. As I go down my list of devices in my house, I can't tell if my MacBook Pros support the 5GHz. Both MacBook Pros are Mid 2010 models.
    The reason for creating two different networks is that the AEBS downgrades your network based on the lowest device (i.e. b/g would be forced on a n device if such device connects to your network).

    LOLuMad wrote:
    I know my ATV2 supports 802.11n in 5GHz. […] I can't tell if my MacBook Pros support the 5GHz. Both MacBook Pros are Mid 2010 models.
    Of course, you are aware that n operates in both 2.4 and 5GHz.
    Check AirPort in System Profiler. It should list supported modes and supported channels. Then compare supported channels to the list of WLAN channels in the 5GHz band.
    <http://en.wikipedia.org/wiki/List_of_WLAN_channels>

  • Does anyone know if the macbook air supports 802.11n 5Ghz ?

    Does anyone know if the macbook air supports 802.11n Ghz ?

    Every MacBook Air supports 802.11 a/b/g/n and the 2013 models added 802.11 ac

  • I can't see my 802.11n, 5ghz-only network on XP SP2

    Hello everybody,
    here's the problem:
    I can't see a 5GHz-only network on Windows XP SP2 with Boot Camp's drivers. The Atheros 5008 Wireless Network Adapter built inside my Macbook is well known for being capable of managing "n-draft" networks.
    The XP's installed driver, the one provided by Boot Camp, actually is the latest available.
    Obviously I don't have the smallest problem on Mac OS 10.5.2, so why the Atheros 5008 Wireless Network Adapter shouldn't work on Windows XP SP2 when its driver can handle 5 GHz band?
    Here's the proof:
    http://drivers.softpedia.com/get/NETWORK-CARD/OTHER-NETWORK-CARDS/Atheros-AR5008 -Series-Driver-60394.shtml
    Everything is ok with "g" or "b" network (created or not by Airport, as I can see the entire neighbourhood's networks), so the connection goes fine.
    I did the Microsoft's mid-2007 hotfix for WPA2 encryption too as suggested by Apple to Boot Camp 1.2 users. Nothing got better.
    I've spent hours on the internet looking for people experiencing this very issue, without success: could you please help me?
    Thanks in advance.
    Luca

    My MacBook is a Spring '07 model as well. I remember, when I got it, it only supported b/g. Then Apple offered up an update to n, through software update. I wonder if this update only works for OS X (Tiger or Leo shouldn't matter if it was a firmware update).
    Just offering up my thoughts. Anyone else?

  • MBP won't recognize 802.11n 5ghz band

    My sisters MBP can recognize the 5ghz wireless N network but mine wont. My MBP can only detect the 2.4Ghz G network. I am using a Linksys E4200 router. I have it set to where the 2.4Ghz band is using G only and The 5Ghz band is using N only.

    Make sure the router is using a 5 GHz channel that the MBP supports.
    You can get the list in System Information under WiFi.

  • Very poor 802.11n performance

    I'm having difficulties with my time capsule. The performance seems very erratic. Due to me having also having a powerbook I've so far run it in compatible mode.
    But the many problems regarding signal strength and a stable throughput struggling to keep above 485 kb/s prompted me to move the Time Capsule closer to the Powerbook so I could hook it up via cable and completely switch to 802.11n 5ghz, connceting the other computers wirelessly.
    Unfortunately, it doesn't work. The performance is laughable, I get a mere 5000 kb/s down (internet based test) whereas I normally (2.4 ghz n/b/g compatibel) i get just under 2 MB/s.
    Sending files to and from a connected harddrive is also very very very slow.
    What is wrong with the Time Capsule? Is it interference from the (bastards) around me that all have their routers setup to automatically chose channel?
    Is my time capsule broken? Is my computer broken? What is wrong?
    I'm close to returning the device.

    I've just completed an experiment.
    Two iMacs side-by-side. One with Airport Utility 5.4.1 ("new"), second with Airport Utility 5.3.1 ("old"). Time Capsule with firmware 7.4.1.
    Initial tests for connection Rate:
    "New" average about 122
    "Old" average about 232 (about twice the Rate)
    Installed Airport Utility 5.4.1 on "old" iMac.
    New tests for connection Rate:
    Both averaging about 116
    To me this suggests an effect of the "upgrade" to 5.4.1. But could this be the case? I'm not going to downgrade the firmware quite yet until I rule this and any interference issues out.

  • Packet loss / pausing when using 802.11N (Intel 6300)

    Hi,
    Previously, I had posted a thread involving the Intel 6250, and lack of detection of N WiFi on that card. Some time later, I bit the bullet and got an Intel 6300 card off eBay. After receiving it today, I popped it into my Thinkpad X220, and it worked.... sort of. I can definitely see wireless N support, and can associate with my 2.4 GHz mixed-mode B/G/N network at 130 Mbps, and my 5 GHz N-only router at around 243 - 270 Mbps. However, right off the bat, it seems the number of "Tx Excessive Retries" in iwconfig climb up to several thousand within ~ 15 - 20 minutes of connecting. Also right off the bat, pings are rather inconsistent (typically at least 2 ms greater than when the card is forced to work in G-only mode, and with pauses and spikes up to 800 - 2000 ms, and packet loss from 5 - 10%)
    From what I have gathered so far, there has been a bug in the iwlwifi kernel tree that affects N wireless users, and this bug has been around since around 2010 or even earlier. However, I was under the impression that some sort of fix has been merged into the mainline Kernel at this point (I'm on 3.5.3-1-ARCH BTW), and my symptoms are somewhat less aggressive than the ones others described (basic web browsing works reasonably well, though there is often noticeable lag in the response times, but anything latency/packet loss-sensitive will suffer in a major way.) Has anyone managed to get wireless N to actually work reasonably well on Arch (or for that matter, ANY linux distro)? As I understand it, the matter is one of relation to the kernel module itself, so distro-distro variations of userspace apps shouldn't be as much a factor anyway. I am using WICD for my network manager, and am happy to say that it does its job admirably well (assuming the card is set to G-only mode, but the connection itself is actually maintained quite stably even in N mode.)
    While I understand that the 11n_disable=1 "fix" allows most people to get on with their lives, I am rather alarmed that this is being considered a long-term solution. Many laptop owners (ThinkPad owners like myself for example) are essentially locked into Intel WiFi cards, unless we are willing to take an expensive risk and flash our BIOS to one that that doesn't have a "whitelist" of approved cards (something that can void the warranty or worse, brick a laptop.) All the while, Intel is still claiming Linux support for a card whose major capabilities are essentially neutered purely based on the OS a user chooses to run (yes, I do consider N to be a major capability, considering 300 Mbps N WiFi is basically old news, with many manufacturers coming out with full 450 Mbps routers. Also, chipsets like Atheros seem to have no problems with offering both performance and stability under Linux... my desktop rig using an Atheros card manages perfectly fine on a full-rate wireless-N network with essentially no packet loss or latency spikes.)
    Below is some information that might be useful:
    iwconfig (802.11g, ~ 1 hour after connection and running a few speedtests, browsing, ping testing):
    wlan0 IEEE 802.11abg ESSID:"dd-wrt"
    Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
    Bit Rate=54 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=69/70 Signal level=-41 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:359 Missed beacon:0
    iwconfig (802.11n, 5GHz after ~10 minutes browsing/ping testing):
    wlan0 IEEE 802.11abgn ESSID:"net2"
    Mode:Managed Frequency:5.745 GHz Access Point: XXXXXX
    Bit Rate=243 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=55/70 Signal level=-55 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:860 Invalid misc:50 Missed beacon:0
    iwconfig (802.11n, 2.4 GHz after connecting and running a speedtest):
    wlan0 IEEE 802.11abgn ESSID:"dd-wrt"
    Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
    Bit Rate=117 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=66/70 Signal level=-44 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:974 Invalid misc:59 Missed beacon:0
    dmesg | grep iwl :
    [12011.488089] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [12011.488092] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
    [12011.488269] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [12011.488271] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050f8000
    [12011.488273] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [12011.488585] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
    [12011.491862] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [12011.492112] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
    [12011.492114] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
    [12011.492116] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
    [12011.492117] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
    [12011.492119] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
    [12011.492121] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [12011.492206] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.502925] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [12011.502928] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
    [12011.502930] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
    [12011.502946] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [12011.503105] ieee80211 phy8: Selected rate control algorithm 'iwl-agn-rs'
    [12011.503456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.503661] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12011.745631] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.745868] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12073.651471] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [12073.651474] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
    [12073.651660] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [12073.651661] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050b8000
    [12073.651663] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [12073.652241] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
    [12073.655662] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [12073.655887] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
    [12073.655890] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
    [12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
    [12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
    [12073.655892] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
    [12073.655894] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [12073.655975] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.666587] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [12073.666593] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
    [12073.666595] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
    [12073.666618] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [12073.667056] ieee80211 phy9: Selected rate control algorithm 'iwl-agn-rs'
    [12073.667456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.667659] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12073.908411] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.908632] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.261869] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.262090] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.487757] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.488010] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.699574] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.699781] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.837322] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.837526] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12097.329577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12097.329832] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12097.797748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12097.797970] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12098.016220] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12098.016458] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.458762] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.459006] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.608769] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.609021] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.764093] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.764341] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.979029] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.979228] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12101.159987] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12101.160208] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    lshw | less :
    *-network
    description: Wireless interface
    product: Centrino Ultimate-N 6300
    vendor: Intel Corporation
    physical id: 0
    bus info: pci@0000:03:00.0
    logical name: wlan0
    version: 35
    serial: 00:24:d7:be:9e:74
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress bus_master cap_list ethernet phy
    sical wireless
    configuration: broadcast=yes driver=iwlwifi driverversion=3.5.3-
    1-ARCH firmware=9.221.4.1 build 25532 ip=192.168.1.145 latency=0 link=yes multic
    ast=yes wireless=IEEE 802.11abgn
    resources: irq:50 memory:f2500000-f2501fff
    Thanks,
    - A.G.

    I have an ASUS UX32VD-DB71 which has the Intel Centrino 6235 wifi card. I've been having this laptop for more than 6 months and I've tried different solutions to fix the issue with Wireless-N but none of them were stable other than disabling N completely using 11n_disable=1
    I've tried different kernels all the way from 3.2 to the latest 3.7 series of kernels (both in the openSUSE tree as well as mainline) with no luck whasoever. I also tried installing the compat-drivers from 2013-01-23-1-u version onto my 3.6 kernel which provided the same results too. I see packet loss with N and the G speeds are just too slow. I have a workstation in my network and I can only transfer effectively at 1.5 MB /s max over G whereas an old laptop from 2007 which has an 1x1 MIMO antenna (again Intel though) can connect at 144 Mbps to my router and transfer files at least 3-4 times faster (if not more).
    It is totally unacceptable for Intel to not just fix this issue for Linux.
    Last edited by Tuxdude (2013-02-17 01:38:59)

  • Slow data transfer with Time Capsule on 802.11n ?

    Hi,
    Actually, I don't know where to start. But let's explain my setup first:
    My iMac (wired) and AppleTV (wireless) are connected to the Time Capsule (802.11n, 5Ghz)
    My girlfriend's MacBook and 2 x iPhone 2G's (wireless) are connected to an Airport Extreme Base station (802.11b/g compatible).
    The Time Capsule and AEBS are connected and show two different networks.
    Now the problem:
    When I copy files from e.g. the iMac to the MacBook or to the Apple TV, it's very slow. I've used scp to copy a 200 mb file and it took about 1.20 minutes (at 2.5MB/s). I've did the same when the iMac was connected over wireless and it took about 3.45 to 4.30 minutes (at 1.0MB/s).
    I'm not sure if this IS slow, but it certainly feels like it. 802.11n should be around 100 Mb/s in practice and 802.11b/g around 20-25 Mb/s.
    By the way: downloading from the Internet is excellent, I get the full download/upload speed my provider offers for my subscription.
    Second, I added the signal strength/noise levels for the Time Capsule attached devices. They vary around -68Db signal, -90Db noise.
    The question is: are these levels normal ? What should be higher or lower ?
    Thanks in advance !
    Rutger

    The new Airport Extremes and Time Capsules suffers from terrible performance over the 5GHz band and it's a problem that not only affects me and you, but hundreds of thousands of other owners.
    Nobody knows if it's a firmware problem or the Marvell chips inside that's the problem, and Apple hasn't said or done anything for months.
    I'm still hoping for a firmware update to solve this, but if it doesn't get fixed soon enough, I'm gonna return it and go back to backing up to wired disk and my rock solid Airport Express.
    Not the happiest answer, but at least you have a clue now.
    Cheers,
    Koski

Maybe you are looking for