ath9k 9380: All 5Ghz channels flagged as passive-scanning

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

Any idea why this is happening?

On a previous boot, I had an STA associated on channel 40 and that was the single 5Ghz channel that didn't show 'passive scanning'.  I removed it's configuration so that it wouldn't associate and upon reboot I see the output below.

More than happy to provide more details...

[root@lec-ath9k-9380 ~]# iw phy wiphy0 info
Wiphy wiphy0
       Band 1:
               Capabilities: 0x11ef
                       RX LDPC
                       HT20/HT40
                       SM Power Save disabled
                       RX HT20 SGI
                       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-23 Frequencies:
                       * 2412 MHz [1] (17.0 dBm)
                       * 2417 MHz [2] (17.0 dBm)
                       * 2422 MHz [3] (17.0 dBm)
                       * 2427 MHz [4] (17.0 dBm)
                       * 2432 MHz [5] (17.0 dBm)
                       * 2437 MHz [6] (17.0 dBm)
                       * 2442 MHz [7] (17.0 dBm)
                       * 2447 MHz [8] (17.0 dBm)
                       * 2452 MHz [9] (17.0 dBm)
                       * 2457 MHz [10] (17.0 dBm)
                       * 2462 MHz [11] (17.0 dBm)
                       * 2467 MHz [12] (17.0 dBm) (passive scanning)
                       * 2472 MHz [13] (17.0 dBm) (passive scanning)
                       * 2484 MHz [14] (disabled)
               Bitrates (non-HT):
                       * 1.0 Mbps
                       * 2.0 Mbps (short preamble supported)
                       * 5.5 Mbps (short preamble supported)
                       * 11.0 Mbps (short preamble supported)
                       * 6.0 Mbps
                       * 9.0 Mbps
                       * 12.0 Mbps
                       * 18.0 Mbps
                       * 24.0 Mbps
                       * 36.0 Mbps
                       * 48.0 Mbps
                       * 54.0 Mbps
       Band 2:
               Capabilities: 0x11ef
                       RX LDPC
                       HT20/HT40
                       SM Power Save disabled
                       RX HT20 SGI
                       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-23 Frequencies:
                       * 5180 MHz [36] (18.0 dBm) (passive scanning, no IBSS)
                       * 5200 MHz [40] (18.0 dBm) (passive scanning, no IBSS)
                       * 5220 MHz [44] (18.0 dBm) (passive scanning, no IBSS)
                       * 5240 MHz [48] (18.0 dBm) (passive scanning, no IBSS)
                       * 5260 MHz [52] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5280 MHz [56] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5300 MHz [60] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5320 MHz [64] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5500 MHz [100] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5520 MHz [104] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5540 MHz [108] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5560 MHz [112] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5580 MHz [116] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5600 MHz [120] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5620 MHz [124] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5640 MHz [128] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5660 MHz [132] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5680 MHz [136] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5700 MHz [140] (18.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5745 MHz [149] (18.0 dBm) (passive scanning, no IBSS)
                       * 5765 MHz [153] (18.0 dBm) (passive scanning, no IBSS)
                       * 5785 MHz [157] (18.0 dBm) (passive scanning, no IBSS)
                       * 5805 MHz [161] (18.0 dBm) (passive scanning, no IBSS)
                       * 5825 MHz [165] (18.0 dBm) (passive scanning, no IBSS)
               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: 2257 bytes
       Coverage class: 0 (up to 0m)
       Available Antennas: TX 0 RX 0
       Supported interface modes:
                * IBSS
                * managed
                * AP
                * AP/VLAN
                * WDS
                * monitor
                * mesh point
                * P2P-client
                * P2P-GO
       Supported commands:
                * new_interface
                * set_interface
                * new_key
                * new_beacon
                * new_station
                * new_mpath
                * set_mesh_params
                * set_bss
                * authenticate
                * associate
                * deauthenticate
                * disassociate
                * join_ibss
                * join_mesh
                * remain_on_channel
                * set_tx_bitrate_mask
                * action
                * frame_wait_cancel
                * set_wiphy_netns
                * set_channel
                * set_wds_peer
                * connect
                * disconnect
       Supported TX frame types:
                * IBSS: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                * managed: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                * AP: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                * AP/VLAN: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                * mesh point: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                * P2P-client: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                * P2P-GO: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0 Supported RX frame types:
                * IBSS: 0x00d0
                * managed: 0x0040 0x00d0
                * AP: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0
                * AP/VLAN: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0
                * mesh point: 0x00b0 0x00c0 0x00d0
                * P2P-client: 0x0040 0x00d0
                * P2P-GO: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0

--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Quoted 4 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Quoted 1 line

Any idea why this is happening?

don't know, may be regulatory.

Quoted 9 lines · Mohammed Shafi

Quoted 4 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 3 lines

Quoted 1 line

Any idea why this is happening?

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

What a pain.

Ben

Quoted 16 lines · Ben Greear

Quoted 9 lines · Mohammed Shafi

Quoted 4 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!

Quoted 49 lines · Ben Greear

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)

cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Quoted 3 lines

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!

Its what the card was designed and programmed for. The only thing you can do with world roaming cards then is just scan, and if you find a beacon on a channel which is a non-DFS channel beaconing will be enabled then.

Luis

Makes it basically useless as a 5Ghz AP though, eh?

Guess it's time to go find a hack to over-ride eeprom settings :(

Quoted 1 line · Ben Greear

Makes it basically useless as a 5Ghz AP though, eh?

Um yup. The card is a world roaming card... not an AP card. For AP mode of functionality vendors have to go through a regulatory test specific to 3 regions, and depending on which region they get certification for they will have then programmed in the values required for regulatory on the CTLs. The EEPROM would be configured for the region the card was being tested for.

Quoted 2 lines

Guess it's time to go find a hack to over-ride eeprom settings :(

Good luck with support from anyone for any further questions ;) [1].

The real solution to these issues is for regulatory agencies to start warming up to the idea about dynamic regulatory selection but for this you will also then need to ensure each card gets properly tested for each regulatory region -- or we'd have to restrict the card to work in

Quoted 4 lines · Luis R. Rodriguez

Quoted 1 line · Ben Greear

Quoted 8 lines

Quoted 1 line

Makes it basically useless as a 5Ghz AP though, eh?

Um yup. The card is a world roaming card... not an AP card. For AP mode of functionality vendors have to go through a regulatory test specific to 3 regions, and depending on which region they get certification for they will have then programmed in the values required for regulatory on the CTLs. The EEPROM would be configured for the region the card was being tested for.

Well, if you have an AP on a 5Ghz channel, and associate a station interface, that one channel becomes
usable, and then you can start hostapd, as far as I can tell. You just can't use an un-used channel, which is of course a pain if you want to do some 5Ghz AP testing on a clean channel!

Quoted 4 lines

Quoted 2 lines

Guess it's time to go find a hack to over-ride eeprom settings :(

Good luck with support from anyone for any further questions ;) [1].

I can certainly disable the module parameter and have it bug for bug compatible with upstream code.  I'm not going to
write to the eeprom or anything funny like that.

Quoted 4 lines

The real solution to these issues is for regulatory agencies to start warming up to the idea about dynamic regulatory selection but for this you will also then need to ensure each card gets properly tested for each regulatory region -- or we'd have to restrict the card to work in

What kinds of things could fail in one region and not another?

 Are there any known regions of the world where the AR9380 actually fails to function in any mode?

Quoted 14 lines · Ben Greear

Quoted 4 lines · Luis R. Rodriguez

Quoted 1 line · Ben Greear

Quoted 8 lines

Quoted 1 line

Makes it basically useless as a 5Ghz AP though, eh?

Um yup. The card is a world roaming card... not an AP card. For AP mode of functionality vendors have to go through a regulatory test specific to 3 regions, and depending on which region they get certification for they will have then programmed in the values required for regulatory on the CTLs. The EEPROM would be configured for the region the card was being tested for.

Quoted 6 lines

Well, if you have an AP on a 5Ghz channel, and associate a station interface, that one channel becomes
usable, and then you can start hostapd, as far as I can tell. You just can't use an un-used channel, which is of course a pain if you want to do some 5Ghz AP testing on a clean channel!

You don't even need to associate, you just need to scan, that's it. It is a pain to test AP functionality but that is not how vendors test AP functionality -- remember you are using a world roaming card, the fact that you can even get away with beaconing modes of operation on some channels is actually a feature.

The issue here comes from the fact that people think using AP mode of functionality is a freedom they are entitled to with any 802.11 card on any channel. Its obviously more complicated than that and figuring out a proper way to do this is part of our own effort to enable APs with Linux properly and in a regulatory compliant manner.

Quoted 7 lines

Quoted 4 lines

The real solution to these issues is for regulatory agencies to start warming up to the idea about dynamic regulatory selection but for this you will also then need to ensure each card gets properly tested for each regulatory region -- or we'd have to restrict the card to work in

What kinds of things could fail in one region and not another?

Atheros cards are optimized to output as much power in the middle area of a spectrum, towards the ends of the spectrum regulatory agencies sometimes require a bit tighter power constraints and cards are required to meet certain power curve constraints. This is one of the reasons for the EEPROM CTLs on the Atheros cards. This is one example of such considerations.

Quoted 2 lines

Are there any known regions of the world where
the AR9380 actually fails to function in any mode?

Huh? AR9380 will work in any region so long as its tested for that region and the CTLs get programmed as such.

Quoted 31 lines · Luis R. Rodriguez

Quoted 15 lines · Ben Greear

Quoted 4 lines · Luis R. Rodriguez

Quoted 1 line · Ben Greear

Quoted 8 lines

Quoted 1 line

Makes it basically useless as a 5Ghz AP though, eh?

Um yup. The card is a world roaming card... not an AP card. For AP mode of functionality vendors have to go through a regulatory test specific to 3 regions, and depending on which region they get certification for they will have then programmed in the values required for regulatory on the CTLs. The EEPROM would be configured for the region the card was being tested for.

Quoted 6 lines

Well, if you have an AP on a 5Ghz channel, and associate a station interface, that one channel becomes
usable, and then you can start hostapd, as far as I can tell. You just can't use an un-used channel, which is of course a pain if you want to do some 5Ghz AP testing on a clean channel!

You don't even need to associate, you just need to scan, that's it. It is a pain to test AP functionality but that is not how vendors test AP functionality -- remember you are using a world roaming card, the fact that you can even get away with beaconing modes of operation on some channels is actually a feature.

Quoted 5 lines

The issue here comes from the fact that people think using AP mode of functionality is a freedom they are entitled to with any 802.11 card on any channel. Its obviously more complicated than that and figuring out a proper way to do this is part of our own effort to enable APs with Linux properly and in a regulatory compliant manner.

Do you know of any 3x3 AR9380 NICs that can be used as 5Ghz APs w/out regdomain hacks?

Sparklan was the only NIC I found, and
I didn't notice any way to order a specific regdomain on the NIC.

Quoted 18 lines

Quoted 7 lines

Quoted 4 lines

The real solution to these issues is for regulatory agencies to start warming up to the idea about dynamic regulatory selection but for this you will also then need to ensure each card gets properly tested for each regulatory region -- or we'd have to restrict the card to work in

What kinds of things could fail in one region and not another?

Atheros cards are optimized to output as much power in the middle area of a spectrum, towards the ends of the spectrum regulatory agencies sometimes require a bit tighter power constraints and cards are required to meet certain power curve constraints. This is one of the reasons for the EEPROM CTLs on the Atheros cards. This is one example of such considerations.

Quoted 2 lines

 Are there any known regions of the world where the AR9380 actually fails to function in any mode?

Quoted 2 lines

Huh? AR9380 will work in any region so long as its tested for that region and the CTLs get programmed as such.

Testing doesn't make something work, it just makes sure that it does work.  Now, programming the CTLs sounds like something important. Is there any way to tell if a NIC is properly programmed for a particular region, or is each brand/revision programmed independently?

Since it *is* possible to start an AP on a channel with existing AP, I assume that the NIC must be able to handle this properly..or is that ability to start on a scanned channel just a bug?  (Please don't fix it, if it is :P)

Quoted 4 lines · Ben Greear

Since it *is* possible to start an AP on a channel with existing AP, I assume that the NIC must be able to handle this properly..or is that ability to start on a scanned channel just a bug? (Please don't fix it, if it is :P)

It a feature, AP functionality is allowed on that channel on a world roaming card given that no CTL is present so the lower regulatory value, from CRDA, is used instead of the CTL value.

Quoted 9 lines · Luis R. Rodriguez

Quoted 4 lines · Ben Greear

Since it *is* possible to start an AP on a channel with existing AP, I assume that the NIC must be able to handle this properly..or is that ability to start on a scanned channel just a bug?  (Please don't fix it, if it is :P)

Quoted 3 lines

It a feature, AP functionality is allowed on that channel on a world roaming card given that no CTL is present so the lower regulatory value, from CRDA, is used instead of the CTL value.

So as long as you have a functional CRDA and do not mis-represent your country with 'iw reg set',

is there any way to
actually get the system out of spec if you use "eeprom" reg-domain of 0x0?

No. You can only do this by trying to take the card out of compliance purposely or unknowingly in software.

Quoted 2 lines · Luis R. Rodriguez

No. You can only do this by trying to take the card out of compliance purposely or unknowingly in software.

Oh and my point was that "regulatory hacks" fit this description.

Quoted 4 lines · Luis R. Rodriguez

On Mon, May 23, 2011 at 2:42 PM, Luis R. Rodriguez<[email protected]> wrote:

Quoted 4 lines

Quoted 2 lines

No. You can only do this by trying to take the card out of compliance purposely or unknowingly in software.

Oh and my point was that "regulatory hacks" fit this description.

Ok.  I believe you are right in general, but I can't see how enabling a device to work on a non-scanned channel can break something,

if it is perfectly legal and appropriate for there to be an AP on that scanned channel.

In other words, if I change my Netgear to be on channel
48, scanned it, and then created a VAP on that channel, that is OK with un-hacked regdomain stuff, but if instead I change regdomain to 0x0 and use channel 48 without re-configuring my Netgear, somehow that suddenly causes issues?

At any rate, all I really wanted to do was tie-break an off the shelf AP that appeared to cause ath9k clients to silently be unable to ARP after a while.  I have something that appears functional now, so back to real work.

Quoted 8 lines · Ben Greear

Quoted 7 lines · Luis R. Rodriguez

Quoted 2 lines · Luis R. Rodriguez

No. You can only do this by trying to take the card out of compliance purposely or unknowingly in software.

Quoted 4 lines

Quoted 1 line

Oh and my point was that "regulatory hacks" fit this description.

Ok. I believe you are right in general, but I can't see how enabling a device to work on a non-scanned channel can break something,

If a card is world roaming, how else on earth without seeing a beacon will you know if you can initiate radiation on that channel?

Quoted 2 lines

if it is perfectly legal and appropriate for there to be an AP on that scanned channel.

Agreed! In fact I'd go so far as to say that if you have multiple 802.11 cards they should be able to share the same beacon hints, and in fact -- this is what cfg80211 does ;)

Quoted 5 lines

In other words, if I change my Netgear to be on channel
48, scanned it, and then created a VAP on that channel, that is OK with un-hacked regdomain stuff, but if instead I change regdomain to 0x0 and use channel 48 without re-configuring my Netgear, somehow that suddenly causes issues?

For Atheros EEPROM 0x0 is designed for usage for the US:

Quoted 12 lines · Luis R. Rodriguez

Quoted 9 lines · Ben Greear

Quoted 7 lines · Luis R. Rodriguez

Quoted 2 lines · Luis R. Rodriguez

No. You can only do this by trying to take the card out of compliance purposely or unknowingly in software.

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

Oh and my point was that "regulatory hacks" fit this description.

Ok.  I believe you are right in general, but I can't see how enabling a device to work on a non-scanned channel can break something,

If a card is world roaming, how else on earth without seeing a beacon will you know if you can initiate radiation on that channel?

I have a strong personal sense of location, and I'm 100% sure that I'm in the US.  So, the the computer could listen to it's human and just trust that I know WTF I am asking for!

It may currently be impossible for vendors to explicitly support this due to regulatory domains that assume users are evil and/or stupid and not to be trusted to know their current location, but please don't pretend that receiving a beacon is rock solid evidence of a channel's availability:  It only means that someone else that set up the AP thinks it's available for use.

Quoted 13 lines

Quoted 2 lines

if it is perfectly legal and appropriate for there to be an AP on that scanned channel.

Agreed! In fact I'd go so far as to say that if you have multiple 802.11 cards they should be able to share the same beacon hints, and in fact -- this is what cfg80211 does ;)

Quoted 5 lines

In other words, if I change my Netgear to be on channel
48, scanned it, and then created a VAP on that channel, that is OK with un-hacked regdomain stuff, but if instead I change regdomain to 0x0 and use channel 48 without re-configuring my Netgear, somehow that suddenly causes issues?

Quoted 1 line

For Atheros EEPROM 0x0 is designed for usage for the US:

Good..that's all I really wanted:  My NIC to support my location w/out undue complaint or limitations.

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

Quoted 49 lines · Ben Greear

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Quoted 8 lines

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

Strange.  This is what I get out of my WPEA-127N:

ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a

Here's how my 5GHz channels look:
               Frequencies:
                       * 5180 MHz [36] (17.0 dBm)
                       * 5200 MHz [40] (17.0 dBm)
                       * 5220 MHz [44] (17.0 dBm)
                       * 5240 MHz [48] (17.0 dBm)
                       * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5600 MHz [120] (disabled)
                       * 5620 MHz [124] (disabled)
                       * 5640 MHz [128] (disabled)
                       * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5745 MHz [149] (30.0 dBm)
                       * 5765 MHz [153] (30.0 dBm)
                       * 5785 MHz [157] (30.0 dBm)
                       * 5805 MHz [161] (30.0 dBm)
                       * 5825 MHz [165] (30.0 dBm)

This is running 2.6.37 with compat-wireless from sometime in March, probably.  I'll try with 2.6.39 and latest compat-wireless when I get a chance.

Quoted 96 lines · Brian Prodoehl

Quoted 49 lines · Ben Greear

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Quoted 8 lines

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

Strange.  This is what I get out of my WPEA-127N:

ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a

Here's how my 5GHz channels look:
               Frequencies:
                       * 5180 MHz [36] (17.0 dBm)
                       * 5200 MHz [40] (17.0 dBm)
                       * 5220 MHz [44] (17.0 dBm)
                       * 5240 MHz [48] (17.0 dBm)
                       * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5600 MHz [120] (disabled)
                       * 5620 MHz [124] (disabled)
                       * 5640 MHz [128] (disabled)
                       * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5745 MHz [149] (30.0 dBm)
                       * 5765 MHz [153] (30.0 dBm)
                       * 5785 MHz [157] (30.0 dBm)
                       * 5805 MHz [161] (30.0 dBm)
                       * 5825 MHz [165] (30.0 dBm)

Quoted 3 lines

This is running 2.6.37 with compat-wireless from sometime in March, probably.  I'll try with 2.6.39 and latest compat-wireless when I get a chance.

What's the problem? You ahve DFS requirements on the channels listed with DFS. You can initiate radiation on the others. We lack master support for DFS yet so you cannot initiate radiation on those channels.

 Luis

Quoted 106 lines · Luis R. Rodriguez

Quoted 96 lines · Brian Prodoehl

Quoted 49 lines · Ben Greear

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Quoted 8 lines

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

Strange.  This is what I get out of my WPEA-127N:

ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a

Here's how my 5GHz channels look:
               Frequencies:
                       * 5180 MHz [36] (17.0 dBm)
                       * 5200 MHz [40] (17.0 dBm)
                       * 5220 MHz [44] (17.0 dBm)
                       * 5240 MHz [48] (17.0 dBm)
                       * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5600 MHz [120] (disabled)
                       * 5620 MHz [124] (disabled)
                       * 5640 MHz [128] (disabled)
                       * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5745 MHz [149] (30.0 dBm)
                       * 5765 MHz [153] (30.0 dBm)
                       * 5785 MHz [157] (30.0 dBm)
                       * 5805 MHz [161] (30.0 dBm)
                       * 5825 MHz [165] (30.0 dBm)

Quoted 3 lines

This is running 2.6.37 with compat-wireless from sometime in March, probably.  I'll try with 2.6.39 and latest compat-wireless when I get a chance.

What's the problem? You ahve DFS requirements on the channels listed with DFS. You can initiate radiation on the others. We lack master support for DFS yet so you cannot initiate radiation on those channels.

Quoted 1 line

 Luis

What I'm seeing is exactly what I would expect.  What Ben is seeing, with the same model card, is different (he has passive scanning set on all 5GHz channels).  It looks like SparkLan changed the EEPROM regdomain on the WPEA-127N from 0 to 0x6a (I bought my cards a month or so before he did).

Quoted 96 lines · Brian Prodoehl

Quoted 49 lines · Ben Greear

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Quoted 8 lines

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

Strange.  This is what I get out of my WPEA-127N:

ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a

Here's how my 5GHz channels look:
               Frequencies:
                       * 5180 MHz [36] (17.0 dBm)
                       * 5200 MHz [40] (17.0 dBm)
                       * 5220 MHz [44] (17.0 dBm)
                       * 5240 MHz [48] (17.0 dBm)
                       * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5600 MHz [120] (disabled)
                       * 5620 MHz [124] (disabled)
                       * 5640 MHz [128] (disabled)
                       * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5745 MHz [149] (30.0 dBm)
                       * 5765 MHz [153] (30.0 dBm)
                       * 5785 MHz [157] (30.0 dBm)
                       * 5805 MHz [161] (30.0 dBm)
                       * 5825 MHz [165] (30.0 dBm)

Quoted 3 lines

This is running 2.6.37 with compat-wireless from sometime in March, probably.  I'll try with 2.6.39 and latest compat-wireless when I get a chance.

What's the problem? You ahve DFS requirements on the channels listed with DFS. You can initiate radiation on the others. We lack master support for DFS yet so you cannot initiate radiation on those channels.

 Luis

Quoted 49 lines · Ben Greear

Quoted 21 lines · Ben Greear

Quoted 19 lines · Ben Greear

Quoted 11 lines · Mohammed Shafi

Quoted 5 lines · Ben Greear

This is on 2.6.39-wl+

All the 5Ghz channels are showing as passive scanning, which makes them unusable for APs if nothing else.

for me channels 36,40,44,48 are ok in 5ghz. used the latest wireless-testing just brought the card up as station mode.

Most of my systems show the same, at least most of the time.

Quoted 2 lines

Quoted 1 line

Any idea why this is happening?

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

don't know, may be regulatory.

After a reboot and an idle weekend, mine also look normal. So, it's something transient it appears.

Err, I mis-spoke..the 9380 system still shows passive scanning everywhere...

Busted one:

ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a

cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Quoted 8 lines

Bleh, seems my Sparklan 127 NIC is set to world-roam :(

What a total pain in the arse!
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

Strange.  This is what I get out of my WPEA-127N:

ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a

Here's how my 5GHz channels look:
               Frequencies:
                       * 5180 MHz [36] (17.0 dBm)
                       * 5200 MHz [40] (17.0 dBm)
                       * 5220 MHz [44] (17.0 dBm)
                       * 5240 MHz [48] (17.0 dBm)
                       * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5600 MHz [120] (disabled)
                       * 5620 MHz [124] (disabled)
                       * 5640 MHz [128] (disabled)
                       * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                       * 5745 MHz [149] (30.0 dBm)
                       * 5765 MHz [153] (30.0 dBm)
                       * 5785 MHz [157] (30.0 dBm)
                       * 5805 MHz [161] (30.0 dBm)
                       * 5825 MHz [165] (30.0 dBm)

This is running 2.6.37 with compat-wireless from sometime in March, probably.  I'll try with 2.6.39 and latest compat-wireless when I get a chance.

-Brian

Quoted 4 lines · Brian Prodoehl

This is running 2.6.37 with compat-wireless from sometime in March, probably. I'll try with 2.6.39 and latest compat-wireless when I get a chance.

I got the similar result with latest wireless testing