iwd/autotests/testFT-FILS-SHA384/hw.conf

[SETUP]
num_radios=3
start_iwd=0

[HOSTAPD]
rad0=ft-eap-ccmp-1.conf
rad1=ft-eap-ccmp-2.conf
radius_server=radius.conf
auto-t: FILS-FT autotest 2019-05-23 00:24:05 +02:00			`[SETUP]`
			`num_radios=3`
auto-t: Change FT test cases to use start_iwd=0 These test cases depend on setting up the existing hostapd instance to a set of known addresses, which might be different from what test-runner sets. During this time, any scans might result in the old and the new addresses used by hostapd to be found in the scan results. Fix that by using start_iwd=0 which tells test_runner that the test wants to start iwd itself. This delays starting iwd until after the setUpClass routine has been called and hostapd configured properly. Also use more sensible rssi values for the 'non-preferred' bss. Otherwise, ranking BSSes by throughput can confuse the test logic since both BSSes are ranked the same and either can be picked by autoconnect. 2021-05-21 18:44:55 +02:00			`start_iwd=0`
auto-t: FILS-FT autotest 2019-05-23 00:24:05 +02:00
			`[HOSTAPD]`
			`rad0=ft-eap-ccmp-1.conf`
			`rad1=ft-eap-ccmp-2.conf`
auto-t: use stand alone radius server for testFT-FILS-SHA384 This fixes the test with recent hostapd versions 2019-12-30 19:09:54 +01:00			`radius_server=radius.conf`