public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen May <steffen.may@posteo.de>
To: linux-wireless@vger.kernel.org
Subject: nl80211: missing minimum TX power attribute causes misleading userspace behavior
Date: Thu, 09 Apr 2026 08:05:34 +0000	[thread overview]
Message-ID: <9ec6fd0b1c7392fce8c913a46c1b197e@posteo.de> (raw)


This issue was discovered during the analysis of two documented OpenWrt 
bugs. Bug 1 is a type comparison error in LuCI wireless.js that causes 0 
dBm to be displayed incorrectly. Bug 2 is in ucode mac80211.sh where the 
value 0 is treated as falsy, causing the router to transmit at maximum 
power instead. Both bugs are proven and reported.

During verification of Bug 2 on five devices with three different 
chipsets, it became apparent that the hardware floor is device-dependent 
and completely unknown to the stack. This is not a bug but a missing 
feature.

Because the floor is unknown, iwinfo generates selection lists 
containing values that have no real effect on the actual output power. 
Userspace accepts configurations such as 0 dBm even though the hardware 
cannot apply them. The system reports success while the hardware remains 
at its minimum supported level. This creates false assumptions.

Measurements

The deviation between the requested transmit power and the actual 
hardware floor is not constant but depends on the hardware:

Device                Chipset            Requested     Actual floor   
Difference
Buffalo WZR-600DHP    Atheros AR7161     1 dBm         3 dBm          +2 
dB
TP-Link Archer C7     Qualcomm QCA9558   1 dBm         5 dBm          +4 
dB
OpenWrt One           MTK Filogic        1 dBm         1 dBm           0 
dB
Cudy WR3000           MTK Filogic        1 dBm         1 dBm           0 
dB
GL.iNet GL-MT6000     MTK Filogic        1 dBm         1 dBm           0 
dB

Concrete example: Buffalo WZR-600DHP with Atheros AR7161

Because the system does not know the actual floor, the list generated by 
iwinfo contains values with no real effect:

0 dBm (1 mW)  reported, hardware remains at floor
1 dBm (1 mW)  reported, no actual reduction
2 dBm (1 mW)  reported, no actual reduction
3 dBm (1 mW)  actual hardware floor
4 dBm (2 mW)  first real power step above the floor

Proposed solution

Introduction of a new nl80211 attribute NL80211_ATTR_WIPHY_TX_POWER_MIN. 
nl80211 already exposes the maximum transmit power. Minimum and maximum 
are both fixed hardware properties -- it is inconsistent that only one 
of the two values is available.

No patch is provided. This mail is intended to describe the problem and 
to encourage interest in an implementation.

             reply	other threads:[~2026-04-09  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  8:05 Steffen May [this message]
2026-04-09 15:27 ` nl80211: missing minimum TX power attribute causes misleading userspace behavior Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2026-04-10  6:55 May

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ec6fd0b1c7392fce8c913a46c1b197e@posteo.de \
    --to=steffen.may@posteo.de \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox