hnyman
November 7, 2021, 8:15am
41
Well, we use automatics since the commit below, and all those values get calculated from the SSID etc.
committed 09:19AM - 18 May 18 UTC
Use ft_psk_generate_local=1 by default, as it makes everything else fairly
trivi… al. All of the r0kh/r1kh and key management stuff goes away and hostapd
fairly much does it all for us.
We do need to provide nas_identifier, which can be derived from the BSSID,
and we need to generate a mobility_domain, for which we default to the first
four chars of the md5sum of the SSID.
The complex manual setup should also still work, but the defaults also
now work easily out of the box. Verified by manually running hostapd
(with the autogenerated config) and watching the debug output:
wlan2: STA ac:37:43:a0:a6:ae WPA: FT authentication already completed - do not start 4-way handshake
This was previous submitted to LEDE in
https://github.com/lede-project/source/pull/1382
[dwmw2: Rewrote commit message]
Signed-off-by: Gospod Nassa <devianca@gmail.com>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Note that instead of automatics, I explicitly used mobility domain 2222, which is byte-symmetrical in case there is possibly bigendian/littleendian trouble between different routers, like pondered in
Hi,
I am new user of openwrt and this looks grate software.
I am trying to join openwrt box on existing 802.11r network by CISCO WAP series.
FT seems not to work properly from cisco's log.
I capture beacon frame of both box and found that openwrt's mobility domain swaps byte order.
My mobility domain is 10000 as decimal and 0x2710 as hex.
CISCO sends it as little endian and wireshark recognize as 0x2710.
OpenWRT sends it as big endian and wireshark recognize as 0x1027.
Which endian is tr…