Kernel/iwd
3
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-11-02 18:19:23 +01:00
Code Releases Activity
7b98a6ed9c
iwd/autotests/testFT-FILS/connection_test.py

167 lines
6.4 KiB
Python
Raw Normal View History

auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
#! /usr/bin/python3
import unittest
import sys, os
sys.path.append('../util')
from iwd import IWD
from iwd import NetworkType
auto-t: prepare autotests for test-runner re-write The tests basically remained the same with a few minor changes. The wiphy_map and in turn hostapd_map are no longer used. This was already partially converted a long time ago when the 'config' parameter was added to HostapdCLI. This patch fully converts all autotests to use 'config' rather than looking up by interface. Some test scripts were named 'test.py' which was fine before but the new rewrite actually loads each python test as a module. The name 'test' is too ambiguous and causes issues due to a native python module with the same name. All of these files were renamed to 'connection_test.py'.
2020-09-11 01:12:22 +02:00
from hostapd import HostapdCLI
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
import testutil
class Test(unittest.TestCase):
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
def validate_connection(self, wd):
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
device = wd.list_devices(1)[0]
condition = 'not obj.scanning'
wd.wait_for_object_condition(device, condition)
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
# Scanning is unavoidable in this case since both FILS-SHA256 and
# FILS-SHA384 are tested. Without a new scan the cached scan results
# would cause IWD to choose an incorrect AKM for the second test.
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
device.scan()
condition = 'obj.scanning'
wd.wait_for_object_condition(device, condition)
condition = 'not obj.scanning'
wd.wait_for_object_condition(device, condition)
ordered_network = device.get_ordered_network('TestFT')
self.assertEqual(ordered_network.type, NetworkType.eap)
self.assertFalse(self.bss_hostapd[0].list_sta())
self.assertFalse(self.bss_hostapd[1].list_sta())
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
device.connect_bssid(self.bss_hostapd[0].bssid)
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
auto-t: replace waiting for network with device Many tests waited on the network object 'connected' property after issuing a Connect command. This is not correct as 'connected' is set quite early in the connection process. The correct way of doing this is waiting for the device state to change to connected. This common code was replaced, hopefully putting to rest any random failures that happen occasionally.
2020-09-14 23:02:33 +02:00
condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_condition(device, condition)
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
self.assertTrue(self.bss_hostapd[0].list_sta())
self.assertFalse(self.bss_hostapd[1].list_sta())
testutil.test_iface_operstate(device.name)
testutil.test_ifaces_connected(self.bss_hostapd[0].ifname, device.name)
self.assertRaises(Exception, testutil.test_ifaces_connected,
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
(self.bss_hostapd[1].ifname, device.name, True, True))
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
device.disconnect()
condition = 'not obj.connected'
wd.wait_for_object_condition(ordered_network.network_object, condition)
ordered_network = device.get_ordered_network('TestFT')
self.assertEqual(ordered_network.type, NetworkType.eap)
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
# TODO: verify FILS was actually used on this second connection
device.connect_bssid(self.bss_hostapd[0].bssid)
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
auto-t: replace waiting for network with device Many tests waited on the network object 'connected' property after issuing a Connect command. This is not correct as 'connected' is set quite early in the connection process. The correct way of doing this is waiting for the device state to change to connected. This common code was replaced, hopefully putting to rest any random failures that happen occasionally.
2020-09-14 23:02:33 +02:00
condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_condition(device, condition)
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
self.assertTrue(self.bss_hostapd[0].list_sta())
self.assertFalse(self.bss_hostapd[1].list_sta())
testutil.test_iface_operstate(device.name)
testutil.test_ifaces_connected(self.bss_hostapd[0].ifname, device.name)
self.assertRaises(Exception, testutil.test_ifaces_connected,
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
(self.bss_hostapd[1].ifname, device.name, True, True))
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
# Check that iwd starts transition to BSS 1 in less than 10 seconds.
# The 10 seconds is longer than needed to scan on just two channels
# but short enough that a full scan on the 2.4 + 5.8 bands supported
# by mac80211_hwsim will not finish. If this times out then, but
# device_roam_trigger_cb has happened, it probably means that
# Neighbor Reports are broken.
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
#rule0.signal = -8000
device.roam(self.bss_hostapd[1].bssid)
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
condition = 'obj.state == DeviceState.roaming'
auto-t: Increase all test timeouts Slower systems may not be able to make some timeouts that tests mandated. All timeouts were increased significantly to allow tests to pass on slow systems.
2020-09-11 01:12:37 +02:00
wd.wait_for_object_condition(device, condition)
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
# Check that iwd is on BSS 1 once out of roaming state and doesn't
# go through 'disconnected', 'autoconnect', 'connecting' in between
auto-t: update roaming tests with wait_for_object_change Every single roaming test had one of two problems with watching the state change between roaming --> connected. Either the test used wait_for_object_condition to wait for 'connected' which could allow other states in between. Or it simply used an assert. The assert wouldn't allow other state changes, but at the cost of potentially failing due to IWD not having made it to the 'connected' state yet. Now we have wait_for_object_change which takes two conditions: initial (from_str) and expected (to_str). This API will not allow any other conditions except these, and will wait for the expected condition before continuing. This allows roaming test to reliably wait for the roaming --> connected state change.
2021-02-05 20:06:37 +01:00
from_condition = 'obj.state == DeviceState.roaming'
to_condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_change(device, from_condition, to_condition)
auto-t: replace waiting for network with device Many tests waited on the network object 'connected' property after issuing a Connect command. This is not correct as 'connected' is set quite early in the connection process. The correct way of doing this is waiting for the device state to change to connected. This common code was replaced, hopefully putting to rest any random failures that happen occasionally.
2020-09-14 23:02:33 +02:00
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
self.assertTrue(self.bss_hostapd[1].list_sta())
testutil.test_iface_operstate(device.name)
testutil.test_ifaces_connected(self.bss_hostapd[1].ifname, device.name)
self.assertRaises(Exception, testutil.test_ifaces_connected,
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
(self.bss_hostapd[0].ifname, device.name, True, True))
def test_fils_ft_roam_sha256(self):
wd = IWD(True)
self.bss_hostapd[0].set_value('wpa_key_mgmt', 'FT-EAP FILS-SHA256 FT-FILS-SHA256')
self.bss_hostapd[0].reload()
self.bss_hostapd[0].wait_for_event("AP-ENABLED")
self.bss_hostapd[1].set_value('wpa_key_mgmt', 'FT-EAP FILS-SHA256 FT-FILS-SHA256')
self.bss_hostapd[1].reload()
self.bss_hostapd[1].wait_for_event("AP-ENABLED")
self.validate_connection(wd)
def test_fils_ft_roam_sha384(self):
wd = IWD(True)
self.bss_hostapd[0].set_value('wpa_key_mgmt', 'FT-EAP FILS-SHA384 FT-FILS-SHA384')
self.bss_hostapd[0].reload()
self.bss_hostapd[0].wait_for_event("AP-ENABLED")
self.bss_hostapd[1].set_value('wpa_key_mgmt', 'FT-EAP FILS-SHA384 FT-FILS-SHA384')
self.bss_hostapd[1].reload()
self.bss_hostapd[1].wait_for_event("AP-ENABLED")
self.validate_connection(wd)
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
def tearDown(self):
os.system('ifconfig "' + self.bss_hostapd[0].ifname + '" down')
os.system('ifconfig "' + self.bss_hostapd[1].ifname + '" down')
os.system('ifconfig "' + self.bss_hostapd[0].ifname + '" up')
os.system('ifconfig "' + self.bss_hostapd[1].ifname + '" up')
@classmethod
def setUpClass(cls):
os.system('ifconfig lo up')
IWD.copy_to_storage('TestFT.8021x')
auto-t: updated autotests to use hwsim.get_radio This removes all the duplicated code where the interfaces are iterated and the radio/hostapd instances are created. Instead the two new APIs are used to get each instance, e.g.: hapd = HostapdCLI(config='ssid.conf') radio = hwsim.get_radio('radX')
2019-06-11 18:25:54 +02:00
cls.bss_hostapd = [ HostapdCLI(config='ft-eap-ccmp-1.conf'),
HostapdCLI(config='ft-eap-ccmp-2.conf') ]
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
# Set interface addresses to those expected by hostapd config files
os.system('ifconfig "' + cls.bss_hostapd[0].ifname +
'" down hw ether 12:00:00:00:00:01 up')
os.system('ifconfig "' + cls.bss_hostapd[1].ifname +
'" down hw ether 12:00:00:00:00:02 up')
cls.bss_hostapd[0].reload()
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
cls.bss_hostapd[0].wait_for_event("AP-ENABLED")
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
cls.bss_hostapd[1].reload()
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
cls.bss_hostapd[1].wait_for_event("AP-ENABLED")
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
# Fill in the neighbor AP tables in both BSSes. By default each
# instance knows only about current BSS, even inside one hostapd
# process.
# FT still works without the neighbor AP table but neighbor reports
# have to be disabled in the .conf files
cls.bss_hostapd[0].set_neighbor('12:00:00:00:00:02', 'TestFT',
'1200000000028f0000005102060603000000')
cls.bss_hostapd[1].set_neighbor('12:00:00:00:00:01', 'TestFT',
'1200000000018f0000005101060603000000')
@classmethod
def tearDownClass(cls):
IWD.clear_storage()
auto-t: release radio/hostapd instances from cls The cls object is part of the unittest framework and its lifespan is out of test-runner's control. Setting objects into the cls object sometimes keeps those objects around longer than desired. Its best to unset anything set in cls when the test is tore down.
2021-02-25 23:00:54 +01:00
cls.bss_hostapd = None
auto-t: combine testFT-FILS* tests This combines the SHA256 and SHA384 tests into one, as well as utilizes the new connect_bssid() and roam() APIs for much faster test execution.
2021-08-12 22:22:01 +02:00
#cls.bss_radio = None
auto-t: FILS-FT autotest
2019-05-23 00:24:05 +02:00
if __name__ == '__main__':
unittest.main(exit=True)
Copy Permalink