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
| ||
|
Message-ID: <bb69b031-53ad-4649-bd1d-e95ca7a0cc70@gmail.com> Date: Wed, 3 Aug 2016 11:51:09 +0900 From: Masashi Honma <masashi.honma@...il.com> To: Johannes Berg <johannes@...solutions.net> Cc: Yaniv Machani <yanivma@...com>, linux-kernel@...r.kernel.org, Meirav Kama <meiravk@...com>, "David S. Miller" <davem@...emloft.net>, linux-wireless@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template On 2016年08月02日 16:27, Johannes Berg wrote: > This explicitly configures *HT capability* though - that's even the > name of the parameter. If you enable HT40 in the capability, the > resulting BSS might still not actually *use* 40 MHz bandwidth, as > required by overlapping BSS detection. OK, I see. HT Capabilities element = Defined by hardware and software spec of the node. So it does not be modified after boot. HT Operation element = Defined by surrounding environment and configuration of the node. So it could be modified after boot. So, if the node supports HT40, HT Capabilities shows HT40 is capable. Now, I understand why you rejected this patch. But now, when disable_ht=1, no HT Capabilities element in beacon even though the node supports HT. My trailing patch could solve the issue. Masashi Honma.
Powered by blists - more mailing lists