please change the two radios to the same country code when you try
please set country code to us and show the output of
iw phy0 info
iw phy1 info
just the terminal info, not luci
1 Like
both radios set to US
if there is a way to better format this text, please tell me, the output is very big
root@OpenWrt:~# iw phy0 info
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 1:
Capabilities: 0x1fe
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 2412 MHz [1] (8.0 dBm)
* 2417 MHz [2] (8.0 dBm)
* 2422 MHz [3] (8.0 dBm)
* 2427 MHz [4] (8.0 dBm)
* 2432 MHz [5] (8.0 dBm)
* 2437 MHz [6] (8.0 dBm)
* 2442 MHz [7] (8.0 dBm)
* 2447 MHz [8] (8.0 dBm)
* 2452 MHz [9] (8.0 dBm)
* 2457 MHz [10] (8.0 dBm)
* 2462 MHz [11] (8.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
valid interface combinations:
* #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 4,
total <= 4, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Supported extended features:
* [ RRM ]: RRM
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
root@OpenWrt:~#
root@OpenWrt:~# iw phy1 info
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2247 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 2:
Capabilities: 0x1ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x318001b0):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Frequencies:
* 5180 MHz [36] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5260 MHz [52] (23.0 dBm) (radar detection)
* 5280 MHz [56] (23.0 dBm) (radar detection)
* 5300 MHz [60] (23.0 dBm) (radar detection)
* 5320 MHz [64] (23.0 dBm) (radar detection)
* 5500 MHz [100] (21.0 dBm) (radar detection)
* 5520 MHz [104] (21.0 dBm) (radar detection)
* 5540 MHz [108] (21.0 dBm) (radar detection)
* 5560 MHz [112] (21.0 dBm) (radar detection)
* 5580 MHz [116] (21.0 dBm) (radar detection)
* 5600 MHz [120] (21.0 dBm) (radar detection)
* 5620 MHz [124] (21.0 dBm) (radar detection)
* 5640 MHz [128] (21.0 dBm) (radar detection)
* 5660 MHz [132] (21.0 dBm) (radar detection)
* 5680 MHz [136] (21.0 dBm) (radar detection)
* 5700 MHz [140] (21.0 dBm) (radar detection)
* 5745 MHz [149] (23.0 dBm)
* 5765 MHz [153] (23.0 dBm)
* 5785 MHz [157] (23.0 dBm)
* 5805 MHz [161] (23.0 dBm)
* 5825 MHz [165] (23.0 dBm)
valid interface combinations:
* #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 8,
total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Supported extended features:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
root@OpenWrt:~#
very strange, this is something about driver, firmware.
what kind of device, radio is that?
if you go up in the messages I specified and sent pictures, just saying so I dont make this too big sending again, but if you want I can do it.
here it is
and here
I think this is the device page
really, this is your problem, we try to solve your problem, and you cannot say a word? like I have a Mikrotik, I have a TP-Link, I have a Netgear ..........
sorry if I tried.
1 Like
...I was saying this - so that the law was not [possibly] violated while testing.
I don't understand what you mean
but thank you for the help.
it's midnight for me so I'm not really fresh, show the output of
uname -a
1 Like
I have no hurrys, if you need to go, go, I'am happy you helped me.
here it is
root@OpenWrt:~# uname -a
Linux OpenWrt 4.14.195 #0 SMP Sun Sep 6 16:19:39 2020 mips GNU/Linux
install a snapshot and you'll be ok, that is a mt76 device
2 Likes
just to clarify, I currently am in a house in the middle of nowhere (albeit with fiber optic internet), in the muddle of a valley, with my closes neighbor at 2km away, yeah, that does not change that I may have "broken the law", but I'm sure that no one was disturbed
I don't get what I stole.
"... or for breaking any other law."
thank you, I will try it tomorrow, hoping for success 
yes, very helpful, thank you. /s
If we can match them to the law regdb. Otherwise, there's nothing to discuss or understand mathematically. It's just basic science, math and law.
I'm not trying to be sarcastic, rude or mean...and I also said I'm search for the BR regulations. 
Just to be clear here, the authoritative source for evaluating the legal limits here would be wireless-regdb, OpenWrt can update it to a newer version if necessary, but won't modify it based on your claims or wishes. If you disagree with its values, you'll have to bring up your case upstream, just be prepared to discuss your case based on legal facts, as it will be questioned and cross-checked by developers and legal departments of several interested parties (foremost QCA, Intel and several distributions).
If you want to be constructive, it would be ideal to point them towards a recent change of regulation, rather than stomping your feet and disagreeing with the interpretation of existing regulatory settings - there's generally a reason how wireless-regdb came up with the current settings and reading into the finer details of (often-) overlapping laws isn't always easy.
OpenWrt tries to follow regulation as well as possible, discussions to actively breach your local laws is not welcome here.
4 Likes
Never was my intention to quote "stomp my feet". I do, yes, want to be constructive, that's why I asked what was the process for that to change, and yes, the regulations are muddy, therefore I won`t pursue this, because people with more knowledge on this area certainly will if it is really wrong, and my problem here was with my router, not regulations, something lleachii missed some ten times or so, and a grate user that joined latter solved very fast, in any case, my intentions are clear for anyone that read what I said, and my problem was actually with the router, and has been addresses, not with the regulations, and certainly not trying to bypass them, even if it is my personal belief that they are stupid, and they can, and should be questioned when different countries have different laws, more so when our institutions are corrupt and do not serve the people, as they should.
Also it became clear to me now, something that wasn't before - and that should be the main take away from this, and if this is marked as solved I asked that this be marked as the solution - the tx power limit is set by regdb, and openwrt simply uses it, something I thought was internal to openwrt before learning this fact, any problems with this (eg. someone thinking it is incorrect) should be treated directly with them, and consulting the limits they set is also easy, for those curious, and can also be done directly on openwrt (as i understand it) with the command iw reg get
As for openwrt and the community, I argue that in some way you could consider using this a breach of "norms" and maybe in some case the "law", as manufactures try to prohibit us to tinker with products that we, the consumer bought, and are then by definition ours, for those standing besides them as if they wore the holy texts, and nothing can questions them, I think civil disobedience is a fair and moral thing to do in these situations, and many of these products wouldn't be running openwrt without breaking TOS, and maybe other "agreements", so think twice what you stand by with such determination, laws are made by humans, and same as us, are fallible, and that's something that should never be forgotten, never forget, the apartheid was in fact legal.
1 Like
I was taught in school and in licensing courses not to alter radios to jam other people. This is international regulation unrelated to any single nation - radio wave can travel across borders and they do not need passports. If one alters a radio, it has to be tested and calibrated - you cannot simply "increase power" like most layperson believe. I wasn't taught that possibly jamming others possibly on band unrelated to WiFi was ethical, legal or being a good citizen - and hardly an act of civil disobedience. It could endanger lives!
In some countries, such alterations are a serious violation of military operations even - and you won't see civil authorities for violating it.
It's usually "people" - such as yourself - that are unaware of radio theory (not the law) and that they could actually jam everyone trying to use WiFi...or what's called a "harmonic frequency" totally unrelated to 2.4 or 5.4.
Social concepts must differ in South America.
I think you confuse Terms of Service with the law authorizing you to transmit on radio frequencies. I also think you forget the owner of a website can restrict the conversation as they please, including not allowing suggestions of violating the law - or making a non-official regdb.
but the problem here is not regdb, you can see that from iw phy.
1 Like