lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e257568948a1af079275df1a904ae04805ead4c7.camel@sipsolutions.net>
Date:   Mon, 29 Nov 2021 09:34:53 +0100
From:   Johannes Berg <johannes@...solutions.net>
To:     Peter Seiderer <ps.report@....net>, Felix Fietkau <nbd@....name>
Cc:     linux-wireless@...r.kernel.org,
        "David S . Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: [RFC v2] mac80211: minstrel_ht: do not set RTS/CTS flag for
 fallback rates

On Fri, 2021-11-26 at 15:25 +0100, Peter Seiderer wrote:
> 
> > 
> > If you don't want this behavior, I'm fine with adding a way to
> > explicitly disable it. However, I do think leaving it on by default
> > makes sense.
> 
> I expected this (as otherwise the flag setting would not be there) ;-)
> 

To be fair, that setting (RTS threshold) has been there for 20 years or
more, and comes from a much simpler time when the reasoning for RTS/CTS
was mostly about hidden stations, not about protecting the transmissions
from older clients that don't understand the newer PHY protocols, etc.

johannes

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ