On 05/03/2025 09:58, Chen-Yu Tsai wrote:
On Wed, Mar 5, 2025 at 4:23 PM <rmandrad@xxxxxxxxx> wrote:
That is not specifying NO-IR which basically is denying any 6Ghz in the US what it means in my opinion is
Client devices (like phones, tablets, laptops) need to find Wi-Fi networks before they can join them.
One-way devices do this is by sending out probe requests. These are little "Are you there?" signals that ask nearby access points (routers) to respond, so the device knows which networks are available.
Section 122 says: The Commission therefore only permits a client
device to send a probe request to an access point after it has
detected a transmission from the access point. The client device
will be required to send the probe request on the same frequency
as the access point's transmission.
I think this translates to "passive scanning only", which is what
NO_IR is meant to specify. NO-IR was previously called PASSIVE-SCAN,
and was renamed when it was merged with NO-IBSS.
Maybe the kernel's implementation needs work? I'm not a WiFi person so
I really don't know all the details.
That is why drivers use the non 6Ghz for allowing clients to identify the router has 6ghz capabilities… I don’t think is for wireless-regdb to take over the HW router compliance and certification which is what 122. is about
No, section 122 is definitely about client devices, which is what Linux
devices are.
No, Linux also supports access point, IBSS, OBSS and mesh, not to
mention monitor injection.
If you remove NO-IR, you are allowing Linux to create access points,
ad-hoc and mesh networks on the channel without conditions.
