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.

Similar Messages

Ipad can't get maximum of 802.11n (40 Mhz channel, 300 Mbps)

Hi, Gens!
I have TP-Link 1043 with OpenWRT. My WiFi is 802.11n with 20 MHz width at 2,4 GHz and 40Mhz width at 5,2 MHz.
Encryption is WPA2 with AES
My laptop connects at follwoing RX/TX rates:
180.0 Mbit/s, MCS 12, 40MHz
270.0 Mbit/s, MCS 14, 40MHz
We can see everything goes fine and 40 MHz wide frequency rage is consumpted
At the same time, Ipad connect only at
24.0 Mbit/s, MCS 0, 20MHz
104.0 Mbit/s, MCS 13, 20MHz
And Iphone 5 - even worse - at
24.0 Mbit/s, MCS 0, 20MHz
52.0 Mbit/s, MCS 5, 20MHz
I looked a lot of discussions but I can not figure out what to do, to make my Iphone work fgaster than 65Mbits and Ipads - faster than 130Mbits... It is a maximum in my conditions and I dunno what to fix...

Hi deemona,
Everything appears to be normal on your wireless network. It all comes down to what WiFi standards each device supports. On 2.4GHz the iPhone 5 only supports a max of 72Mpbs (20MHz, 1 stream). The new iPad (mini/Air) supports a max of 150Mbps (20Mhz, 2 streams).
On 5GHz things change slightly where both the iPhone 5 and new iPads support 40Mhz channel bonding allowing each to support higher speeds, the iPhone 5 150Mbps and new iPads 300Mbps.
Hope this helps!
Brice

Anyone get a 300 Mbit link speed using 40 MHz (Channel-Bonding) on 802.11n?

I recently switched from a MacBook Pro 2.33 C2D 15 to a new MacBook Air 1.86 SSD... For some reason, one little persistent mystery that remains, is that I have been unable to get the Air to establish the link speed at 300 Mbit/s at 40 Mhz (Channel-Bonded). The best I can get is 270 Mbit/s, although my MacBook Pro consistently links at maximum. Signal quality is not an issue...
Anyone have an idea why? Can an Air owner out there confirm max link, or is this little gem incapable of 802.11n wide 300 Mbit/s?
Thanks to anyone who can shed light on this little puzzle...

Thanks for the reply.
First, you need your TC's 'Radio Mode' set to '802.11n only (5 Ghz)' - (I assume you do, since I don't think the 'Use wide channels' option should appear in any other mode...).
Now, the quick method to check Link Speed is in the 'Network Utility' Info tab...
Note that I don't have a major issue with my transfer rates, but do think it's an anomaly for a MacBook Pro to consistently link at 300 Mbit/s and my Air to refuse the same (max 270). In general, I would say that my Air exhibits (a bit) less sensitivity than the Pro with consistent wireless performance (i.e., I never had issues with the Pro acquiring and maintaining wireless links - the Air less so...).
Thanks for your help.

WRT160N with 40 MHz channel width?

Just purchased a WRT160N version 3. I had some connection issues and restricting the router to use 20 MHz channel width only and using channel 11 solved them. The router now works wonderfully. As soon as I allow the router to use 20 Mhz or 40 Mhz channel width my laptop with Intel 5100AGN wifi loses connection about 3 times a day. Why is this?? I would like to use 40 MHz as it allows for faster speeds.

Check this link.

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.

802.1x peap mschap v2 with MAC Filter + IP Address Permanent

Hi my name is Ivan, i have an issue
I have one cisco wlc 5508 with ios 7.4.100 with a ssid is working with 802.1x peap mschap v2 with mac filter, and I need configure in the web page of the WLC Security > Mac Filter, a MAC and one IP Address permanent to the users.
I have a service dhcp into the wlc to this profile.
This configuration works fine for 3 or 4 days. At the fifth day , my users renew the ip address, and they can not surfing to internet, because in my firewall i have a policy to the users with exactly ip address, for example.
MAC Filter - IP Address A - UserA
My policy say:
PolicyUserA - Internet
Please, i can establish an filter mac associate to one ip address permanent to one user, when service dhcp in the cisco wlc is active?
I possible to do it?.
How can i do it?

Hi Ivan,
You can not map the mac-ip address pairs on the WLC DHCP.
The WLC has a limited DHCP server functionalities. You better to use an external DHCP server with full functionalities and then you can configure the DHCP server to provide the same IP address everytime to each client in your network.
HTH
Amjad
Rating useful replies is more useful than saying "Thank you"

Troubleshoot Cisco Airlap 1242 with WLC 4400 Series LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response

I have a Problem with my new AIRLAP 1242 to connect with WLC 4400
after debug in my airlap it shows :
Reset done!
ethernet link up, 100 mbps, full-duplex
Ethernet port 0 initialized: link is up
Loading "flash:/c1240-k9w8-mx.123-7.JX8/c1240-k9w8-mx.123-7.JX8"...######################################################################################################################################################################################################################################
File "flash:/c1240-k9w8-mx.123-7.JX8/c1240-k9w8-mx.123-7.JX8" uncompressed and installed, entry point: 0x3000
executing...
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.3(7)JX8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Mon 19-Mar-07 01:42 by hqluong
Image text-base: 0x00003000, data-base: 0x004051E0
Initializing flashfs...
flashfs[1]: 9 files, 3 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 15998976
flashfs[1]: Bytes used: 5062144
flashfs[1]: Bytes available: 10936832
flashfs[1]: flashfs fsck took 4 seconds.
flashfs[1]: Initialization complete....done Initializing flashfs.
cisco AIR-LAP1242AG-E-K9   (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
Processor board ID FCW1411U0FZ
PowerPCElvis CPU at 266Mhz, revision number 0x0950
Last reset from power-on
1 FastEthernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 68:EF:BD:5F:9A:18
Part Number                          : 73-10256-07
PCA Assembly Number                  : 800-26918-06
PCA Revision Number                  : A0
PCB Serial Number                    : FOC14093XU3
Top Assembly Part Number             : 800-29152-03
Top Assembly Serial Number           : FCW1411U0FZ
Top Revision Number                  : A0
Product/Model Number                 : AIR-LAP1242AG-E-K9
Press RETURN to get started!
*Mar 1 00:00:05.608: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:06.858: %DOT11-2-VERSION_INVALID: Interface Dot11Radio0, unable to find required radio version 581.18
*Mar 1 00:00:06.858: Interface Dot11Radio0, Accepting as a test version of radio firmware
*Mar 1 00:00:06.878: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:07.234: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:08.212: %DOT11-2-VERSION_INVALID: Interface Dot11Radio1, unable to find required radio version 581.18
*Mar 1 00:00:08.212: Interface Dot11Radio1, Accepting as a test version of radio firmware
*Mar 1 00:00:08.232: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:09.278: %SYS-6-LOGGERSTART: Logger process started
*Mar 1 00:00:09.326: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.3(7)JX8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Mon 19-Mar-07 01:42 by hqluong
*Mar 1 00:00:09.332: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power source
*Mar 1 00:00:09.388: %DOT11-6-FREQ_SCAN: Interface Dot11Radio0, Scanning frequencies for 32 seconds
*Mar 1 00:00:10.271: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:10.332: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:10.332: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:11.271: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:28.331: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:28.361: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2462 selected
*Mar 1 00:00:28.362: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 1 00:00:28.363: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:28.369: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5260 selected
*Mar 1 00:00:28.372: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:28.398: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:28.399: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:28.465: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:29.398: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:00:29.465: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
Translating "CISCO-LWAPP-CONTROLLER.ekahospital.com"...domain server (202.134.0.155)
*Mar 1 00:00:38.351: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 172.31.xxx.xxx, mask 255.255.255.0, hostname AP68ef.bd5f.9a18
*Mar 1 00:00:38.820: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2417 selected
*Mar 1 00:00:38.827: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5200 selected (203.130.196.5)
*Mar 1 00:00:49.835: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2422 selected
*Mar 1 00:00:49.842: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5220 selected
*Mar 1 00:00:49.851: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:49.852: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:00:49.852: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Mar 1 00:00:50.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:50.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Sep 18 07:02:25.504: %LWAPP-5-CHANGED: LWAPP changed state to CFG
*Sep 18 07:02:29.288: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.MYDOMAIN.com
*Sep 18 07:02:30.504: LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response
*Sep 18 07:02:30.551: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET CONFIG RESPONSE.
*Sep 18 07:02:30.551: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.
flashfs[0]: 9 files, 3 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 15998976
flashfs[0]: Bytes used: 5062144
flashfs[0]: Bytes available: 10936832
flashfs[0]: flashfs fsck took 26 seconds.
Base ethernet MAC Address: 68:ef:bd:5f:9a:18
Initializing ethernet port 0...
Reset ethernet port 0...
Reset done!
and after that i check in my WLC that shows
AP with Base Radio MAC xx:xx:xx:xx:xx:xx (APxxxx.xxxx.xxxx) is unable to associate.
The reulatory domain configured on it '-e' does not match the controller's country
code: USA
i found that the problem about the region.
question :
1. is it possible to change the region in AIRLAP 1242 or in WLC?
2. if possible how to change it?
INFO :
my first AIRLAP Product/Model Number : AIR-LAP1242AG-A-K9 and my new AIRLAP Product/Model Number : AIR-LAP1242AG-E-K9

WLC GUI >> Wireless >> Country >> Select the country.
Regards
Surendra

Client get connected occationally with WLC 5508

Hi ,
I have one strange problem on wireless connection.
I just upgraded several 1131 APs to LAP with 2 new Cisco 5508 controller deployed, and we found the clients sometime can get conneted to the 1131 AP, and connection well, sometimes cannot. during our test, one conecion is ok, next one cannot, the third one seems ok again and again.
And we also have 2 new 1140 APs, seems no such problem,
The version for controller is 6.0.196.0, and Client is Lenevo PC with XP.
Any suggestion? or some troubleshooting procedure I can follow?
Thanks!
Roy

Thanks!
Seems some problem with open authentication.
On the Client, it reported cannot get associated.
on the WLC, while I am debug client it reports:
*Jul 14 10:18:51.844: 00:1f:3c:c2:e9:71 Sending Assoc Response to station on BSSID c4:7d:4f:47:a5:c0 (status 12)
*Jul 14 10:18:51.889: 00:1f:3c:c2:e9:71 Ignoring 802.11 assoc request from mobile pending deletion
*Jul 14 10:18:51.889: 00:1f:3c:c2:e9:71 Sending Assoc Response to station on BSSID c4:7d:4f:47:a5:c0 (status 12)
*Jul 14 10:18:51.928: 00:1f:3c:c2:e9:71 Ignoring 802.11 assoc request from mobile pending deletion
*Jul 14 10:18:51.928: 00:1f:3c:c2:e9:71 Sending Assoc Response to station on BSSID c4:7d:4f:47:ae:b0 (status 12)
*Jul 14 10:18:52.446: 00:1f:3c:c2:e9:71 apfMsExpireCallback (apf_ms.c:418) Expiring Mobile!
*Jul 14 10:18:52.446: 00:1f:3c:c2:e9:71 apfMsExpireMobileStation (apf_ms.c:4427) Changing state for mobile 00:1f:3c:c2:e9:71 on AP c4:7d:4f:47:ae:b0 from Associated to Disassociated
I am using remote radius with WLC only.
The strange thing is, when get connected, it looks fine, but I tried disconnect manually, then connect again, it reported cannot get associated, then I try again, it can get connect again,....

Several DAQmx Channels with Start and Clear Task VI's

Hi,
I'm trying to read in several DAQmx channels in a while loop. When I just place the channels within the while loop and connect them directly to the read VI's, everything is fine. But I read in the help, that this will slow down my system, because it's opening and closing the task each cycle. So I used Start Task and Clear Task VI's to open and clear them before and after the loop. But now it's only reading one of my channels in, although I wired all of them in exactly the same manner. Anyone has an idea, what I did wrong?
Thanks,
Miclas
Attachments:
Save&Stop DAQ.JPG ‏87 KB

You would have seen the error if you had wired up and error indicator.
You cannot run multiple tasks of the same type (i.e. an analog input) at the same time. What you read about stopping and closing tasks is correct but it was the only way your program could work. What you don't realize is that you can have multiple channels with a single task. If you used a physical channel constant, it would be something like 'dev1/ai0:2' if you had consecutive channels or 'dev1/ai0, dev1/ai2' for non-consecutive. Global channels are done in a similar fashion. You would have 'FSR1, FSR2, Knee Angle', etc.

VIEW won't display channels with same names

Hello,
We have recently installed DIAdem 2010 and are beginning to find channel name problems that we didn't have before with 9.1.
Traditionally we have always set the name-oriented channel references to 'only channel name' and we have never had any problems when displaying multiple traces in VIEW. Now, we find that when we display more than one trace in VIEW with channel names that are repeated we get problems with the axis system display dialogue box. This dialogue box tells me that the X and Y channel names AND NUMBERS are the same for all three traces when in fact the data displayed is different. If I try and change one of the channels it immediately reverts back to the first channel with that name.
I have attached a screen dump to help explain. The image shows a VIEW window with three speed time histories from three separate data files that have been loaded together. The three X channels will all be named 'time' but will be channel numbers 1, 4 and 7. The Y channnels are all 'speed km\h' and are numbered 2, 5 and 8. However, the dialogue box shows that all three traces are made from channels 1 and 2 despite the three traces appearing different. If I change one of the 'time' channels from number 1 to, say, number 4, then it reverts back to number 1 as soon as I move the focus to somewhere else in the box. Version 9.1 never had this problem.
If I swith the name-oriented channel references to '[group index]/channel name' then the problem goes away - even thought the data displayed in the graph is the same!
I'm not entirely clear on the reasons for settling on 'name only' references - probably historical - but I am even less clear on the effect of switching to '[group index]/channel name', particularly with the many autosequences that we use.
Is this a bug that can be fixed?
Regards, Si.
Attachments:
VIEW.jpg ‏236 KB

Simon,
The DataFinder is a database that DIAdem installs that integrates directly into the NAVIGATOR, so that you can easily query data files/groups/channels or compile properties from multiple files into correlated curves on a graph, etc. You might be interested in the ability to look inside your data files in the NAVIGATOR to see the group/channel structure and their properties. This is particularly interesting if you wan to load selected groups/channels from one or more files.
Here are the feature description files,
Brad Turpin
DIAdem Product Support Engineer
National Instruments
Attachments:
New Features from DIAdem 9.1 to 2010.zip ‏69 KB

RpcOut: couldn't open channel with RPCI protocol

callservicesd and soagent using very CPU and memory.
in console, I get the error message as "RpcOut: couldn't open channel with RPCI protocol"
Lots of these error messages logged
(com.apple.imdmessageservices.IMDMessageServicesAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
(com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
Some issue with messages app and Skype app - when I launch them - they get to hung state.
PRAM reset, reboot in safe mode, restore from back up before this started and ran check disk using utilities - all tried.
Still the problem continues.
Fan spins and continues till the laptop is shutdown.
Hardware Overview:
Model Name: MacBook Air
Model Identifier: MacBookAir5,2
Processor Name: Intel Core i7
Processor Speed: 2 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB
Boot ROM Version: MBA51.00EF.B02
SMC Version (system): 2.5f9
Serial Number (system): C02J74FPDRVG
Hardware UUID: 6A4E07EC-B46D-5AF8-BD8F-F6554AAF7AC0
Hardware Overview:

I don't get anything with mccon in the search
Below is all the logs in the console. Let me know if this helps.
4/18/15 9:00:15.956 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 9:00:27.640 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 9:00:28.265 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 9:00:32.159 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[1912]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
4/18/15 9:00:39.621 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 9:00:51.772 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 9:00:52.378 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 9:01:00.555 PM com.apple.xpc.launchd[1]: (com.apple.AddressBook.abd) Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
4/18/15 9:01:17.583 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:01:44.006 PM com.apple.xpc.launchd[1]: assertion failed: 14D136: launchd + 163781 [7F885D63-B284-3471-B6E3-172489232C37]: 0xe
4/18/15 10:01:44.006 PM com.apple.xpc.launchd[1]: assertion failed: 14D136: launchd + 163781 [7F885D63-B284-3471-B6E3-172489232C37]: 0xe
4/18/15 10:01:49.896 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:01:55.400 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:01:55.949 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:01:59.350 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:01:59.389 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:01:59.871 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:02:00.360 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:02:08.803 PM com.apple.xpc.launchd[1]: (com.apple.AddressBook.abd) Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
4/18/15 10:02:15.418 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:02:32.070 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:02:44.786 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:02:45.537 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:02:56.379 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:03:07.791 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:03:08.501 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:03:18.117 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:03:39.431 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:04:01.349 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:04:15.925 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:04:16.437 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:04:24.106 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:04:37.842 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:04:38.326 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:04:46.050 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:05:07.269 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:05:28.475 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:05:42.116 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:05:42.588 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:05:50.333 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:06:11.496 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:06:33.236 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:06:40.766 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:06:46.857 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:06:47.325 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:06:55.009 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:07:08.683 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:07:09.171 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:07:17.058 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:07:38.272 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:07:59.502 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:08:13.195 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:08:13.725 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
4/18/15 10:08:28.088 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

Can I playback in both channels with my audio interface?

From what I've found so far I'm afraid the answer is already "no" but I have to ask for myself.
When I record into QuickTime movie (not Pro) using my Alesis IO|14 Firewire interface, it only plays back on the left channel.
Is there ANY way to get it to play back on both channels? (Or is this a sneaky way of urging us to upgrade to QT Pro?)
I'm assuming the audio quality of my M-Audio Nova condenser mic is better than my iMac's built-in mic, which is why I'd really like to do this. I don't even need true stereo, just both channels playing back.
(QT 10.1, on Lion)
Thanks.

The mic and interface record just fine into GarageBand, either as stereo or mono, and plays back out of both channels with the same setup, so I think the problem is with QT.
I don't find any kind of switch like that in the Hardware Direct Monitoring software for the Alesis, but I'll investigate further.
As I mentioned, I've searched this and other forums and it seems like this is just how QT is set up. But I was hoping for some sort of solution.
As previously indicated, I am not familiar with your IO device, so let me ask a few questions here.
1) Is the Nova mic you mentioned mono or stereo?
2) If mono, are you using two of them?
3) If mono and you are not using a pair of mics, does the input interface hardware have the ability to blend left and right (mic 1 and mic 2) input channels?
4) If mono, you are not using a pair of mics, and the device has no ability to blend left and right channels, are you you using an adapter cable to input a split signal to both input channels of the device?
If you are using a mono mic to input a signal to only one channel of the input device and are not/cannot blend this signal to both channels before output via the Firewire cable, then its sounds like your system is working normally and correctly. Basically, the Firewire audio is sent to the QT app as received from the Firewire device and recorded as is in stereo. I.e., if the left channel is active with the mic signal and the right channel is empty, then the audio is recorded only to the left channel and the right channel records the "nil" signal/nothing. On the other hand, GarageBand is an audio editor designed specifically to blend, pan, duck, filter, and/or otherwise taylor audio content as desired by the user. (I.e., which includes the ability to re-channel a single mono audio channel to both channels of a stereo track during the recording process which the QT app can't do.) In short, both apps are doing what they are designed to do as they were designed to do it. As such and as previously noted you have three basic options here.
1) You force the IO device to send stereo or two-channel mono audio to your Mac by using two separate mics, use a single stereo mic with dual channel audio output, using an adapter cable to split the single mono mic audio output line into two separate lines to be plugged into both channels of your IO device, or you can apply/blend the active channel to left and right Firewire output channels within the device if it has this capability.
2) You can use GarageBand to do create and export audio recordings instead of the QT app, or
3) You can purchase QT 7 Pro in order to fix your left channel problem post recording by simply applying the left channel audio to both left and right channels within the audio track so it will play as you want in any media player on your computer.
(Actually, there is a fourth option if you are using an external amplifier for playback, which is to simply use the output amplifier to accomplish re-channelization during playback rather than actually fixing the media file with QT 7 Pro.)

Connecting Cisco AIR-CAP2602E over WAN with WLC - Procedural Details

Hi,
I have a Wireless LAN Controller Installed in one of the subnets where some AIR-CAP2602E's are connected with the WLC. WLC acts as DHCP for the AIR-CAP2602E Devices.
I have additional AIR-CAP2602E access-points at other location (Subnet) and Need to connect them with WLC.
Challange faced by me is creating DHCP on Cisco 2950 (L2) or 3750 (L3) with DHCP option 43. Can any one has detailed configuration of enabling DHCP for specific VLAN on Cisco L2 and L3 Devices.

If you have control of the DNS environment for these network segments, just make an entry for :
cisco-lwapp-controller aliases cisco-capwap-controller (IP list) as the CAP will hunt for those two name sets.
My WLC provides DHCP support only to the wlans supported by the AP but not the AP it self..
hope this helps

Could not establish trust relationship for the SSL/TLS secure channel with authority

Hello everyone, I need to establish a connection between my HTTPS WCF hosted in Windows Azure Web Role and my Windows Store App Client. The service is actually exposed for testing purposes using a self-signed certificate.
I have installed the certificate in Personal and Trusted Root Certification Authorities in Current User and Local Manchine.
In the Windows Store App, I create the service reference pointing to the cloud https service, then edit the manifest and create a new declaration to Add a New Certificate, I checked Exclusive Trust and Auto select, pointing to Root storage name and
my self-signed certificate.cer.
The result is the following exception in the IntelliTrace stack:
Exception:Caught: "The remote certificate is invalid according to the validation procedure." (System.Security.Authentication.AuthenticationException)
A System.Security.Authentication.AuthenticationException was caught: "The remote certificate is invalid according to the validation procedure."
Time: 19/01/2015 04:42:33 p. m.
Thread:Worker Thread[17080]
Exception:Thrown: "Could not establish trust relationship for the SSL/TLS secure channel with authority 'appchallengewhi.cloudapp.net'." (System.ServiceModel.Security.SecurityNegotiationException)
A System.ServiceModel.Security.SecurityNegotiationException was thrown: "Could not establish trust relationship for the SSL/TLS secure channel with authority 'appchallengewhi.cloudapp.net'."
Time: 19/01/2015 04:42:34 p. m.
Thread:Worker Thread[17080]
Appreciate any help, to solve this with the approach of WCF Service Reference in Windows Store App.
Note:
If I call the HTTPS service using a Console App it works very good using the following the code:
ChannelFactory<IAgentService> factory = new ChannelFactory<IAgentService>("basicHttpBinding_IAgentService");
ServicePointManager.ServerCertificateValidationCallback = (sender, cert, chain, error) => true;
IAgentService wcfProxy = factory.CreateChannel();
Thanks in advance,
RC

Maybe not implemented.
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/2dab2818-8f4c-4474-a7a1-db2cbfb40d40/accepting-client-certificate-for-https-connections?forum=winappswithcsharp

Could not establish trust relationship for the SSL/TLS secure channel with authority SharePoint ssis connectors

Hi All,
I am using SharePoint List Connectors to load the data from Sharepoint list to Sql server.
I have created an ssis package and attached to the SQL agent job in works fine
SharePoint Source dev url : http://company.dev.com (working fine)(http)
DB server:(server\instance)
I thought all i good and can test with the uat sharepoint url.
I have changed the configuration url yo point to uat.(https)
SharePoint Source dev url : https://companyuat.dev.com (working fine)
DB server:(server\instance)
Suddently it fails when with the following error:
In both the cases i am running the agent job from the same db server
DB server:(server\instance)
Error Message:
Could not establish trust relationship for the SSL/TLS secure channel with authority 'companyuat.dev.com'. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
Source: Data Flow Task SharePoint List Source [1] Description: System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure channel with authority 'companyuat.dev.com'. ---> System.Net.WebException:
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
Is there is workaround to reslove this?Any inputs highly appreciated as it is time to move to production :(.
Thanks
Ravi
Ravi

This is the important error: The remote certificate is invalid according to the validation procedure.
Your SharePoint server certificate is invalid. You have to either correct your certificate or make your SSIS client machine explicitly trust the server certificate.
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

802.11an 40 Mhz channels with WLC (7.4)

Similar Messages

Maybe you are looking for