[LEDE-DEV] regulatory domain information

Charles charles2016 at firemail.at
Fri Nov 18 08:47:12 PST 2016


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.850000] cfg80211: Calling CRDA to update world regulatory
> > domain [   10.880000] cfg80211: World regulatory domain updated:
> > [   10.880000] cfg80211:  DFS Master region: unset
> > [   10.890000] cfg80211:   (start_freq - end_freq @ bandwidth),
> > (max_antenna_gain, max_eirp), (dfs_cac_time) [   10.900000]
> > cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000
> > mBm), (N/A) [   10.910000] cfg80211:   (2457000 KHz - 2482000 KHz @
> > 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [   10.920000]
> > cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000
> > mBm), (N/A) [   10.920000] cfg80211:   (5170000 KHz - 5250000 KHz @
> > 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [   10.930000]
> > cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz
> > AUTO), (N/A, 2000 mBm), (0 s) [   10.940000] cfg80211:   (5490000
> > KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
> > [   10.950000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz),
> > (N/A, 2000 mBm), (N/A) [   10.960000] cfg80211:   (57240000 KHz -
> > 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) ... [   11.140000]
> > cfg80211: Calling CRDA for country: US [   11.140000] cfg80211:
> > Regulatory domain changed to country: US [   11.150000] cfg80211:
> > DFS Master region: FCC [   11.150000] cfg80211:   (start_freq -
> > end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
> > [   11.160000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz),
> > (N/A, 3000 mBm), (N/A) [   11.170000] cfg80211:   (5170000 KHz -
> > 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A)
> > [   11.180000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz,
> > 160000 KHz AUTO), (N/A, 2300 mBm), (0 s) [   11.190000] cfg80211:
> > (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
> > [   11.200000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz),
> > (N/A, 3000 mBm), (N/A) [   11.210000] cfg80211:   (57240000 KHz -
> > 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) ...
> > [   19.920000] cfg80211: Calling CRDA for country: DE
> > [   19.940000] cfg80211: Regulatory domain changed to country: DE
> > [   19.950000] cfg80211:  DFS Master region: ETSI [   19.950000]
> > cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain,
> > max_eirp), (dfs_cac_time) [   19.960000] cfg80211:   (2400000 KHz -
> > 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [   19.970000]
> > cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz
> > AUTO), (N/A, 2000 mBm), (N/A) [   19.980000] cfg80211:   (5250000
> > KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm),
> > (0 s) [   19.990000] cfg80211:   (5470000 KHz - 5725000 KHz @
> > 160000 KHz), (N/A, 2700 mBm), (0 s) [   20.000000] cfg80211:
> > (57000000 KHz - 66000000 KHz @ 2160000 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=0xb8100000, irq=47
> [    8.984380] PCI: Enabling device 0000:00:00.0 (0000 -> 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=0xb0000000, 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
> [   16.976930] ath: EEPROM regdomain: 0x8114
> [   16.980994] ath: EEPROM indicates we should expect a country code
> [   16.987188] ath: doing EEPROM country->regdmn map search
> [   16.992587] ath: country maps to regdmn code: 0x37
> [   16.997442] ath: Country alpha2 being used: DE
> [   17.001958] ath: Regpair used: 0x37
> [   17.005496] ath: regdomain 0x8114 dynamically updated by user

Even though I'm still confused about FCC lines in 'iw reg get' output
(see other mail). So the same question, are these latter lines recently
introduced in LEDE or upstream?

Some background: I've happily noticed 'iw phy' in LEDE showing
channels affected by DFS /not/ flagged with 'no IR' (no initial
radiation, channels 52 upwards) anymore. Which I interpret as LEDE
is now able to operate in AP mode on all DFS channels, including the
ones with higher power limits (channels 104 upwards). I do need that
extra transmission power to compensate for a flaky Fresel zone on a
radio link (touching trees and a tin roof located in-between, no other
5 GHz wifi users, fortunately). Since I want to install APs on third
person's ground, I'd like to be double careful obeying regulatory
rules, though.

tnx, Charles





More information about the Lede-dev mailing list