Re: [LEDE-DEV] regulatory domain information

2016-11-18 Thread Charles 
on 2016-10-20 Charles wrote:
> on 2016-10-19 Charles wrote:
> 
> > Questions:  
> 
> A similar observation: With OpenWrt 15.05.1, after booting, dmesg
> output contains driver messages related to regulatory domain
> changes and final (I hope) settings:
> 
> > [   10.85] cfg80211: Calling CRDA to update world regulatory
> > domain [   10.88] cfg80211: World regulatory domain updated:
> > [   10.88] cfg80211:  DFS Master region: unset
> > [   10.89] cfg80211:   (start_freq - end_freq @ bandwidth),
> > (max_antenna_gain, max_eirp), (dfs_cac_time) [   10.90]
> > cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000
> > mBm), (N/A) [   10.91] cfg80211:   (2457000 KHz - 2482000 KHz @
> > 2 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [   10.92]
> > cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000
> > mBm), (N/A) [   10.92] cfg80211:   (517 KHz - 525 KHz @
> > 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) [   10.93]
> > cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz
> > AUTO), (N/A, 2000 mBm), (0 s) [   10.94] cfg80211:   (549
> > KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
> > [   10.95] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz),
> > (N/A, 2000 mBm), (N/A) [   10.96] cfg80211:   (5724 KHz -
> > 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) ... [   11.14]
> > cfg80211: Calling CRDA for country: US [   11.14] cfg80211:
> > Regulatory domain changed to country: US [   11.15] cfg80211:
> > DFS Master region: FCC [   11.15] cfg80211:   (start_freq -
> > end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
> > [   11.16] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz),
> > (N/A, 3000 mBm), (N/A) [   11.17] cfg80211:   (517 KHz -
> > 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2300 mBm), (N/A)
> > [   11.18] cfg80211:   (525 KHz - 533 KHz @ 8 KHz,
> > 16 KHz AUTO), (N/A, 2300 mBm), (0 s) [   11.19] cfg80211:
> > (549 KHz - 573 KHz @ 16 KHz), (N/A, 2300 mBm), (0 s)
> > [   11.20] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz),
> > (N/A, 3000 mBm), (N/A) [   11.21] cfg80211:   (5724 KHz -
> > 6372 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) ...
> > [   19.92] cfg80211: Calling CRDA for country: DE
> > [   19.94] cfg80211: Regulatory domain changed to country: DE
> > [   19.95] cfg80211:  DFS Master region: ETSI [   19.95]
> > cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain,
> > max_eirp), (dfs_cac_time) [   19.96] cfg80211:   (240 KHz -
> > 2483000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [   19.97]
> > cfg80211:   (515 KHz - 525 KHz @ 8 KHz, 20 KHz
> > AUTO), (N/A, 2000 mBm), (N/A) [   19.98] cfg80211:   (525
> > KHz - 535 KHz @ 8 KHz, 20 KHz AUTO), (N/A, 2000 mBm),
> > (0 s) [   19.99] cfg80211:   (547 KHz - 5725000 KHz @
> > 16 KHz), (N/A, 2700 mBm), (0 s) [   20.00] cfg80211:
> > (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 4000 mBm),
> > (N/A)  
> 
> One can easily see region changing from 'unset' over 'FCC' to 'ETSI'.
> 
> With current LEDE, however, these messages are completely missing,
> making it harder to trust radio obeying regulatory rules.  I mean,
> what is the rationale for this change (as well as that subject of the
> other mail)?

With yesterday's LEDE snapshot, it looks like regulatory messages are
back. Not quite the same, but similar:

> [8.960274] ath: EEPROM regdomain: 0x0
> [8.960293] ath: EEPROM indicates default country code should be used
> [8.960303] ath: doing EEPROM country->regdmn map search
> [8.960325] ath: country maps to regdmn code: 0x3a
> [8.960336] ath: Country alpha2 being used: US
> [8.960346] ath: Regpair used: 0x3a
> [8.972638] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> [8.977433] ieee80211 phy0: Atheros AR9340 Rev:2 mem=0xb810, irq=47
> [8.984380] PCI: Enabling device :00:00.0 ( -> 0002)
> [8.995580] ath: EEPROM regdomain: 0x0
> [8.995597] ath: EEPROM indicates default country code should be used
> [8.995608] ath: doing EEPROM country->regdmn map search
> [8.995629] ath: country maps to regdmn code: 0x3a
> [8.995640] ath: Country alpha2 being used: US
> [8.995650] ath: Regpair used: 0x3a
> [9.005211] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
> [9.010033] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb000, irq=40
>   [...]
> [   16.942415] ath: EEPROM regdomain: 0x8114
> [   16.946491] ath: EEPROM indicates we should expect a country code
> [   16.952718] ath: doing EEPROM country->regdmn map search
> [   16.958107] ath: country maps to regdmn code: 0x37
> [   16.962977] ath: Country alpha2 being used: DE
> [   16.967487] ath: Regpair used: 0x37
> [   16.971028] ath: regdomain 0x8114 dynamically updated by user
>

Re: [LEDE-DEV] regulatory domain information

2016-11-18 Thread Charles 
on 2016-10-19 Charles wrote:

Sorry to bother you again with this, but it looks like there's only 1
out of 3 questions answered so far.  Here are some updates on my
observations:

> on a TP-Link WDR3600 v1 (dual-band wifi, ath9k, wireless settings are
> attached below, most notably wireless.radioX.country=DE), the output
> of command 'iw reg get' is
> 
> with OpenWrt 15.05.1:
> 
> country DE: DFS-ETSI
>   (2400 - 2483 @ 40), (N/A, 20), (N/A)
>   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
>   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
>   (5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS
>   (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> 
> and with current LEDE:
> 
> global
> country DE: DFS-ETSI
>   (2400 - 2483 @ 40), (N/A, 20), (N/A)
>   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
>   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>   (5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS
>   (5725 - 5875 @ 80), (N/A, 14), (N/A)
>   (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> 
> phy#1
> country US: DFS-FCC
>   (2402 - 2472 @ 40), (N/A, 30), (N/A)
>   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
>   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
>   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
>   (5735 - 5835 @ 80), (N/A, 30), (N/A)
>   (57240 - 63720 @ 2160), (N/A, 40), (N/A)
> 
> phy#0
> country US: DFS-FCC
>   (2402 - 2472 @ 40), (N/A, 30), (N/A)
>   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
>   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
>   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
>   (5735 - 5835 @ 80), (N/A, 30), (N/A)
>   (57240 - 63720 @ 2160), (N/A, 40), (N/A)
> 
> global
> country DE: DFS-ETSI
>   (2400 - 2483 @ 40), (N/A, 20), (N/A)
>   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
>   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>   (5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS
>   (5725 - 5875 @ 80), (N/A, 14), (N/A)
>   (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> 
> Questions:
> 
> 1. Why does LEDE show four regulatory domain blocks while OpenWrt shows
>only one?

The last 'global' section is not shown by 'iw reg get' with yesterday's
LEDE snapshot anymore, but that's still two more 'FCC' sections than in
OpenWrt 15.05.1. Are these changes related to LEDE or upstream?


> 2. What does the "country US: DFS-FCC" blocks tell me when radio is set
>to an ETSI region country (DE) according to uci?
> 
> 3. What does AUTO-BW mean?
> 
> tnx, Charles
> 
> 
> $uci export wireless
> 
> config wifi-device 'radio0'
>   option type 'mac80211'
>   option channel '11'
>   option hwmode '11g'
>   option path 'platform/ar934x_wmac'
>   option htmode 'HT20'
>   option country 'DE'
> 
> config wifi-iface
>   option device 'radio0'
>   option network 'lan'
>   option mode 'ap'
>   option ssid 'OpenWrt'
>   option encryption 'none'
> 
> config wifi-device 'radio1'
>   option type 'mac80211'
>   option hwmode '11a'
>   option path 'pci:00/:00:00.0'
>   option htmode 'HT20'
>   option country 'DE'
>   option channel '36'
> 
> config wifi-iface
>   option device 'radio1'
>   option network 'lan'
>   option mode 'ap'
>   option ssid 'OpenWrt'
>   option encryption 'none'




___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] regulatory domain information

2016-11-06 Thread Charles 
on 2016-10-24 Charles wrote:

> on 2016-10-24 Felix Fietkau wrote:
> 
> > On 2016-10-19 23:31, Charles wrote:  
> > > 
> > > Questions:
> > > 
> > > 1. Why does LEDE show four regulatory domain blocks while OpenWrt shows
> > >only one?
> > This was added in Linux upstream. LEDE uses a newer version of mac80211.  
> 
> OK.  Problem is, iw as a moving target seems not to be too well
> documented.  Any recommended readings related to how iw reg output
> should to be interpreted?
> 
> 
> > > 3. What does AUTO-BW mean?
> > It means maximum channel bandwidth is determined by the available
> > frequency range.  
> 
> Thanks!  Is that what AVM FritzBoxes call wireless coexistence?  Can't
> see the relation to regulation, which is rather about primary and
> secondary users /not coexisting/.  Well, as I said, some more iw
> documentation could help understanding (Linux) wireless better.

Think I got this one (at least).  Regulation is about /not
coexisting/ on the same channel while AUTO-BW is about coexistence on
neighbouring channels (within the same band).


> > > 2. What does the "country US: DFS-FCC" blocks tell me when radio is set
> > >to an ETSI region country (DE) according to uci?
> > Please try the latest version from my staging tree at:
> > https://git.lede-project.org/?p=lede/nbd/staging.git;a=summary  
> 
> Oh, I'm not a developer, but building custom images with the image
> generator so far.  With the recent enabling of IPv6 in the kernel so
> that it cannot be disabled by removing some packages in the image
> generator, I do have a need to switch to compiling images anyway.  Will
> report back (and more problems) when I have kept up with that.  Thanks
> again!

Not yet there with mastering buildroot, sorry, but since I've seen
f78405f landing in the repository -- which I think is the commit you were
referring to -- I did try out a current nightly build (2016-11-05).  But
I can't observe any change in 'iw reg get' output (and I'm still not
sure if iw is telling me wifi is obeying FCC rules or ETSI rules).

tnx, Charles



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] regulatory domain information

2016-10-24 Thread Charles 
on 2016-10-24 Felix Fietkau wrote:

> On 2016-10-19 23:31, Charles wrote:
> > 
> > Questions:
> > 
> > 1. Why does LEDE show four regulatory domain blocks while OpenWrt shows
> >only one?  
> This was added in Linux upstream. LEDE uses a newer version of mac80211.

OK.  Problem is, iw as a moving target seems not to be too well
documented.  Any recommended readings related to how iw reg output
should to be interpreted?


> > 3. What does AUTO-BW mean?  
> It means maximum channel bandwidth is determined by the available
> frequency range.

Thanks!  Is that what AVM FritzBoxes call wireless coexistence?  Can't
see the relation to regulation, which is rather about primary and
secondary users /not coexisting/.  Well, as I said, some more iw
documentation could help understanding (Linux) wireless better.


> > 2. What does the "country US: DFS-FCC" blocks tell me when radio is set
> >to an ETSI region country (DE) according to uci?  
> Please try the latest version from my staging tree at:
> https://git.lede-project.org/?p=lede/nbd/staging.git;a=summary

Oh, I'm not a developer, but building custom images with the image
generator so far.  With the recent enabling of IPv6 in the kernel so
that it cannot be disabled by removing some packages in the image
generator, I do have a need to switch to compiling images anyway.  Will
report back (and more problems) when I have kept up with that.  Thanks
again!

Charles



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] regulatory domain information

2016-10-24 Thread Felix Fietkau 
On 2016-10-19 23:31, Charles wrote:
> Hello,
> 
> on a TP-Link WDR3600 v1 (dual-band wifi, ath9k, wireless settings are
> attached below, most notably wireless.radioX.country=DE), the output
> of command 'iw reg get' is
> 
> with OpenWrt 15.05.1:
> 
> country DE: DFS-ETSI
>   (2400 - 2483 @ 40), (N/A, 20), (N/A)
>   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
>   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
>   (5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS
>   (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> 
> and with current LEDE:
> 
> global
> country DE: DFS-ETSI
>   (2400 - 2483 @ 40), (N/A, 20), (N/A)
>   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
>   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>   (5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS
>   (5725 - 5875 @ 80), (N/A, 14), (N/A)
>   (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> 
> phy#1
> country US: DFS-FCC
>   (2402 - 2472 @ 40), (N/A, 30), (N/A)
>   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
>   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
>   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
>   (5735 - 5835 @ 80), (N/A, 30), (N/A)
>   (57240 - 63720 @ 2160), (N/A, 40), (N/A)
> 
> phy#0
> country US: DFS-FCC
>   (2402 - 2472 @ 40), (N/A, 30), (N/A)
>   (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
>   (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
>   (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
>   (5735 - 5835 @ 80), (N/A, 30), (N/A)
>   (57240 - 63720 @ 2160), (N/A, 40), (N/A)
> 
> global
> country DE: DFS-ETSI
>   (2400 - 2483 @ 40), (N/A, 20), (N/A)
>   (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
>   (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>   (5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS
>   (5725 - 5875 @ 80), (N/A, 14), (N/A)
>   (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> 
> Questions:
> 
> 1. Why does LEDE show four regulatory domain blocks while OpenWrt shows
>only one?
This was added in Linux upstream. LEDE uses a newer version of mac80211.

> 2. What does the "country US: DFS-FCC" blocks tell me when radio is set
>to an ETSI region country (DE) according to uci?
Please try the latest version from my staging tree at:
https://git.lede-project.org/?p=lede/nbd/staging.git;a=summary

> 3. What does AUTO-BW mean?
It means maximum channel bandwidth is determined by the available
frequency range.

- Felix

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] regulatory domain information

2016-10-23 Thread Charles 
on 2016-10-19 Charles wrote:

> Questions:
> 
> 1. Why does LEDE show four regulatory domain blocks while OpenWrt shows
>only one?
> 
> 2. What does the "country US: DFS-FCC" blocks tell me when radio is set
>to an ETSI region country (DE) according to uci?
> 
> 3. What does AUTO-BW mean?

If this is the wrong place to ask regulation related questions, could
you please point me to a better one?  Where is upstream - iw, driver or
kernel?

tnx, Charles



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] regulatory domain information

2016-10-20 Thread Charles 
on 2016-10-19 Charles wrote:

> Questions:

A similar observation: With OpenWrt 15.05.1, after booting, dmesg
output contains driver messages related to regulatory domain
changes and final (I hope) settings:

> [   10.85] cfg80211: Calling CRDA to update world regulatory domain
> [   10.88] cfg80211: World regulatory domain updated:
> [   10.88] cfg80211:  DFS Master region: unset
> [   10.89] cfg80211:   (start_freq - end_freq @ bandwidth), 
> (max_antenna_gain, max_eirp), (dfs_cac_time)
> [   10.90] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 
> 2000 mBm), (N/A)
> [   10.91] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz, 92000 KHz 
> AUTO), (N/A, 2000 mBm), (N/A)
> [   10.92] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 
> 2000 mBm), (N/A)
> [   10.92] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
> AUTO), (N/A, 2000 mBm), (N/A)
> [   10.93] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
> AUTO), (N/A, 2000 mBm), (0 s)
> [   10.94] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 
> 2000 mBm), (0 s)
> [   10.95] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 
> 2000 mBm), (N/A)
> [   10.96] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 
> 0 mBm), (N/A)
> ...
> [   11.14] cfg80211: Calling CRDA for country: US
> [   11.14] cfg80211: Regulatory domain changed to country: US
> [   11.15] cfg80211:  DFS Master region: FCC
> [   11.15] cfg80211:   (start_freq - end_freq @ bandwidth), 
> (max_antenna_gain, max_eirp), (dfs_cac_time)
> [   11.16] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 
> 3000 mBm), (N/A)
> [   11.17] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
> AUTO), (N/A, 2300 mBm), (N/A)
> [   11.18] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
> AUTO), (N/A, 2300 mBm), (0 s)
> [   11.19] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 
> 2300 mBm), (0 s)
> [   11.20] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 
> 3000 mBm), (N/A)
> [   11.21] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 
> 4000 mBm), (N/A)
> ...
> [   19.92] cfg80211: Calling CRDA for country: DE
> [   19.94] cfg80211: Regulatory domain changed to country: DE
> [   19.95] cfg80211:  DFS Master region: ETSI
> [   19.95] cfg80211:   (start_freq - end_freq @ bandwidth), 
> (max_antenna_gain, max_eirp), (dfs_cac_time)
> [   19.96] cfg80211:   (240 KHz - 2483000 KHz @ 4 KHz), (N/A, 
> 2000 mBm), (N/A)
> [   19.97] cfg80211:   (515 KHz - 525 KHz @ 8 KHz, 20 KHz 
> AUTO), (N/A, 2000 mBm), (N/A)
> [   19.98] cfg80211:   (525 KHz - 535 KHz @ 8 KHz, 20 KHz 
> AUTO), (N/A, 2000 mBm), (0 s)
> [   19.99] cfg80211:   (547 KHz - 5725000 KHz @ 16 KHz), (N/A, 
> 2700 mBm), (0 s)
> [   20.00] cfg80211:   (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 
> 4000 mBm), (N/A)

One can easily see region changing from 'unset' over 'FCC' to 'ETSI'.

With current LEDE, however, these messages are completely missing,
making it harder to trust radio obeying regulatory rules.  I mean, what
is the rationale for this change (as well as that subject of the other
mail)?

tnx, Charles



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev