3
0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-11-22 14:49:24 +01:00
iwd/autotests/testFT-FILS-SHA384
Denis Kenzior 8d8ea67da1 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-24 14:31:04 -05:00
..
connection_test.py auto-t: Change FT test cases to use start_iwd=0 2021-05-24 14:31:04 -05:00
ft-eap-ccmp-1.conf auto-t: use stand alone radius server for testFT-FILS-SHA384 2020-01-06 11:18:48 -06:00
ft-eap-ccmp-2.conf auto-t: use stand alone radius server for testFT-FILS-SHA384 2020-01-06 11:18:48 -06:00
hw.conf auto-t: Change FT test cases to use start_iwd=0 2021-05-24 14:31:04 -05:00
main.conf treewide: Use CamelCase for [Scan] settings 2019-10-24 15:58:08 -05:00
pwd.eap_user auto-t: FILS-FT autotest 2019-05-23 15:28:24 -05:00
radius.conf auto-t: use stand alone radius server for testFT-FILS-SHA384 2020-01-06 11:18:48 -06:00
TestFT.8021x auto-t: Rename setting Autoconnect to AutoConnect 2019-10-24 13:04:53 -05:00