Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-08-01 Thread Nicola von Thadden
Hi,

my main problem isn't the 17dBm on the lower 5ghz channels. I can
happily use a higher channel with DFS and 250mW (which seems to be the
hardware limit).
My main problem is the DFS implementation which seems to limit 2.4ghz to
a lower value:
I have two similar regulatory entries:
country DF: DFS-FCC
(2402 - 2472 @ 40), (30)
(5170 - 5250 @ 80), (17), AUTO-BW
(5250 - 5330 @ 80), (23), DFS, AUTO-BW
(5490 - 5730 @ 160), (23), DFS
(5735 - 5835 @ 80), (30)
country DG: DFS-ETSI
(2402 - 2472 @ 40), (30)
(5170 - 5250 @ 80), (17), AUTO-BW
(5250 - 5330 @ 80), (23), DFS, AUTO-BW
(5490 - 5730 @ 160), (23), DFS
(5735 - 5835 @ 80), (30)

root@ap02:~# iw reg set DF
root@ap02:~# iwinfo wlan0 txp
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
  15 dBm (  31 mW)
  16 dBm (  39 mW)
  17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)
  21 dBm ( 125 mW)
  22 dBm ( 158 mW)
  23 dBm ( 199 mW)
  24 dBm ( 251 mW)
  25 dBm ( 316 mW)
  26 dBm ( 398 mW)
  27 dBm ( 501 mW)
* 28 dBm ( 630 mW)
  29 dBm ( 794 mW)
root@ap02:~# iw reg set DG
root@ap02:~# iw phy phy0 set txpower fixed 2000
root@ap02:~# iwinfo wlan0 txp
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
  15 dBm (  31 mW)
  16 dBm (  39 mW)
* 17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)
  21 dBm ( 125 mW)
  22 dBm ( 158 mW)
  23 dBm ( 199 mW)
  24 dBm ( 251 mW)
  25 dBm ( 316 mW)
  26 dBm ( 398 mW)
  27 dBm ( 501 mW)
  28 dBm ( 630 mW)
  29 dBm ( 794 mW)
root@ap02:~#


You see what I mean? The problem is not the power level in the
regulatory database. The problem is that the software thinks it's right
to limit it to 17dBm. It also does not depend which antenna gain is set
via iw of what power levels are defined in the regulatory database.
Everything higher than 17dBm is ignored and set to 17dBm, on 2.4Ghz.

Since the only difference is the DFS regulatory information, I think the
part parsing those information from the database is faulty. Maybe it
thinks that it's okay to limit it to 17dBm because DFS is not used on
2.4Ghz, which is sonsense.

I don't think that any part in hardware is causing the problem. I can
use higher power levels on 2.4Ghz when using DFS-FCC or no regulatory
limitations at all.

Thanks
Nico



On 07/30/2015 06:08 PM, Gerald Matzka wrote:
 Ben is right, take a look at 
 https://forum.openwrt.org/viewtopic.php?id=42197
 
 In newer Openwrt versions the kernel modules are compiled to respect the
 reg-domain settings programmed in hardware.
 
 Kind regards
 
 ... sent from my iPhone
 
 Am 30.07.2015 um 17:11 schrieb Ben West b...@gowasabi.net
 mailto:b...@gowasabi.net:
 
 You can look up your respective country's spectrum regulations.  It is
 possible prior versions OpenWRT didn't fully conform to each
 regulatory domain and were fixed in more recent versions (just as the
 converse is possible).

 For example, for the USA, here is a table of power limits for the
 2.4GHz and 5GHz bands.  Channels 36-48 are limited to 16dBm
 transmitter power.
 http://www.air802.com/fcc-rules-and-regulations.html

 On Thu, Jul 30, 2015 at 3:32 AM, Nicola von Thadden n...@vthadden.de
 mailto:n...@vthadden.de wrote:

 Hi,

 I also thought to have used 20dBm or 23dBm in earlier releases (AA).
 Is there a way to find out to which txpower levels the 5Ghz
 transceiver
 is limited? I think the driver reads them out, maybe there is a way to
 print them on the cmd?

 But my main problem is the 17dBm on 2.4Ghz when setting DFS-ETSI
 countries. I don't think that it is a problem of the hardware but
 of the
 software parsing the regdom. Maybe there is a fixed limit of 17dBm on
 non-DFS channels, even when DFS is not required, which is not very
 useful. Does anyone have an idea where that could be set? My search in
 the source code had no results until now, where it could be.

 Thanks
 Nico

 On 07/29/2015 06:21 PM, Atanas Vladimirov wrote:
  https://dev.openwrt.org/ticket/20201
 
  On BB I used 20dBm for both 2.4 and 5GHz on the same router.
 
  Sent with AquaMail for Android
  http://www.aqua-mail.com
 
  On 29 юли 2015 г. 18:40:10 Ben West b...@gowasabi.net 
 mailto:b...@gowasabi.net wrote:
 
  This is what I observe running Barrier Breaker on UBNT M5 products,
  too.  I believe the 17dBm limit is intentional, i.e. per regulation.
  The 30dBm tx power limit applies to channels 

Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-07-30 Thread Ben West
You can look up your respective country's spectrum regulations.  It is
possible prior versions OpenWRT didn't fully conform to each regulatory
domain and were fixed in more recent versions (just as the converse is
possible).

For example, for the USA, here is a table of power limits for the 2.4GHz
and 5GHz bands.  Channels 36-48 are limited to 16dBm transmitter power.
http://www.air802.com/fcc-rules-and-regulations.html

On Thu, Jul 30, 2015 at 3:32 AM, Nicola von Thadden n...@vthadden.de
wrote:

 Hi,

 I also thought to have used 20dBm or 23dBm in earlier releases (AA).
 Is there a way to find out to which txpower levels the 5Ghz transceiver
 is limited? I think the driver reads them out, maybe there is a way to
 print them on the cmd?

 But my main problem is the 17dBm on 2.4Ghz when setting DFS-ETSI
 countries. I don't think that it is a problem of the hardware but of the
 software parsing the regdom. Maybe there is a fixed limit of 17dBm on
 non-DFS channels, even when DFS is not required, which is not very
 useful. Does anyone have an idea where that could be set? My search in
 the source code had no results until now, where it could be.

 Thanks
 Nico

 On 07/29/2015 06:21 PM, Atanas Vladimirov wrote:
  https://dev.openwrt.org/ticket/20201
 
  On BB I used 20dBm for both 2.4 and 5GHz on the same router.
 
  Sent with AquaMail for Android
  http://www.aqua-mail.com
 
  On 29 юли 2015 г. 18:40:10 Ben West b...@gowasabi.net wrote:
 
  This is what I observe running Barrier Breaker on UBNT M5 products,
  too.  I believe the 17dBm limit is intentional, i.e. per regulation.
  The 30dBm tx power limit applies to channels 149 and above, I believe.
 
Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are
  forced
to be 17dBm only on the WNDR3800? I found two possible explanations:
either because of the factory calibration
 
 
  On Wed, Jul 29, 2015 at 10:25 AM, Gerald Matzka mgeral...@yahoo.de
  mailto:mgeral...@yahoo.de wrote:
 
  Well, it looks like the txpower of your wdnr3800 is limited to
  17dBm because of the hardware reg-domain settings.
 
  Kind regards,
 
  ... sent from my iPhone
 
   Am 29.07.2015 um 10:43 schrieb Nicola von Thadden
  n...@vthadden.de mailto:n...@vthadden.de:
  
   Hi,
  
   I have this strange behaviour down below, for which I also opened
 a
   ticket because I think this should not be like that ;)
  
   Does anyone have an idea where the problem could originate from
  and how
   to fix it?
  
   Thanks
   Nico
  
   On 07/29/2015 12:37 AM, OpenWrt wrote:
   #20222: 2.4Ghz limited to 50mW in DFS-ETSI
   --+--
   Reporter:  nicoduck  |  Owner:  developers
   Type:  defect| Status:  new
   Priority:  normal|  Milestone:  Chaos Calmer (trunk)
   Component:  kernel|Version:  Trunk
   Keywords:  wndr3800  |
   --+--
   I have got a Netgear WNDR 3800 running with openwrt since quite
  a while.
   I now upgraded to the latest version (trunk) and wanted to use
  WLAN within
   the regulations here in Germany but also wanted to max out the
  output
   power (within the regulations).
   Switching the country to Germany limits the maximum output
  power to 17dBm,
   although it does show as being limited on 20dBm:
   root@OpenWrt:/# iwinfo wlan0 txpower
  0 dBm (   1 mW)
  1 dBm (   1 mW)
  2 dBm (   1 mW)
  3 dBm (   1 mW)
  4 dBm (   2 mW)
  5 dBm (   3 mW)
  6 dBm (   3 mW)
  7 dBm (   5 mW)
  8 dBm (   6 mW)
  9 dBm (   7 mW)
 10 dBm (  10 mW)
 11 dBm (  12 mW)
 12 dBm (  15 mW)
 13 dBm (  19 mW)
 14 dBm (  25 mW)
 15 dBm (  31 mW)
 16 dBm (  39 mW)
   * 17 dBm (  50 mW)
 18 dBm (  63 mW)
 19 dBm (  79 mW)
 20 dBm ( 100 mW)
  
   What I did: reset the device, flash it with various builts from
  trunk and
   try to figure out what was going on.
   I now modified my regdb and was able to isolate the source of
  the problem:
   country DE: DFS-ETSI
   # entries 279004 and 280006
   (2400 - 2483.5 @ 40), (100 mW)
   # entry 303005
   (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
   # entries 304002 and 305002
   (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
   # entries 308002, 309001 and 310003
   (5470 - 5725 @ 160), (500 mW), DFS
   # 60 gHz band channels 1-4, ref: Etsi En 302 567
   (57000 - 66000 @ 2160), (40)
   Thas does not work and has the mentioned behaviour, 2.4Ghz is
  limited at
   17dBm. It also does not depend on which values are set in 

Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-07-30 Thread David Lang
What's more, The regulation is on the signal strength of the radiated 
signal, not the transmitter power. so if you go to max transmitter power and add 
a better antenna, you actually exceed the limits.


There is apparently an exception to this for point-to-point use. But you still 
can't use full power + high gain antenna


David Lang

On Thu, 30 Jul 2015, Ben West wrote:


You can look up your respective country's spectrum regulations.  It is
possible prior versions OpenWRT didn't fully conform to each regulatory
domain and were fixed in more recent versions (just as the converse is
possible).

For example, for the USA, here is a table of power limits for the 2.4GHz
and 5GHz bands.  Channels 36-48 are limited to 16dBm transmitter power.
http://www.air802.com/fcc-rules-and-regulations.html

On Thu, Jul 30, 2015 at 3:32 AM, Nicola von Thadden n...@vthadden.de
wrote:


Hi,

I also thought to have used 20dBm or 23dBm in earlier releases (AA).
Is there a way to find out to which txpower levels the 5Ghz transceiver
is limited? I think the driver reads them out, maybe there is a way to
print them on the cmd?

But my main problem is the 17dBm on 2.4Ghz when setting DFS-ETSI
countries. I don't think that it is a problem of the hardware but of the
software parsing the regdom. Maybe there is a fixed limit of 17dBm on
non-DFS channels, even when DFS is not required, which is not very
useful. Does anyone have an idea where that could be set? My search in
the source code had no results until now, where it could be.

Thanks
Nico

On 07/29/2015 06:21 PM, Atanas Vladimirov wrote:

https://dev.openwrt.org/ticket/20201

On BB I used 20dBm for both 2.4 and 5GHz on the same router.

Sent with AquaMail for Android
http://www.aqua-mail.com

On 29 юли 2015 г. 18:40:10 Ben West b...@gowasabi.net wrote:


This is what I observe running Barrier Breaker on UBNT M5 products,
too.  I believe the 17dBm limit is intentional, i.e. per regulation.
The 30dBm tx power limit applies to channels 149 and above, I believe.


 Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are

forced

 to be 17dBm only on the WNDR3800? I found two possible explanations:
 either because of the factory calibration



On Wed, Jul 29, 2015 at 10:25 AM, Gerald Matzka mgeral...@yahoo.de
mailto:mgeral...@yahoo.de wrote:

Well, it looks like the txpower of your wdnr3800 is limited to
17dBm because of the hardware reg-domain settings.

Kind regards,

... sent from my iPhone

Am 29.07.2015 um 10:43 schrieb Nicola von Thadden
n...@vthadden.de mailto:n...@vthadden.de:
   
Hi,
   
I have this strange behaviour down below, for which I also opened

a

ticket because I think this should not be like that ;)
   
Does anyone have an idea where the problem could originate from
and how
to fix it?
   
Thanks
Nico
   
On 07/29/2015 12:37 AM, OpenWrt wrote:
#20222: 2.4Ghz limited to 50mW in DFS-ETSI
--+--
Reporter:  nicoduck  |  Owner:  developers
Type:  defect| Status:  new
Priority:  normal|  Milestone:  Chaos Calmer (trunk)
Component:  kernel|Version:  Trunk
Keywords:  wndr3800  |
--+--
I have got a Netgear WNDR 3800 running with openwrt since quite
a while.
I now upgraded to the latest version (trunk) and wanted to use
WLAN within
the regulations here in Germany but also wanted to max out the
output
power (within the regulations).
Switching the country to Germany limits the maximum output
power to 17dBm,
although it does show as being limited on 20dBm:
root@OpenWrt:/# iwinfo wlan0 txpower
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
  15 dBm (  31 mW)
  16 dBm (  39 mW)
* 17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)
   
What I did: reset the device, flash it with various builts from
trunk and
try to figure out what was going on.
I now modified my regdb and was able to isolate the source of
the problem:
country DE: DFS-ETSI
# entries 279004 and 280006
(2400 - 2483.5 @ 40), (100 mW)
# entry 303005
(5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
# entries 304002 and 305002
(5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
# entries 308002, 309001 and 310003
(5470 - 5725 @ 160), (500 mW), DFS
# 60 gHz band channels 1-4, ref: Etsi En 302 567
(57000 - 66000 @ 2160), (40)
Thas does not work and has the 

Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-07-30 Thread Nicola von Thadden
Hi,

I also thought to have used 20dBm or 23dBm in earlier releases (AA).
Is there a way to find out to which txpower levels the 5Ghz transceiver
is limited? I think the driver reads them out, maybe there is a way to
print them on the cmd?

But my main problem is the 17dBm on 2.4Ghz when setting DFS-ETSI
countries. I don't think that it is a problem of the hardware but of the
software parsing the regdom. Maybe there is a fixed limit of 17dBm on
non-DFS channels, even when DFS is not required, which is not very
useful. Does anyone have an idea where that could be set? My search in
the source code had no results until now, where it could be.

Thanks
Nico

On 07/29/2015 06:21 PM, Atanas Vladimirov wrote:
 https://dev.openwrt.org/ticket/20201
 
 On BB I used 20dBm for both 2.4 and 5GHz on the same router.
 
 Sent with AquaMail for Android
 http://www.aqua-mail.com
 
 On 29 юли 2015 г. 18:40:10 Ben West b...@gowasabi.net wrote:
 
 This is what I observe running Barrier Breaker on UBNT M5 products,
 too.  I believe the 17dBm limit is intentional, i.e. per regulation. 
 The 30dBm tx power limit applies to channels 149 and above, I believe.

   Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are
 forced
   to be 17dBm only on the WNDR3800? I found two possible explanations:
   either because of the factory calibration


 On Wed, Jul 29, 2015 at 10:25 AM, Gerald Matzka mgeral...@yahoo.de
 mailto:mgeral...@yahoo.de wrote:

 Well, it looks like the txpower of your wdnr3800 is limited to
 17dBm because of the hardware reg-domain settings.

 Kind regards,

 ... sent from my iPhone

  Am 29.07.2015 um 10:43 schrieb Nicola von Thadden
 n...@vthadden.de mailto:n...@vthadden.de:
 
  Hi,
 
  I have this strange behaviour down below, for which I also opened a
  ticket because I think this should not be like that ;)
 
  Does anyone have an idea where the problem could originate from
 and how
  to fix it?
 
  Thanks
  Nico
 
  On 07/29/2015 12:37 AM, OpenWrt wrote:
  #20222: 2.4Ghz limited to 50mW in DFS-ETSI
  --+--
  Reporter:  nicoduck  |  Owner:  developers
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  Chaos Calmer (trunk)
  Component:  kernel|Version:  Trunk
  Keywords:  wndr3800  |
  --+--
  I have got a Netgear WNDR 3800 running with openwrt since quite
 a while.
  I now upgraded to the latest version (trunk) and wanted to use
 WLAN within
  the regulations here in Germany but also wanted to max out the
 output
  power (within the regulations).
  Switching the country to Germany limits the maximum output
 power to 17dBm,
  although it does show as being limited on 20dBm:
  root@OpenWrt:/# iwinfo wlan0 txpower
 0 dBm (   1 mW)
 1 dBm (   1 mW)
 2 dBm (   1 mW)
 3 dBm (   1 mW)
 4 dBm (   2 mW)
 5 dBm (   3 mW)
 6 dBm (   3 mW)
 7 dBm (   5 mW)
 8 dBm (   6 mW)
 9 dBm (   7 mW)
10 dBm (  10 mW)
11 dBm (  12 mW)
12 dBm (  15 mW)
13 dBm (  19 mW)
14 dBm (  25 mW)
15 dBm (  31 mW)
16 dBm (  39 mW)
  * 17 dBm (  50 mW)
18 dBm (  63 mW)
19 dBm (  79 mW)
20 dBm ( 100 mW)
 
  What I did: reset the device, flash it with various builts from
 trunk and
  try to figure out what was going on.
  I now modified my regdb and was able to isolate the source of
 the problem:
  country DE: DFS-ETSI
  # entries 279004 and 280006
  (2400 - 2483.5 @ 40), (100 mW)
  # entry 303005
  (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
  # entries 304002 and 305002
  (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
  # entries 308002, 309001 and 310003
  (5470 - 5725 @ 160), (500 mW), DFS
  # 60 gHz band channels 1-4, ref: Etsi En 302 567
  (57000 - 66000 @ 2160), (40)
  Thas does not work and has the mentioned behaviour, 2.4Ghz is
 limited at
  17dBm. It also does not depend on which values are set in the
 regulatory
  database for the 2.4Ghz channels, anything over 17dBm will be
 limited to
  17dBm.
  running iw phy phy0 set txpower fixed 2000 gives no error but
 does not
  change it to 20dBm. Changing the value to anything below 17dBm
 works
  though.
 
  country DE: DFS-FCC
  # entries 279004 and 280006
  (2400 - 2483.5 @ 40), (100 mW)
  # entry 303005
  (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
  # entries 304002 and 305002
  (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW

Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-07-30 Thread Gerald Matzka
Ben is right, take a look at 
https://forum.openwrt.org/viewtopic.php?id=42197

In newer Openwrt versions the kernel modules are compiled to respect the 
reg-domain settings programmed in hardware.

Kind regards

... sent from my iPhone

 Am 30.07.2015 um 17:11 schrieb Ben West b...@gowasabi.net:
 
 You can look up your respective country's spectrum regulations.  It is 
 possible prior versions OpenWRT didn't fully conform to each regulatory 
 domain and were fixed in more recent versions (just as the converse is 
 possible).
 
 For example, for the USA, here is a table of power limits for the 2.4GHz and 
 5GHz bands.  Channels 36-48 are limited to 16dBm transmitter power.
 http://www.air802.com/fcc-rules-and-regulations.html
 
 On Thu, Jul 30, 2015 at 3:32 AM, Nicola von Thadden n...@vthadden.de wrote:
 Hi,
 
 I also thought to have used 20dBm or 23dBm in earlier releases (AA).
 Is there a way to find out to which txpower levels the 5Ghz transceiver
 is limited? I think the driver reads them out, maybe there is a way to
 print them on the cmd?
 
 But my main problem is the 17dBm on 2.4Ghz when setting DFS-ETSI
 countries. I don't think that it is a problem of the hardware but of the
 software parsing the regdom. Maybe there is a fixed limit of 17dBm on
 non-DFS channels, even when DFS is not required, which is not very
 useful. Does anyone have an idea where that could be set? My search in
 the source code had no results until now, where it could be.
 
 Thanks
 Nico
 
 On 07/29/2015 06:21 PM, Atanas Vladimirov wrote:
  https://dev.openwrt.org/ticket/20201
 
  On BB I used 20dBm for both 2.4 and 5GHz on the same router.
 
  Sent with AquaMail for Android
  http://www.aqua-mail.com
 
  On 29 юли 2015 г. 18:40:10 Ben West b...@gowasabi.net wrote:
 
  This is what I observe running Barrier Breaker on UBNT M5 products,
  too.  I believe the 17dBm limit is intentional, i.e. per regulation.
  The 30dBm tx power limit applies to channels 149 and above, I believe.
 
Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are
  forced
to be 17dBm only on the WNDR3800? I found two possible explanations:
either because of the factory calibration
 
 
  On Wed, Jul 29, 2015 at 10:25 AM, Gerald Matzka mgeral...@yahoo.de
  mailto:mgeral...@yahoo.de wrote:
 
  Well, it looks like the txpower of your wdnr3800 is limited to
  17dBm because of the hardware reg-domain settings.
 
  Kind regards,
 
  ... sent from my iPhone
 
   Am 29.07.2015 um 10:43 schrieb Nicola von Thadden
  n...@vthadden.de mailto:n...@vthadden.de:
  
   Hi,
  
   I have this strange behaviour down below, for which I also opened a
   ticket because I think this should not be like that ;)
  
   Does anyone have an idea where the problem could originate from
  and how
   to fix it?
  
   Thanks
   Nico
  
   On 07/29/2015 12:37 AM, OpenWrt wrote:
   #20222: 2.4Ghz limited to 50mW in DFS-ETSI
   --+--
   Reporter:  nicoduck  |  Owner:  developers
   Type:  defect| Status:  new
   Priority:  normal|  Milestone:  Chaos Calmer (trunk)
   Component:  kernel|Version:  Trunk
   Keywords:  wndr3800  |
   --+--
   I have got a Netgear WNDR 3800 running with openwrt since quite
  a while.
   I now upgraded to the latest version (trunk) and wanted to use
  WLAN within
   the regulations here in Germany but also wanted to max out the
  output
   power (within the regulations).
   Switching the country to Germany limits the maximum output
  power to 17dBm,
   although it does show as being limited on 20dBm:
   root@OpenWrt:/# iwinfo wlan0 txpower
  0 dBm (   1 mW)
  1 dBm (   1 mW)
  2 dBm (   1 mW)
  3 dBm (   1 mW)
  4 dBm (   2 mW)
  5 dBm (   3 mW)
  6 dBm (   3 mW)
  7 dBm (   5 mW)
  8 dBm (   6 mW)
  9 dBm (   7 mW)
 10 dBm (  10 mW)
 11 dBm (  12 mW)
 12 dBm (  15 mW)
 13 dBm (  19 mW)
 14 dBm (  25 mW)
 15 dBm (  31 mW)
 16 dBm (  39 mW)
   * 17 dBm (  50 mW)
 18 dBm (  63 mW)
 19 dBm (  79 mW)
 20 dBm ( 100 mW)
  
   What I did: reset the device, flash it with various builts from
  trunk and
   try to figure out what was going on.
   I now modified my regdb and was able to isolate the source of
  the problem:
   country DE: DFS-ETSI
   # entries 279004 and 280006
   (2400 - 2483.5 @ 40), (100 mW)
   # entry 303005
   (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
   # entries 304002 and 305002
   (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
   # entries 308002, 309001 and 

Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-07-29 Thread Atanas Vladimirov

https://dev.openwrt.org/ticket/20201

On BB I used 20dBm for both 2.4 and 5GHz on the same router.

Sent with AquaMail for Android
http://www.aqua-mail.com


On 29 юли 2015 г. 18:40:10 Ben West b...@gowasabi.net wrote:


This is what I observe running Barrier Breaker on UBNT M5 products, too.  I
believe the 17dBm limit is intentional, i.e. per regulation.  The 30dBm tx
power limit applies to channels 149 and above, I believe.

  Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are forced
  to be 17dBm only on the WNDR3800? I found two possible explanations:
  either because of the factory calibration


On Wed, Jul 29, 2015 at 10:25 AM, Gerald Matzka mgeral...@yahoo.de wrote:

 Well, it looks like the txpower of your wdnr3800 is limited to 17dBm
 because of the hardware reg-domain settings.

 Kind regards,

 ... sent from my iPhone

  Am 29.07.2015 um 10:43 schrieb Nicola von Thadden n...@vthadden.de:
 
  Hi,
 
  I have this strange behaviour down below, for which I also opened a
  ticket because I think this should not be like that ;)
 
  Does anyone have an idea where the problem could originate from and how
  to fix it?
 
  Thanks
  Nico
 
  On 07/29/2015 12:37 AM, OpenWrt wrote:
  #20222: 2.4Ghz limited to 50mW in DFS-ETSI
  --+--
  Reporter:  nicoduck  |  Owner:  developers
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  Chaos Calmer (trunk)
  Component:  kernel|Version:  Trunk
  Keywords:  wndr3800  |
  --+--
  I have got a Netgear WNDR 3800 running with openwrt since quite a while.
  I now upgraded to the latest version (trunk) and wanted to use WLAN
 within
  the regulations here in Germany but also wanted to max out the output
  power (within the regulations).
  Switching the country to Germany limits the maximum output power to
 17dBm,
  although it does show as being limited on 20dBm:
  root@OpenWrt:/# iwinfo wlan0 txpower
 0 dBm (   1 mW)
 1 dBm (   1 mW)
 2 dBm (   1 mW)
 3 dBm (   1 mW)
 4 dBm (   2 mW)
 5 dBm (   3 mW)
 6 dBm (   3 mW)
 7 dBm (   5 mW)
 8 dBm (   6 mW)
 9 dBm (   7 mW)
10 dBm (  10 mW)
11 dBm (  12 mW)
12 dBm (  15 mW)
13 dBm (  19 mW)
14 dBm (  25 mW)
15 dBm (  31 mW)
16 dBm (  39 mW)
  * 17 dBm (  50 mW)
18 dBm (  63 mW)
19 dBm (  79 mW)
20 dBm ( 100 mW)
 
  What I did: reset the device, flash it with various builts from trunk
 and
  try to figure out what was going on.
  I now modified my regdb and was able to isolate the source of the
 problem:
  country DE: DFS-ETSI
  # entries 279004 and 280006
  (2400 - 2483.5 @ 40), (100 mW)
  # entry 303005
  (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
  # entries 304002 and 305002
  (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
  # entries 308002, 309001 and 310003
  (5470 - 5725 @ 160), (500 mW), DFS
  # 60 gHz band channels 1-4, ref: Etsi En 302 567
  (57000 - 66000 @ 2160), (40)
  Thas does not work and has the mentioned behaviour, 2.4Ghz is limited at
  17dBm. It also does not depend on which values are set in the regulatory
  database for the 2.4Ghz channels, anything over 17dBm will be limited to
  17dBm.
  running iw phy phy0 set txpower fixed 2000 gives no error but does not
  change it to 20dBm. Changing the value to anything below 17dBm works
  though.
 
  country DE: DFS-FCC
  # entries 279004 and 280006
  (2400 - 2483.5 @ 40), (100 mW)
  # entry 303005
  (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
  # entries 304002 and 305002
  (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
  # entries 308002, 309001 and 310003
  (5470 - 5725 @ 160), (500 mW), DFS
  # 60 gHz band channels 1-4, ref: Etsi En 302 567
  (57000 - 66000 @ 2160), (40)
 
  Thad does work. The only change to the entry above is DFS-FCC instead
 of
  DFS-ETSI. I can now select any powerlevel between 1 and 20dBm and it
 is
  also reported as being used:
  root@OpenWrt:/# iwinfo wlan0 txpower
 0 dBm (   1 mW)
 1 dBm (   1 mW)
 2 dBm (   1 mW)
 3 dBm (   1 mW)
 4 dBm (   2 mW)
 5 dBm (   3 mW)
 6 dBm (   3 mW)
 7 dBm (   5 mW)
 8 dBm (   6 mW)
 9 dBm (   7 mW)
10 dBm (  10 mW)
11 dBm (  12 mW)
12 dBm (  15 mW)
13 dBm (  19 mW)
14 dBm (  25 mW)
15 dBm (  31 mW)
16 dBm (  39 mW)
17 dBm (  50 mW)
18 dBm (  63 mW)
19 dBm (  79 mW)
  * 20 dBm ( 100 mW)
 
 
  I have no idea why but there seems to be a bug in the code parsing the
 DFS
  regulations, limiting 2.4Ghz to lot lower values than allowed. Changing
 it
  to DFS-FCC works for using the applicaple output power but does not seem
  to be in compliance which German law.
 
  Do you have an idea where the problem could 

Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-07-29 Thread Gerald Matzka
Well, it looks like the txpower of your wdnr3800 is limited to 17dBm because of 
the hardware reg-domain settings. 

Kind regards,

... sent from my iPhone

 Am 29.07.2015 um 10:43 schrieb Nicola von Thadden n...@vthadden.de:
 
 Hi,
 
 I have this strange behaviour down below, for which I also opened a
 ticket because I think this should not be like that ;)
 
 Does anyone have an idea where the problem could originate from and how
 to fix it?
 
 Thanks
 Nico
 
 On 07/29/2015 12:37 AM, OpenWrt wrote:
 #20222: 2.4Ghz limited to 50mW in DFS-ETSI
 --+--
 Reporter:  nicoduck  |  Owner:  developers
 Type:  defect| Status:  new
 Priority:  normal|  Milestone:  Chaos Calmer (trunk)
 Component:  kernel|Version:  Trunk
 Keywords:  wndr3800  |
 --+--
 I have got a Netgear WNDR 3800 running with openwrt since quite a while.
 I now upgraded to the latest version (trunk) and wanted to use WLAN within
 the regulations here in Germany but also wanted to max out the output
 power (within the regulations).
 Switching the country to Germany limits the maximum output power to 17dBm,
 although it does show as being limited on 20dBm:
 root@OpenWrt:/# iwinfo wlan0 txpower
0 dBm (   1 mW)
1 dBm (   1 mW)
2 dBm (   1 mW)
3 dBm (   1 mW)
4 dBm (   2 mW)
5 dBm (   3 mW)
6 dBm (   3 mW)
7 dBm (   5 mW)
8 dBm (   6 mW)
9 dBm (   7 mW)
   10 dBm (  10 mW)
   11 dBm (  12 mW)
   12 dBm (  15 mW)
   13 dBm (  19 mW)
   14 dBm (  25 mW)
   15 dBm (  31 mW)
   16 dBm (  39 mW)
 * 17 dBm (  50 mW)
   18 dBm (  63 mW)
   19 dBm (  79 mW)
   20 dBm ( 100 mW)
 
 What I did: reset the device, flash it with various builts from trunk and
 try to figure out what was going on.
 I now modified my regdb and was able to isolate the source of the problem:
 country DE: DFS-ETSI
 # entries 279004 and 280006
 (2400 - 2483.5 @ 40), (100 mW)
 # entry 303005
 (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
 # entries 304002 and 305002
 (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
 # entries 308002, 309001 and 310003
 (5470 - 5725 @ 160), (500 mW), DFS
 # 60 gHz band channels 1-4, ref: Etsi En 302 567
 (57000 - 66000 @ 2160), (40)
 Thas does not work and has the mentioned behaviour, 2.4Ghz is limited at
 17dBm. It also does not depend on which values are set in the regulatory
 database for the 2.4Ghz channels, anything over 17dBm will be limited to
 17dBm.
 running iw phy phy0 set txpower fixed 2000 gives no error but does not
 change it to 20dBm. Changing the value to anything below 17dBm works
 though.
 
 country DE: DFS-FCC
 # entries 279004 and 280006
 (2400 - 2483.5 @ 40), (100 mW)
 # entry 303005
 (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
 # entries 304002 and 305002
 (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
 # entries 308002, 309001 and 310003
 (5470 - 5725 @ 160), (500 mW), DFS
 # 60 gHz band channels 1-4, ref: Etsi En 302 567
 (57000 - 66000 @ 2160), (40)
 
 Thad does work. The only change to the entry above is DFS-FCC instead of
 DFS-ETSI. I can now select any powerlevel between 1 and 20dBm and it is
 also reported as being used:
 root@OpenWrt:/# iwinfo wlan0 txpower
0 dBm (   1 mW)
1 dBm (   1 mW)
2 dBm (   1 mW)
3 dBm (   1 mW)
4 dBm (   2 mW)
5 dBm (   3 mW)
6 dBm (   3 mW)
7 dBm (   5 mW)
8 dBm (   6 mW)
9 dBm (   7 mW)
   10 dBm (  10 mW)
   11 dBm (  12 mW)
   12 dBm (  15 mW)
   13 dBm (  19 mW)
   14 dBm (  25 mW)
   15 dBm (  31 mW)
   16 dBm (  39 mW)
   17 dBm (  50 mW)
   18 dBm (  63 mW)
   19 dBm (  79 mW)
 * 20 dBm ( 100 mW)
 
 
 I have no idea why but there seems to be a bug in the code parsing the DFS
 regulations, limiting 2.4Ghz to lot lower values than allowed. Changing it
 to DFS-FCC works for using the applicaple output power but does not seem
 to be in compliance which German law.
 
 Do you have an idea where the problem could be? I'm happy to try out more
 builds and future versions.
 
 Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are forced
 to be 17dBm only on the WNDR3800? I found two possible explanations:
 either because of the factory calibration (is it possible to get them in a
 human readable form somehow? The hexdump is not really readable and I have
 not been able to find the code which pases them) or because these channels
 are considered as edge-channels and someone thought it would be safe to
 limit the power, to not disturb any other systems running on even lower
 channels. The latter explanation is kind of weird because it would make no
 sense to limit these 4 channels but no other ones. I find it especially
 strange because that is typically the job of regulatory authorities, to
 define those 

Re: [OpenWrt-Devel] [OpenWrt] 2.4Ghz limited to 50mW in DFS-ETSI

2015-07-29 Thread Ben West
This is what I observe running Barrier Breaker on UBNT M5 products, too.  I
believe the 17dBm limit is intentional, i.e. per regulation.  The 30dBm tx
power limit applies to channels 149 and above, I believe.

  Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are forced
  to be 17dBm only on the WNDR3800? I found two possible explanations:
  either because of the factory calibration


On Wed, Jul 29, 2015 at 10:25 AM, Gerald Matzka mgeral...@yahoo.de wrote:

 Well, it looks like the txpower of your wdnr3800 is limited to 17dBm
 because of the hardware reg-domain settings.

 Kind regards,

 ... sent from my iPhone

  Am 29.07.2015 um 10:43 schrieb Nicola von Thadden n...@vthadden.de:
 
  Hi,
 
  I have this strange behaviour down below, for which I also opened a
  ticket because I think this should not be like that ;)
 
  Does anyone have an idea where the problem could originate from and how
  to fix it?
 
  Thanks
  Nico
 
  On 07/29/2015 12:37 AM, OpenWrt wrote:
  #20222: 2.4Ghz limited to 50mW in DFS-ETSI
  --+--
  Reporter:  nicoduck  |  Owner:  developers
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  Chaos Calmer (trunk)
  Component:  kernel|Version:  Trunk
  Keywords:  wndr3800  |
  --+--
  I have got a Netgear WNDR 3800 running with openwrt since quite a while.
  I now upgraded to the latest version (trunk) and wanted to use WLAN
 within
  the regulations here in Germany but also wanted to max out the output
  power (within the regulations).
  Switching the country to Germany limits the maximum output power to
 17dBm,
  although it does show as being limited on 20dBm:
  root@OpenWrt:/# iwinfo wlan0 txpower
 0 dBm (   1 mW)
 1 dBm (   1 mW)
 2 dBm (   1 mW)
 3 dBm (   1 mW)
 4 dBm (   2 mW)
 5 dBm (   3 mW)
 6 dBm (   3 mW)
 7 dBm (   5 mW)
 8 dBm (   6 mW)
 9 dBm (   7 mW)
10 dBm (  10 mW)
11 dBm (  12 mW)
12 dBm (  15 mW)
13 dBm (  19 mW)
14 dBm (  25 mW)
15 dBm (  31 mW)
16 dBm (  39 mW)
  * 17 dBm (  50 mW)
18 dBm (  63 mW)
19 dBm (  79 mW)
20 dBm ( 100 mW)
 
  What I did: reset the device, flash it with various builts from trunk
 and
  try to figure out what was going on.
  I now modified my regdb and was able to isolate the source of the
 problem:
  country DE: DFS-ETSI
  # entries 279004 and 280006
  (2400 - 2483.5 @ 40), (100 mW)
  # entry 303005
  (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
  # entries 304002 and 305002
  (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
  # entries 308002, 309001 and 310003
  (5470 - 5725 @ 160), (500 mW), DFS
  # 60 gHz band channels 1-4, ref: Etsi En 302 567
  (57000 - 66000 @ 2160), (40)
  Thas does not work and has the mentioned behaviour, 2.4Ghz is limited at
  17dBm. It also does not depend on which values are set in the regulatory
  database for the 2.4Ghz channels, anything over 17dBm will be limited to
  17dBm.
  running iw phy phy0 set txpower fixed 2000 gives no error but does not
  change it to 20dBm. Changing the value to anything below 17dBm works
  though.
 
  country DE: DFS-FCC
  # entries 279004 and 280006
  (2400 - 2483.5 @ 40), (100 mW)
  # entry 303005
  (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
  # entries 304002 and 305002
  (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
  # entries 308002, 309001 and 310003
  (5470 - 5725 @ 160), (500 mW), DFS
  # 60 gHz band channels 1-4, ref: Etsi En 302 567
  (57000 - 66000 @ 2160), (40)
 
  Thad does work. The only change to the entry above is DFS-FCC instead
 of
  DFS-ETSI. I can now select any powerlevel between 1 and 20dBm and it
 is
  also reported as being used:
  root@OpenWrt:/# iwinfo wlan0 txpower
 0 dBm (   1 mW)
 1 dBm (   1 mW)
 2 dBm (   1 mW)
 3 dBm (   1 mW)
 4 dBm (   2 mW)
 5 dBm (   3 mW)
 6 dBm (   3 mW)
 7 dBm (   5 mW)
 8 dBm (   6 mW)
 9 dBm (   7 mW)
10 dBm (  10 mW)
11 dBm (  12 mW)
12 dBm (  15 mW)
13 dBm (  19 mW)
14 dBm (  25 mW)
15 dBm (  31 mW)
16 dBm (  39 mW)
17 dBm (  50 mW)
18 dBm (  63 mW)
19 dBm (  79 mW)
  * 20 dBm ( 100 mW)
 
 
  I have no idea why but there seems to be a bug in the code parsing the
 DFS
  regulations, limiting 2.4Ghz to lot lower values than allowed. Changing
 it
  to DFS-FCC works for using the applicaple output power but does not seem
  to be in compliance which German law.
 
  Do you have an idea where the problem could be? I'm happy to try out
 more
  builds and future versions.
 
  Also (kind of off-topic): Do you know why 5Ghz channels 36-48 are forced
  to be 17dBm only on the WNDR3800? I found two possible explanations:
  either