Question on 'iw reg get/set'

I'm using an ath9k NIC on a slightly hacked 2.6.34 kernel, Fedora 13 32-bit. I'm using the stock 'iw' command that comes with Fedora 13.

As far as I can tell, the results of 'iw reg get'
are funky:

[root@atom lanforge]# iw reg get
country 98:

	(2402 - 2472 @ 40), (N/A, 20)
	(5170 - 5250 @ 20), (N/A, 17)
	(5250 - 5330 @ 20), (N/A, 18), DFS

What is '98'? It doesn't correspond to anything I can find in the numeric or ascii lists of country codes.

Also, setting the domain doesn't seem to do anything, although there are no errors:

[root@atom lanforge]# iw reg get
country 98:

	(2402 - 2472 @ 40), (N/A, 20)
	(5170 - 5250 @ 20), (N/A, 17)
	(5250 - 5330 @ 20), (N/A, 18), DFS
[root@atom lanforge]# iw reg set US
[root@atom lanforge]# iw reg get
country 98:
	(2402 - 2472 @ 40), (N/A, 20)
	(5170 - 5250 @ 20), (N/A, 17)
	(5250 - 5330 @ 20), (N/A, 18), DFS

Anyone know if this is *supposed* to work?

Quoted 30 lines · Ben Greear

I'm using an ath9k NIC on a slightly hacked 2.6.34 kernel, Fedora 13 32-bit. I'm using the stock 'iw' command that comes with Fedora 13.

As far as I can tell, the results of 'iw reg get'
are funky:

[root@atom lanforge]# iw reg get
country 98:

	(2402 - 2472 @ 40), (N/A, 20)
	(5170 - 5250 @ 20), (N/A, 17)
	(5250 - 5330 @ 20), (N/A, 18), DFS

What is '98'? It doesn't correspond to anything I can find in the numeric or ascii lists of country codes.

Also, setting the domain doesn't seem to do anything, although there are no errors:

[root@atom lanforge]# iw reg get
country 98:

	(2402 - 2472 @ 40), (N/A, 20)
	(5170 - 5250 @ 20), (N/A, 17)
	(5250 - 5330 @ 20), (N/A, 18), DFS
[root@atom lanforge]# iw reg set US
[root@atom lanforge]# iw reg get
country 98:
	(2402 - 2472 @ 40), (N/A, 20)
	(5170 - 5250 @ 20), (N/A, 17)
	(5250 - 5330 @ 20), (N/A, 18), DFS

Quoted 1 line

Anyone know if this is *supposed* to work?

The ath9k driver is setting its own regulatory restrictions based on its EEPROM. Setting the domain from userland can only further restrict the regulatory settings. The '98' value represents a synthesized regulatory domain, based on the intersection of the available source of regulatory information (which can include the EEPROM, the userland setting, and a country IE from your AP).

Quoted 6 lines · John W. Linville

The ath9k driver is setting its own regulatory restrictions based on its EEPROM. Setting the domain from userland can only further restrict the regulatory settings. The '98' value represents a synthesized regulatory domain, based on the intersection of the available source of regulatory information (which can include the EEPROM, the userland setting, and a country IE from your AP).

Is there any way to get/set these raw settings (like, whatever it has in EEPROM)?

I expect we may ship some of these systems overseas, and would like the flexibility to set the country-code for testing purposes, if nothing else.

Is there any documentation as to what '98' really means, or do we just ignore that value and look at the info printed out after that?

Quoted 9 lines · Ben Greear

Quoted 6 lines · John W. Linville

The ath9k driver is setting its own regulatory restrictions based on its EEPROM.  Setting the domain from userland can only further restrict the regulatory settings.  The '98' value represents a synthesized regulatory domain, based on the intersection of the available source of regulatory information (which can include the EEPROM, the userland setting, and a country IE from your AP).

Quoted 4 lines

Is there any way to get/set these raw settings (like, whatever it has in EEPROM)?

I expect we may ship some of these systems overseas, and would like the flexibility to set the country-code for testing purposes, if nothing else.

I'll leave it to the Atheros guys to address this.

Quoted 2 lines

Is there any documentation as to what '98' really means, or do we just ignore that value and look at the info printed out after that?

'98' pretty much means "look at the info" :-)