Hi!
I tried this patch and at works as expected. Thank you very much!
André
Am 07.10.21 um 00:27 schrieb David Bauer:
> The existing wnm_disassoc_imminent ubus method only supports issuing a
> bss transition request with the disassoc imminent flag set.
> For use-cases, where the client is reque
Hi,
> right now luci will force 2
nope, it will not. It calculates the dynamic default according to the logic in
hostapd.sh and will remove the value from uci if the selected user value
matches the dynamic default [1].
So with WPA3 selected and choosing 11w ...
... required -> remove option iee
Am 11.10.21 um 19:40 schrieb Henrique de Moraes Holschuh via openwrt-devel:
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by th
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On 11/10/2021 14:14, Jo-Philipp W
Hi,
> Doesn't that downgrade PSK-SAE which the user configured to be with
> mandatory MFP to now only have optional MFP?
yes. The way I read it, it also prevents using the WPA3 protocol without
obligatory MFP (afair some users use that for limited drivers)
~ Jo
signature.asc
Description: Ope
On Mon, Oct 11, 2021 at 02:16:14PM +0200, John Crispin wrote:
> WPA3 modes require 11w to be set to optional/required. Using set_default would
> allow forcing an invalid value from UCI.
>
> Signed-off-by: John Crispin
> ---
> package/network/services/hostapd/files/hostapd.sh | 4 ++--
> 1 file c
Currently netifd only knows 2 wpa3/eap modes, wpa3 and wpa3-mixed.
Accoring to the spec there are however 3 mode, wpa3, wpa3-192 and wpa3-mixed.
In addition the mode currently called "incorrectly" setups up wpa3-192 and there
is no wpa3(-only) mode.
Fix the handler script s.T. hostap.sh can then p
WPA3 modes require 11w to be set to optional/required. Using set_default would
allow forcing an invalid value from UCI.
Signed-off-by: John Crispin
---
package/network/services/hostapd/files/hostapd.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/network/servic
Currently netifd only knows 2 wpa3/eap modes, wpa3 and wpa3-mixed.
Accoring to the spec there are however 3 mode, wpa3, wpa3-192 and wpa3-mixed.
In addition the mode currently called "incorrectly" setups up wpa3-192 and there
is currently no wpa3(-only) mode.
Fix hostapd.sh s.T. the now corretly p
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On 2021-10-11 10:31, Bjoern Frank
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On 2021-10-11 10:31, Bjoern Frank
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Add support for SAM9X60-EK board.
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Add support for SAMA5D27 WLSOM1-EK
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Add support for SAMA5D2 ICP board.
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Bump at91 targets to kernel v5.10.
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Enable kernel config for SAM9X60.
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Enable specific sam9x kernel confi
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi,
This series adds support for
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi,
is there any chance of gett
On Sunday, 10 October 2021 14:53:13 CEST Sven Eckelmann wrote:
[...]
> Since there are most likely more devices out there which use mtdparts, I
> would
> guess that there might already be a strategy out there which can be used to
> define the nvmem-provider for mtdparts defined partitions. At le
20 matches
Mail list logo
