Modify

Opened 5 years ago

Last modified 2 years ago

#12814 reopened defect

ar71xx/tl-wdr4300: doesn't use txpower above 14dBm

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: packages Version: Trunk
Keywords: Cc:

Description

Currently on r35147. Two tl-wdr4300 using WDS bridge on 5GHz band, each also used as 2.4GHz AP.

Even with txpower set in config/luci, it won't go above 14dBm on 5GHz, and 19dBm on 2.4GHz (atleast according to what luci tells me). With iwconfig gone, I don't really know how to read out txpower from console, iw apparently won't do. iw does however let me select txpower manually, but nothing happens.

I used to be able to run at much higher txpower earlier, 20dBm on 2.4 band and I think 17dBm on 5GHz band. regulatory does seem to allow using 20dBm on 5GHz band though, but luci wouldn't let me select it, and manually editing the configuration wouldn't make any difference.

Probably not cosmetic as I've noticed WiFi working poorly the last day or two.

[   28.210000] cfg80211: Calling CRDA for country: GR
[   28.220000] cfg80211: Regulatory domain changed to country: GR
[   28.230000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   28.230000] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   28.240000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   28.250000] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   28.260000] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
[25872.030000] ------------[ cut here ]------------
[25872.030000] WARNING: at /home/azx/openwrt/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2013-01-07/net/mac80211/driver-ops.h:12 0x871815cc()
[25872.050000] wlan1.sta1:  Failed check-sdata-in-driver check, flags: 0x2
[25872.060000] Modules linked in: ath79_wdt ohci_hcd ledtrig_usbdev ledtrig_netdev ip6t_REJECT ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah ip6table_raw ip6table_mangle ip6table_filter ip6_tables nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_irc nf_nat_ftp nf_conntrack_irc nf_conntrack_ftp ipt_MASQUERADE iptable_nat xt_nat nf_nat_ipv4 nf_nat pppoe xt_conntrack xt_CT iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppox ipt_REJECT xt_TCPMSS xt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base crc_ccitt ipv6 cfg80211(O) compat(O) arc4 ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O)
[25872.130000] Call Trace:[<8027b544>] 0x8027b544
[25872.140000] [<8027b544>] 0x8027b544
[25872.140000] [<80071624>] 0x80071624
[25872.140000] [<871815cc>] 0x871815cc
[25872.150000] [<800716d8>] 0x800716d8
[25872.150000] [<871815cc>] 0x871815cc
[25872.150000] [<8718ee70>] 0x8718ee70
[25872.160000] [<87195c60>] 0x87195c60
[25872.160000] [<87092a20>] 0x87092a20
[25872.160000] [<80094edc>] 0x80094edc
[25872.170000] [<80183af8>] 0x80183af8
[25872.170000] [<8021316c>] 0x8021316c
[25872.180000] [<802158ec>] 0x802158ec
[25872.180000] [<8021550c>] 0x8021550c
[25872.180000] [<801ee8f4>] 0x801ee8f4
[25872.190000] [<80215700>] 0x80215700
[25872.190000] [<80214cb8>] 0x80214cb8
[25872.190000] [<801ee8f4>] 0x801ee8f4
[25872.200000] [<801edea8>] 0x801edea8
[25872.200000] [<802156f0>] 0x802156f0
[25872.200000] [<8021499c>] 0x8021499c
[25872.210000] [<801ee904>] 0x801ee904
[25872.210000] [<802145ec>] 0x802145ec
[25872.220000] [<800b3378>] 0x800b3378
[25872.220000] [<80214a70>] 0x80214a70
[25872.220000] [<800b7a68>] 0x800b7a68
[25872.230000] [<801e3f7c>] 0x801e3f7c
[25872.230000] [<800e4180>] 0x800e4180
[25872.230000] [<80124870>] 0x80124870
[25872.240000] [<801e4bcc>] 0x801e4bcc
[25872.240000] [<800c85b8>] 0x800c85b8
[25872.240000] [<800c8a14>] 0x800c8a14
[25872.250000] [<8006b894>] 0x8006b894
[25872.250000] [<80171f7c>] 0x80171f7c
[25872.260000] [<800b42c0>] 0x800b42c0
[25872.260000] [<800b46ac>] 0x800b46ac
[25872.260000] [<801e6a48>] 0x801e6a48
[25872.270000] [<80069ae4>] 0x80069ae4
[25872.270000]
[25872.270000] ---[ end trace cd1c90614dea461e ]---
Wiphy phy1
        Band 1:
                Capabilities: 0x11ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-23
                Frequencies:
                        * 5180 MHz [36] (17.0 dBm)
                        * 5200 MHz [40] (17.0 dBm)
                        * 5220 MHz [44] (17.0 dBm)
                        * 5240 MHz [48] (17.0 dBm)
                        * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5600 MHz [120] (disabled)
                        * 5620 MHz [124] (disabled)
                        * 5640 MHz [128] (disabled)
                        * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5745 MHz [149] (disabled)
                        * 5765 MHz [153] (disabled)
                        * 5785 MHz [157] (disabled)
                        * 5805 MHz [161] (disabled)
                        * 5825 MHz [165] (disabled)
                Bitrates (non-HT):
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
        max # scan SSIDs: 4
        max scan IEs length: 2261 bytes
        Coverage class: 0 (up to 0m)
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP (00-0f-ac:4)
                * CMAC (00-0f-ac:6)
        Available Antennas: TX 0x7 RX 0x7
        Configured Antennas: TX 0x7 RX 0x7
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
        software interface modes (can always be added):
                 * AP/VLAN
                 * monitor
        valid interface combinations:
                 * #{ managed, WDS, P2P-client } <= 2048, #{ AP, mesh point, P2P-GO } <= 8, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * start_ap
                 * new_station
                 * new_mpath
                 * set_mesh_config
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * join_mesh
                 * remain_on_channel
                 * set_tx_bitrate_mask
                 * frame
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * tdls_mgmt
                 * tdls_oper
                 * probe_client
                 * set_noack_map
                 * register_beacons
                 * Unknown command (89)
                 * Unknown command (92)
                 * connect
                 * disconnect
        Supported TX frame types:
                 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * (null): 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
        Supported RX frame types:
                 * IBSS: 0x40 0xb0 0xc0 0xd0
                 * managed: 0x40 0xd0
                 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * mesh point: 0xb0 0xc0 0xd0
                 * P2P-client: 0x40 0xd0
                 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * (null): 0x40 0xd0
        Device supports RSN-IBSS.
        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
        Device supports TX status socket option.
        Device supports HT-IBSS.

Attachments (0)

Change History (15)

comment:1 Changed 5 years ago by Halo2

You can install wireless-tools for iwconfig beeing there.

But the old values were also not right!

I'm talking about WDR3600, so 2.4GHz is the same, but 5GHz has 2 instead of 3 chains, so maximum selectable values could be 3dB less there.

On channel 36 and 100 15 was the maximum setable, so beeing 12 on one chain.
On channel 104 19 was the maximum, so beeing 16 on one chain, but that resultet to 13 dBm.
12 led to 9.8dBm on 36, 9.2dBm on 100&104.
10 led to 8dBm on 36, 7dBm on 100/104.

On channel 1 20 was the maximum, so beeing 17 on one chain, but in reality it resultet to >21dBm.
12 led to >17dBm
10 to >16dBm.

Said that, i wonder why 19 is the limit on 2.4GHz now (because there was more possible).
But 5GHz propably really does not give much more output.
And hopefully the 2.4GHz values are more true now. So less performance could also result of getting what you set in contrast to before (if you're on 2.4).
But you will only really know that if measured i think. At least I haven't found any reliable txpower values by now. Even gone worse because getting none with iw. (And sometimes you need a reboot (i.e. when changing number of chains) to get refreshed values with iwconfig/iwlist. Currently the numbers in debugfs do not take chain numbers (or more) into account, so they are definitely no good)

comment:2 Changed 5 years ago by anonymous

I had a run with stock firmware to see if I'd get any better results and I could really tell a difference as I could now use 5GHz band in my kitchen again, something I haven't been able to do for some days.

Back on openwrt trunk things remain the same though. I did however try to change regulatory country to US, and now luci is displaying 17dBm on the WDS AP again. The WDS client on the other hand is still capped to 14dBm, even after testing US as regulatory setting there too.. I should also note that 5GHz coverage still seemed worse then stock firmware. Something strange going on here??

I did find the txpower values in debugfs (ieee80211), but they made no sense at all.

How are we supposed to get a realistic readout of txpower from console now? Where does luci find this information?

comment:3 Changed 5 years ago by anonymous

Additionally this is what luci shows with US as regulatory domain;

WDS AP
------
Channel: 36 (5.180 GHz) | Tx-Power: 17 dBm
Signal: -66 dBm | Noise: -95 dBm
Bitrate: 270.0 Mbit/s | Country: US
WDS client
----------
Channel: 36 (5.180 GHz) | Tx-Power: 14 dBm
Signal: -69 dBm | Noise: -95 dBm
Bitrate: 270.0 Mbit/s | Country: US

If setting regulatory country to GR, both devices will show Tx-Power: 14dBm.

Signal with AA-rc1 and earlier BB-trunk was (from my memory) around 56-60dBm. With latest trunks from last days, it's usually around 68-74. Noise is always steady at -95dBm with trunk, but in AA-rc1 noise used to be -88 to -89dBm.

Further I never see bitrates above 270-300mbps any more (I guess no triple stream, since MCS index never seems to be able to go above 15 due to poor signal). MCS index 22-23 (400-450mbps) used to be quite common before these problems.

Sadly I have no analyzer to give any hard evidence..

comment:4 Changed 5 years ago by anonymous

Problem is still around. Sometimes it actually seems to change to 17dBm briefly though, even without touching anything.. Currently on rev 35255.

Below is from WDS client. But it's the same on the WDS AP.

config wifi-device 'radio1'
        option type 'mac80211'
        option macaddr 'xx:xx:xx:xx:xx:xx'
        option hwmode '11na'
        list ht_capab 'LDPC'
        list ht_capab 'SHORT-GI-20'
        list ht_capab 'SHORT-GI-40'
        list ht_capab 'TX-STBC'
        list ht_capab 'RX-STBC1'
        list ht_capab 'DSSS_CCK-40'
        option txpower '17'
        option channel '36'
        option htmode 'HT40+'
        option noscan '1'
        option country 'GR'

config wifi-iface
        option device 'radio1'
        option network 'lan'
        option ssid 'mesa'
        option mode 'sta'
        option wds '1'
        option encryption 'psk2+ccmp'
        option key '12345678'
Mode: Client | SSID: xxxx
BSSID: xx:xx:xx:xx:xx:xx | Encryption: WPA2 PSK (CCMP)
Channel: 36 (5.180 GHz) | Tx-Power: 14 dBm
Signal: -68 dBm | Noise: -95 dBm
Bitrate: 270.0 Mbit/s | Country: GR
root@xxx:~# iwconfig wlan1
wlan1     IEEE 802.11an  ESSID:"mesa"
          Mode:Managed  Frequency:5.18 GHz  Access Point: xx:xx:x:x:xx:xx
          Bit Rate=270 Mb/s   Tx-Power=14 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=42/70  Signal level=-68 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
root@xxx:~# cat /sys/kernel/debug/ieee80211/phy1/power
17
root@xxx:~# iw reg get
country GR:
        (2402 - 2482 @ 40), (N/A, 20)
        (5170 - 5250 @ 40), (N/A, 20)
        (5250 - 5330 @ 40), (N/A, 20), DFS
        (5490 - 5710 @ 40), (N/A, 27), DFS

comment:5 Changed 5 years ago by anonymous

Today I noticed that if I set TX power to 16, luci and iwconfig shows TX power to be "5". and /sys/kernel/debug/ieee80211/phy1/power is 0.

comment:6 Changed 5 years ago by technozen

FWIW, I was also getting oscillating wifi drops on a tl-wdr3600 v1.0 (similar platform to wdr4300). Although my case is about 2.4 band, could be relevant.

Normally I tune wifi power DOWN to the MINIMUM that offers stable link at farthest point. WDR3600 even at max power had unstable wifi, regularly dropping clients. Much worse than older TL-WR1043ND (2.4 only) or a number of Buffalo routers, all pretty stable at the same location. But now fixed.

Troubleshooting with "inSSIDer" on laptop, and "WiFi Manager" on android.

Things I tried:

  • pretty much every channel => speed differences, yes, but no stability improvement
  • disable A radio => no improvement on 2.4 B/G/N band
  • trunk vs 12.09-rc1 => no improvement
  • openwrt/jffs2 vs stock fw => similar drops, plus stock hangs occasionally
  • b/g/n vs only g/n => (not enough testing)
  • squashfs vs jffs2 image => squashfs fewer drops, less jitter (cannot explain)
  • set to US, and reduce power => much better, wifi drops solved (radio chip bug?)

So try the squashfs build, set to US, and adjust your power for stability.

Trade-off: you lose two Euro channels 12,13 in 2.4 band (or three 12,13,14 in Japan). On A band there are many channels either way, so not an issue.

Now all my clients are ok, no more drops. Still looking into tuning matters :) but the main problem is gone.

comment:7 Changed 5 years ago by anonymous

Just to update, this problem is still around.

comment:8 Changed 5 years ago by anonymous

Still around, but what is actually the top hardware power output of the wdr4300?

comment:9 Changed 5 years ago by Gorby

Got the same issue on my Buffalo, discribed it here
https://dev.openwrt.org/ticket/13541#comment:16
Not as thoroughly as you, though. ;)

comment:10 Changed 4 years ago by winrootkit@…

my TL-WDR4300 has similar issues:
very disappointing as a German user, stock gets about 1.5-2.5times the range on both radios
i cannot set txpower any higher than this:

$iwlconfig
wlan1     IEEE 802.11an  Mode:Master  Tx-Power=14 dBm   
          RTS thr:off   Fragment thr:off
          Power Management:off
          
wlan0     IEEE 802.11bgn  Mode:Master  Tx-Power=19 dBm   
          RTS thr:off   Fragment thr:off
          Power Management:off
$iw reg get
country DE: DFS-UNSET
	(2400 - 2483 @ 40), (N/A, 20)
	(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
	(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
	(5470 - 5725 @ 40), (N/A, 27), DFS
$iw list
Wiphy phy1
	max # scan SSIDs: 4
	max scan IEs length: 2261 bytes
	Coverage class: 1 (up to 450m)
	Device supports RSN-IBSS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP (00-0f-ac:4)
		* CMAC (00-0f-ac:6)
	Available Antennas: TX 0x7 RX 0x7
	Configured Antennas: TX 0x7 RX 0x7
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * WDS
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
	Band 2:
		Capabilities: 0x11ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-23
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5180 MHz [36] (17.0 dBm)
			* 5200 MHz [40] (17.0 dBm)
			* 5220 MHz [44] (17.0 dBm)
			* 5240 MHz [48] (17.0 dBm)
			* 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5600 MHz [120] (disabled)
			* 5620 MHz [124] (disabled)
			* 5640 MHz [128] (disabled)
			* 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			  DFS state: usable (for 2149211 sec)
			* 5745 MHz [149] (disabled)
			* 5765 MHz [153] (disabled)
			* 5785 MHz [157] (disabled)
			* 5805 MHz [161] (disabled)
			* 5825 MHz [165] (disabled)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * remain_on_channel
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * tdls_mgmt
		 * tdls_oper
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * Unknown command (92)
		 * testmode
		 * connect
		 * disconnect
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	software interface modes (can always be added):
		 * AP/VLAN
		 * monitor
	valid interface combinations:
		 * #{ managed, WDS, P2P-client } <= 2048, #{ AP, mesh point, P2P-GO } <= 8, #{ IBSS } <= 1,
		   total <= 2048, #channels <= 1, STA/AP BI must match
		 * #{ AP } <= 1,
		   total <= 1, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 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
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports low priority scan.
	Device supports scan flush.
	Device supports AP scan.
Wiphy phy0
	max # scan SSIDs: 4
	max scan IEs length: 2257 bytes
	Coverage class: 1 (up to 450m)
	Device supports RSN-IBSS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP (00-0f-ac:4)
		* CMAC (00-0f-ac:6)
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * WDS
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
	Band 1:
		Capabilities: 0x11ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-15
		Bitrates (non-HT):
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
			* 2484 MHz [14] (disabled)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * remain_on_channel
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * tdls_mgmt
		 * tdls_oper
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * Unknown command (92)
		 * testmode
		 * connect
		 * disconnect
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	software interface modes (can always be added):
		 * AP/VLAN
		 * monitor
	valid interface combinations:
		 * #{ managed, WDS, P2P-client } <= 2048, #{ AP, mesh point, P2P-GO } <= 8, #{ IBSS } <= 1,
		   total <= 2048, #channels <= 1, STA/AP BI must match
		 * #{ AP } <= 1,
		   total <= 1, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 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
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports low priority scan.
	Device supports scan flush.
	Device supports AP scan.

comment:11 Changed 3 years ago by anonymous

Channels 36 and 44 with HT40 are considered edge-band channels since they're, well, on the edge. Therefore the power is apparently reduced further 3dBm to avoid out-of-band transmissions.

It's a shame since stock firmwares apparently do not follow this rule and transmit at full power regardless...

comment:12 Changed 3 years ago by nbd

please try current trunk

comment:13 Changed 3 years ago by nbd

  • Resolution set to no_response
  • Status changed from new to closed

comment:14 Changed 3 years ago by anonymous

  • Resolution no_response deleted
  • Status changed from closed to reopened

Yes, this problem still exists. But I don't think it can be fixed. Wireless output power has been 'unreliable' every since I got 6 of the units, occassionally on the 2.4GHz band, but the 5GHz band is the weirdest. I've seen all kind of results from a lot of experimenting. On current trunk, channel 40 will use 20dBm, channel 44, 15dBm and channel 36 at 17dBm. Regulatory settings, jows reghack and ATH_USER_REGD seems to have some influences on results. But in the end it's all about play the "settings game" till a somewhat desired result is achieved. Kernels and patches seems to have little effect, other than adding some "confusion" to how to get to the desired configuration result (channel/width/dBm/maxrate).

So I think it's harware/eeprom/ART related. And even if it could be overridden by clever hacking that would probably just mean regulatory/legal issues.

What do you think of this, developers?

comment:15 Changed 2 years ago by anonymous

This problem is still around.

Add Comment

Modify Ticket

Action
as reopened .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.