iwd/autotests/testSAE/hw.conf

[SETUP]
num_radios=4
start_iwd=0
hwsim_medium=yes

[HOSTAPD]
rad0=ssidSAE.conf
rad1=ssidSAE-H2E.conf
rad2=ssidSAE-default-group.conf
auto-t: added test for SAE 2018-08-13 16:25:49 -07:00			`[SETUP]`
auto-t: Add test for new SAE default group behavior Tests the 3 possible options to UseDefaultEccGroup behave as expected: - When not provided use the "auto" behavior. - When false, always use higher order groups - When true, always use default group 2024-02-27 10:34:04 -08:00			`num_radios=4`
auto-t: added test for SAE 2018-08-13 16:25:49 -07:00			`start_iwd=0`
auto-t: make hwsim registration off by default With the addition of connect_bssid/roam very few tests actually require hwsim. Since hwsim can lead to problems with scan results its best to have it off by default and have each test that needs it explicitly turn it on. Tests which previously turned it off have had that option removed. Tests that do require hwsim still are vulnerable to scan result problems, so for these tests beacon_int was added to the hostapd config which seems to help with reliability somewhat. 2021-08-12 13:38:10 -07:00			`hwsim_medium=yes`
auto-t: added test for SAE 2018-08-13 16:25:49 -07:00
			`[HOSTAPD]`
			`rad0=ssidSAE.conf`
auto-t: refactor/fix testSAE The SAE test made some assumptions on certain conditions due to there being no way of checking if those conditions were met Mainly the use of H2E/hunt-and-peck. We assumed that when we told hostapd to use H2E or hunt/peck it would but in reality it was not. Hostapd is apparently not very good at swapping between the two with a simple "reload" command. Once H2E is enabled it appears that it cannot be undone. Similarly the vendor elements seem to carry over from test to test, and sometimes not which causes unintended behavior. To fix this create separate APs for the specific scenario being tested: - Hunt and peck - H2E - Special vendor_element simulating buggy APs Another issue found was that if password identifies are used hostapd automatically chooses H2E which was not intented, at least based on the test names (in reality it wasn't causing any problems). The tests have also been improved to use hostapds "sta_status" command which contains the group number used when authenticating, so now that at least can be verified. 2024-02-27 10:34:03 -08:00			`rad1=ssidSAE-H2E.conf`
auto-t: Add test for new SAE default group behavior Tests the 3 possible options to UseDefaultEccGroup behave as expected: - When not provided use the "auto" behavior. - When false, always use higher order groups - When true, always use default group 2024-02-27 10:34:04 -08:00			`rad2=ssidSAE-default-group.conf`