AR9220 802.11an but no bgn?

I'm thoroughly confused by the output I'm getting from an AR9220 card: it claims to support 5GHz band only.
I've never heard of 5GHz single-band cards, and it was labeled abgn, and AR9220 is usually listed as abgn chip with built-in radio part.
Can anyone please take a look at the output and maybe clarify it for me or maybe point out what I'm missing here?
Is it hw limitation, firmware, or the driver?
My ultimate goal is to make it work as an AP in 2.4GHz range.
Initially the card showed domain 00 with all frequencies scan-only or disabled, but after messing with the CRDA stuff (who knew it depends on stinky udev and its helpers?) I managed to get it working in 5GHz AP mode.
But I need 2.4GHz.
iw list output:
Wiphy phy0
Band 1:
Capabilities: 0x11ce
HT20/HT40
SM Power Save disabled
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 5180 MHz [36] (13.0 dBm)
* 5200 MHz [40] (19.0 dBm)
* 5220 MHz [44] (19.0 dBm)
* 5240 MHz [48] (19.0 dBm)
* 5260 MHz [52] (19.0 dBm)
* 5280 MHz [56] (19.0 dBm)
* 5300 MHz [60] (19.0 dBm)
* 5320 MHz [64] (20.0 dBm)
* 5500 MHz [100] (20.0 dBm)
* 5520 MHz [104] (20.0 dBm)
* 5540 MHz [108] (20.0 dBm)
* 5560 MHz [112] (20.0 dBm)
* 5580 MHz [116] (20.0 dBm)
* 5600 MHz [120] (20.0 dBm)
* 5620 MHz [124] (19.0 dBm)
* 5640 MHz [128] (19.0 dBm)
* 5660 MHz [132] (19.0 dBm)
* 5680 MHz [136] (19.0 dBm)
* 5700 MHz [140] (19.0 dBm)
* 5745 MHz [149] (20.0 dBm)
* 5765 MHz [153] (20.0 dBm)
* 5785 MHz [157] (20.0 dBm)
* 5805 MHz [161] (20.0 dBm)
* 5825 MHz [165] (20.0 dBm)
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
max scan IEs length: 2261 bytes
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* P2P-client
* P2P-GO
software interface modes (can always be added):
* AP/VLAN
* monitor
interface combinations are not supported
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
Device supports RSN-IBSS.
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Relevant parts from kernel output:
[ 0.075315] cfg80211: Calling CRDA to update world regulatory domain
[ 0.078403] NetLabel: Initializing
[ 0.079004] NetLabel: domain hash size = 128
[ 0.080003] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.081143] cfg80211: World regulatory domain updated:
[ 0.082003] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 0.083009] cfg80211: (2402000 KHz - 2480000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 0.084010] cfg80211: (5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A, 3000 mBm)
[ 0.085094] NetLabel: unlabeled traffic allowed by default
[ 2.033744] ath: EEPROM regdomain: 0x0
[ 2.033759] ath: EEPROM indicates default country code should be used
[ 2.033776] ath: doing EEPROM country->regdmn map search
[ 2.033799] ath: country maps to regdmn code: 0x3a
[ 2.033815] ath: Country alpha2 being used: US
[ 2.033866] ath: Regpair used: 0x3a
[ 2.034143] Switching to clocksource tsc
[ 2.043210] cfg80211: Updating information on frequency 5180 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043244] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043268] cfg80211: Updating information on frequency 5200 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043299] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043324] cfg80211: Updating information on frequency 5220 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043355] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043378] cfg80211: Updating information on frequency 5240 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043409] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043433] cfg80211: Updating information on frequency 5260 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043465] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043488] cfg80211: Updating information on frequency 5280 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043518] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043543] cfg80211: Updating information on frequency 5300 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043574] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043598] cfg80211: Updating information on frequency 5320 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043628] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043653] cfg80211: Updating information on frequency 5500 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043684] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043708] cfg80211: Updating information on frequency 5520 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043738] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043763] cfg80211: Updating information on frequency 5540 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043794] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043818] cfg80211: Updating information on frequency 5560 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043849] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043874] cfg80211: Updating information on frequency 5580 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043905] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043929] cfg80211: Updating information on frequency 5600 MHz for a 20 MHz width channel with regulatory rule:
[ 2.043959] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.043984] cfg80211: Updating information on frequency 5620 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044049] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044073] cfg80211: Updating information on frequency 5640 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044104] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044129] cfg80211: Updating information on frequency 5660 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044160] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044183] cfg80211: Updating information on frequency 5680 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044213] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044238] cfg80211: Updating information on frequency 5700 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044269] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044293] cfg80211: Updating information on frequency 5745 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044323] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044348] cfg80211: Updating information on frequency 5765 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044379] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044403] cfg80211: Updating information on frequency 5785 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044433] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044458] cfg80211: Updating information on frequency 5805 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044489] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.044513] cfg80211: Updating information on frequency 5825 MHz for a 20 MHz width channel with regulatory rule:
[ 2.044543] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.045103] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 2.047173] cfg80211: Calling CRDA for country: US
[ 2.052209] Registered led device: ath9k-phy0
[ 2.052237] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xd0820000, irq=9
[ 2.059065] cfg80211: Updating information on frequency 5180 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059097] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059124] cfg80211: Updating information on frequency 5200 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059154] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059177] cfg80211: Updating information on frequency 5220 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059207] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059232] cfg80211: Updating information on frequency 5240 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059262] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059286] cfg80211: Updating information on frequency 5260 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059316] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059341] cfg80211: Updating information on frequency 5280 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059371] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059394] cfg80211: Updating information on frequency 5300 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059424] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059449] cfg80211: Updating information on frequency 5320 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059480] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059504] cfg80211: Updating information on frequency 5500 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059534] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059559] cfg80211: Updating information on frequency 5520 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059589] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059613] cfg80211: Updating information on frequency 5540 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059643] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059668] cfg80211: Updating information on frequency 5560 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059698] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059722] cfg80211: Updating information on frequency 5580 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059752] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059777] cfg80211: Updating information on frequency 5600 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059807] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059830] cfg80211: Updating information on frequency 5620 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059860] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059885] cfg80211: Updating information on frequency 5640 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059916] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059940] cfg80211: Updating information on frequency 5660 MHz for a 20 MHz width channel with regulatory rule:
[ 2.059970] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.059995] cfg80211: Updating information on frequency 5680 MHz for a 20 MHz width channel with regulatory rule:
[ 2.060056] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.060080] cfg80211: Updating information on frequency 5700 MHz for a 20 MHz width channel with regulatory rule:
[ 2.060110] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.060135] cfg80211: Updating information on frequency 5745 MHz for a 20 MHz width channel with regulatory rule:
[ 2.060165] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.060189] cfg80211: Updating information on frequency 5765 MHz for a 20 MHz width channel with regulatory rule:
[ 2.060219] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.060244] cfg80211: Updating information on frequency 5785 MHz for a 20 MHz width channel with regulatory rule:
[ 2.060274] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.060298] cfg80211: Updating information on frequency 5805 MHz for a 20 MHz width channel with regulatory rule:
[ 2.060328] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.060353] cfg80211: Updating information on frequency 5825 MHz for a 20 MHz width channel with regulatory rule:
[ 2.060383] cfg80211: 5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm)
[ 2.060425] cfg80211: Regulatory domain changed to country: US
[ 2.066296] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 2.074516] cfg80211: (2402000 KHz - 2480000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 2.081959] cfg80211: (5130000 KHz - 5850000 KHz @ 40000 KHz), (N/A, 3000 mBm)
iw reg get shows domain 00 and whatever the kernel has for that domain.
iw reg set XX says repeats the same freq selection but it changes nothing in iw list or iw reg get output.
This is while the kernel is configured to use a built-in db.tx, with all-open entries for 00 and US.
hostapd complains about inability to use selected hw_mode (b or g):
Hardware does not support configured mode
wlan0: IEEE 802.11 Hardware does not support configured mode (1) (hw_mode in hostapd.conf)
Could not select hw_mode and channel. (-2)
wlan0: Unable to setup interface.
Last edited by axs (2012-10-05 19:07:14)

Hm, yeah, you're right. Googled a bit more and found them. WLM200N5, MikroTik R5nH etc.
They all look quite differently from what I've got however, pcb-wise mine seem to match dual-band WLM200NX exactly.
Anyway, I overrode eeprom setting today and forced it into 2.4GHz mode.
Frequencies are reported, hostpad starts but I get no signal whatsoever.
So looks like it's hw problem and 2.4 was disabled for a reason.

Similar Messages

802.11an 40 Mhz channels with WLC (7.4)

Hi
I would be interested to learn if anyone has enabled 40mhz channels in 802.11an.
Did this cause you any issues?
Any client compatibility issues?
What about sites with a mix of 802.11a and 802.11an AP's?
(I'd be inclined to enable this in sites with only 802.11an AP's. but would appreciate the thoughts\experience of others)
Do the clients become sticky to the 802.11an AP's?
Thanks in advance!

I've enabled 40 Mhz since deploying 802.11n APs in 2009.
The only issue I have noticed are the drivers for 802.11n wireless NIC needs to be updated. We had cases where the clients would report there's not enough wireless signal even though they are standing underneath the AP. We soon discovered that the drivers were out of date. Going to get the "updated" drivers from the laptop manufacturers website was not a smart move (because the drivers were equally out of date). The solution was to go to the wireless NIC manufacturer's website and pull the latest drivers. This fixes the issue. Now, when we push updates to the laptops, we make sure the wireless NIC driver is one of them.

My wifi network is 802.11n but there are times changing for 802.11g, and have to restart ... after the update for Mountain Lion

My wifi network is 802.11n but there are times changing for 802.11g, and have to restart ... after the update for Mountain Lion... Help!!!
Several problems with Mountain Lion, APP STORE (login/logout error), WIFI(802.11n for 802.11g), MAIL (horrible)... Apple, what is happening?

Do a factory reset .. nothing will be deleted from your backups and you will be able to get access to them again.
The Factory Reset Gen1-4.
Unplug your TC. Hold in reset. and power the TC back on.. without releasing reset for about 10sec. When the status light flashes rapidly; release it.
Be Gentle! Feel the switch click on. It has a positive feel.. add no more pressure after that.
TC will reboot after a couple of minutes with default factory settings and will wipe out previous configurations.
No files are deleted on the hard disk.. No reset of the TC deletes files.. to do that you use erase from the airport utility.

New Macbook Air will not connect to 802.11n, but my old 2011 model will

I have just bought a new MBA 13", i7, 8 GB RAM, 256 GB SSD.
When I connect to my home network I see it as a 802.11n network, but as soon as I log on, I only have 802.11g connection. I still have my old 2011 MBA, and it connects to the n-standard just fine.
I went to the local Apple reseller to have them look at it, but the problem was not present when connecting to their airport extremes.
Has anyone else had this kind of problem, and is there a known fix?
Casper

The warranty entitles you to complimentary phone support for the first 90 days of ownership. If you bought the product in the U.S. directly from Apple (not from a reseller), you also have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different.

ISE 1.2, Supplicant configured for 802.1x but need to MAB

I posted this yesterday but deleted the thread thinking I had fixed the issue - alas I was wrong. In summary I have a scenario where I am doing wired 802.1x and also wired MAB/CWA. The issue is that a certain number of external/BYOD hosts have supplicants configured for 802.1x at their "home" organisations which for obvious reasons can't authenticate on this network. The idea is that MAB and CWA become a fallback but these hosts in question don't efficiently fail to MAB.
If the host has validate server certificates enabled (and doesn't have our root selected) then 802.1x fails and goes to MAB as per the tx timers etc. Hosts that don't validate certificates essentially fail authentication, abandon the EAP session and start new... this process seems to continue for a very long time.
Does anyone have any similoar experiences and if so can you provide some info? I am looking into tweaking 802.1x port timers to make this fail quicker/better but am not confident this will fix the issue.
Thanks in advance

Maybe the held-period and quite-period parameters would help. I would not change the TX period to anything shorter than 10 seconds. Every cisco doc that I have ever seen has said this same recomendation and I can tell you from experience you will have devices at times that will authenticate via MAB when you dont want them to if you decrease lower than 10 seconds.
Read this doc for best pratices including the timers listed below.
I hope this link works. http://d2zmdbbm9feqrf.cloudfront.net/2014/eur/pdf/BRKSEC-3698.pdf
If not goto www.ciscolive365.com (signup if you havn't already) and search for
"BRKSEC-3698 - Advanced ISE and Secure Access Deployment (2014 Milan) - 2 Hours"
Change the dot1x hold, quiet, and ratelimit-period to 300.
held-period seconds
Configures the time, in seconds for which a supplicant will stay in the HELD state (that is, the length of time it will wait before trying to send the credentials again after a failed attempt). The range is from 1 to 65535. The default is 60.
quiet-period seconds
Configures the time, in seconds, that the authenticator (server) remains quiet (in the HELD state)
following a failed authentication exchange before trying to reauthenticate the client. For all platforms except the Cisco 7600 series Switch, the range is from 1 to 65535. The default is 120.
ratelimit-period seconds
Throttles the EAP-START packets that are sent from misbehaving client PCs (for example, PCs that send EAP-START packets that result in the wasting of switch processing power). The authenticator ignores EAPOL-Start packets from clients that have successfully authenticated For the rate-limit period duration. The range is from 1 to 65535. By default, rate limiting is disabled.

High Latency experienced once connected to 802.11g, but linktest results appear healthy?

I was connected at 802.11g and was running a continual ping to the DG interface on the L3 switch to which the WLC is connected too.
Response times were healthy almost all day and then they jumped very high. They continued to stay high for a long period. I disconnected (to wired) and then reconnected to the wireless and got the same results. I then disconnected for some time (connected via wired) and then reconnected via Wireless again - to which I got the same results. I stayed on the wireless connection and then it decided to come right. During this time high response time period I ran a linktest to my MAC address from the WLC and got the following results.
(Cisco Controller) >linktest 1C-65-9D-E4-55-16
Link Test to 1C-65-9D-E4-55-16.
        Link Test Packets Sent.......................... 20
        Link Test Packets Received...................... 19
        Local Signal Strength........................... -50dBm
        Local Signal to Noise Ratio..................... 44dB
Seems healthy? But yet I was getting these appalling response times. The WAP and WLC are plugged into the same L3 switch. When I connected to the wired interface my response times returned to what is expected.
I have attached the output to this discussion for review.
Any ideas as to what this would be a result of? please note that this occurred outside of peak usage hours - also note that I have seen this before another time during peak times. But no alerts or traps seen on the WCS or WLC?
Any thoughts or ideas would be appreciated.

Why put up with all that when a call to VZ will get you a replacement router?
The Westells were a good router in their day, but are now obsolete and no longer issued by VZ.

Imac 17" 1.83ghz - OK, it's incompatible, but how can you use 802.11n???!

The Imac Intel G5 17" 1.83ghz does not work with airport extreme's draft 802.11n, for whatever reason. What are the ways to make it compatible? Currently using it on 802.11g but I do want to use the 802.11n.....
Any ideas?
Many thanks.

The Imac Intel G5...
Intel and G5 are 2 completely different things. You do not have a G5 you have an Intel-based iMac. It either has the "Core Duo" processor or "Core 2 Duo" processor.
You should take a look at some of the USB solutions offered by QuickerTek.

How fast can Broadcom 802.11n support for maximum?

hey everybody,i got U160 yesterday that the WLAN adapter is Broadcom 802.11n but i just got a connection speed of 65Mbps but i can get 150 Mbps with my G230 with intel 5100 bgn ,connecting to the same N-Router,so i am wondering how fast can Broadcom 802.11n support for maximum.......

if readycomm installed, remove it.
check your firewall is active and using high performance.
by the way, which model of broadcom are you using?

Does 802.11n give a speed boost on the iPad?

I did some testing to see if I'd get a speed boost by enabling 802.11n on my Belkin F5D8233-4 router, which supports 802.11n draft specification. I have Verizon FIOS with 25Mbps download/upload. I also have the Verizon router, which only supports 802.11b/g, and I can switch which router I'm connected to in order to compare speeds of 802.11n and 802.11g. All tests were done less than 3 feet from either router.
Bottom line is that the iPad doesn't get any speed boost by using 802.11n, at least by using speedtest.net to do the testing.
The test I used was with the speedtest app for the iPhone. I made the Belkin a pure 11n router, and ran that app from the iPad. So the connection had to be 802.11n. Then I connected the iPad to my Verizon router, which had to be 802.11g, and saw virtually no difference.
I did the same test with a Windows laptop from my job that supports 802.11n. It connected locally to the Belkin router at 72Mbps according to the internal utility. Testing using speedtest.net indicated that using the 802.11n connection on the Belkin was 50% faster than the 802.11g connection on the Verizon router. (About 30Mbps for Belkin/802.11n compared to 20Mbps for Verizon/802.11g for downloads).
But with the iPad, doing the same test (switching from Belkin router to Verizon router), the speed didn't change. It actually seemed a little slower when I was on 802.11n, but repeated tests showed some variability, and the average was about 19Mbps.
I realize that the overall speed for the iPad when I'm in my house will get throttled by the FIOS connection max of 25Mbps (although it's interesting that with my MacMini, and the Windows laptop, when connected via 100baseT, I get 30Mbps from FIOS when they promise 25Mbps!). But I can't get the good results from the iPad using 802.11n that I see with the Windows laptop. I'd like to try a local speedtest using the local LAN. I installed Speedtest MINI on the MacMini, enabling the Mac as a server, and the Windows laptop did 72Mbps on the local LAN. But Speedtest MINI requires Flash in the browser, so I can't do that test on the iPad. And the Speedtest app for iPhone doesn't let you pick a local URL for the server.
So I'm now pretty sure that 802.11n isn't really working right on the iPad with my Belkin router, in terms of delivering increased performance. I've read other posts where people have looked at the transmit rate from the router side, but I really wish I could look at the transmit rate from the iPad (like I do in Mac OS X, or in Windows) to verify.
To be sure, I'd like to run a speedtest on my local LAN from the iPad. Has anyone been able to actually do some kind of test that verifies the speed of an iPad connection on a local LAN, and does that verification from the iPad, and not the router?
And finally, has anyone ever done a test that verifies that 802.11n from an iPad delivers a speed boost compared to 802.11g? Are there specific requirements on the router side that need to be satisfied so that the iPad gets a boost? I've read elsewhere where someone said that you only get the boost if using Apple's Airport Extreme as the router (so that you can't really get 802.11n on a non-Apple router), and I think I saw someone say that the router has to support communication over 5.0Ghz for the iPad to be fast on 802.11n. Has Apple ever said what are the real requirements for the iPad to be faster on 802.11n versus 802.11g?

To the contrary, my experience is that the "G" standard on WiFi provided MUCH faster speeds than the "N" standard on Wi-Fi. It makes no sense, I know, but it is true.
I was having horribly slow Wi-Fi speeds on my iPad2, despite a fast cable modem connection and a "N" generation Linksys wireless router (maybe 2-3 yrs old). Was achieving speeds of only 1.3Mbs -- slow enough that you couldn't watch YouTube videos. From hunting around on the web, I came across the suggestion to manually set the Wi-Fi router to the "G" standard (ie downgrade it from the faster "N" standard). Remarkably, I did it and it worked like a charm. I now get Wi-Fi speeds of about 12 or 13 Mbs, or 10x what I was getting before. It is an easy fix. And also I think the "G" standard is capable of 50Mbs so even though it is a slower and older standard, it is still way faster than anything you are likely to achieve as a home user. I think there is some glitch or oddity in the iPad and iPad2 which can cause it to perform very poorly with older "N" standard WiFi routers. New ones don't seem to have a problem.

Airport Express, WPS, 802.11n and 7.5.2 firmware - can this work?!

Can't believe this hasn't happened to anyone else, but I can't find a relevant thread.
I have a Time Capsule and an Airport Express base station. The Time Capsule was configured as a WDS base station, and the Express as a WDS Relay. The Express is less than a year old, ie 802.11n.
Everything worked beautifully until firmware upgrade 7.5.2 which self-installed on the Time Capsule just as you would expect - except the relay stopped working.
I've tried everything I can imagine, but I can't get the two devices to communicate with each other any more (even with the new firmware on the Express). I have read somewhere on the Apple site that WDS "doesn't work" with 802.11n, but this doesn't fully explain how it did work with 802.11n up until the time of the firmware upgrade to put it mildly. And releasing a firmware "upgrade" that stops existing configurations working, without warning, is not really an Apple thing to do.
One thing I haven't tried is to revert to older firmware; do I really have to do that? Or is there something wrong here please, Apple? Or did I just imagine, for those 9 months, that the relay was working sweetly?!
Don't know if this is related, but Airport Utility almost consistently fails to see both devices if they are both switched on, but can only see one or the other. Is it possible that the Express has developed a fault?
Please help; I have an old house and I can't penetrate most of it without my WDS!!

Might this apply?
AirPort Firmware Update 7.5.2 does not install on an extended Wi-Fi base station
http://support.apple.com/kb/TS3433

Ip phone is not working with 802.1x port

i can authenticate the pc using 802.1x, but its not working with ip phones...waiting for your kind reply..

The switch is 4006 and the image is cat OS 7.3(2).
The port configuration is
set radius server X.X.X.X
set radius key xxxxxx
set dot1x system-auth-control enable
set port dot1x 3/17 port-control auto
set port dot1x 3/17 initialize

MacBook Pro can connect via Airport but not iPhone or iBook G4.

Anyone have any ideas? My Macbook Pro can connect to my Airport (v.7.3.1, 802.11n) but not my iPhone or iBook or a Windows Computer or WiFi Blackberry.
The connection is strong and detectable by the ibook but "unable to connect".
Somethings up with the settings but not sure what.
Any ideas?
HELP!
thanks
--K

I've tried Channel 1,2,3,4,5 (still need to try the others)
Secured or unsecured the only wireless connection that works is my MacBookPro.
I get the message "unable to join network..." The connection is very strong.

New dual-band time capsule but computers only access 2.4ghz channel

Just set up a new dual-band Time Capsule (bought it prior to the latest release though). Everything is working so far - Time Machine, wireless internet - but I noticed that both computers in the apartment (2 Macbook Pros - one running 10.5.6, the other 10.6.1) are only accessing the wireless network on Channel 2 (2.4Ghz). And on the laptop running Snow Leopard, I'm only seeing transmit rates of between 50-100. On the Leopard laptop I see up to 130. Doesn't this suggest that the computers are only using the "b/g" band and not the "n" band? When I option-click on the airport menu icon on the SL laptop it does say PHY mode is 802.11n, but I have no idea what PHY mode means frankly.
I feel as though the laptops should be connecting on a much higher channel and seeing much higher transmit rates (closer to 300?), but I'm not at all well-versed in these wireless realms. Any help would be much appreciated...
thanks
Tom

Welcome to the discussions, Thomas!
+"And on the laptop running Snow Leopard, I'm only seeing transmit rates of between 50-100. On the Leopard laptop I see up to 130. Doesn't this suggest that the computers are only using the "b/g" band and not the "n" band?"+
If you were receiving "g" rates, the number would be 54 or less depending on the distance from the router to the computer, so you are seeing some "n" speeds from the 2.4 GHz network. I believe the default setting for this "guest" band is 802.11n (802.11b/g compatible).
Would suggest that you contact Apple as a number of users have reported that either the main network or guest network is not functioning correctly.
The default setting on the main network is 802.11n at 5 GHz, so if you have a good connection and are relatively close to the router, you should see speeds in the 200-270 range.
Many users assume that 5 GHz is a stronger signal, but the facts are that 5 GHz signals are absorbed by walls and obstructions much more quickly than 2.4 GHz signals, so depending on your home construction, distance from router, etc., the 5 GHz signal may not be strong enough. Your computers will connect to the strongest signal. If that's the 2.4 GHz band, that's where they will connect.

Late 2007 Macbook Pro 802.11n slow transmit rate

I have a Netgear Rangemax N router. But when I connect to the network and option+click on the wifi, my PHY Mode says "802.11n" but my transmit rate is only 54. When my Macbook air connects to the same router, the PHY Mode is still 802.11n, but my transmit is 170. What is happening that my Macbook Pro is connecting slower than the Macbook Air when on the same network?

When I read "crash," "distorted line across my screen," "it gets really hot," and "2007 17" MacBook Pro," the first thing that comes to mind is logic/graphics board. Visit your local Apple Store, and see if they can validate this suspicion or not. The SMART utility reading usually precedes a drive failure, but it's hard to conclude what's happening here.
In the meantime, make sure you're completely backed up. If you don't back up, purchase an external HD, and back up with SuperDuper. Preserve your machine by running things at lower temperatures (under 160•F), and keep an eye on iStat.
Oh, and tell us the problem when you know.

How do I check if my Macbook Pro support 802.11n?

I am thinking of upgrading my wireless router to 802.11n, but I don't know if my Macbook Pro's wireless card support this?
I bought my 15.4 inch Mac book pro in Nov 2007. Currently I am running on 10.5.8. Please kindly where to check my wireless card status.

Click here for information.
(47970)

AR9220 802.11an but no bgn?

Similar Messages

Maybe you are looking for