Kernel/iwd
3
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-11-29 13:59:24 +01:00
Code Releases Activity
bb604b92f1
iwd/autotests/testFT-8021x-roam/connection_test.py

99 lines
3.8 KiB
Python
Raw Normal View History

autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01: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
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
import testutil
class Test(unittest.TestCase):
def test_roam_success(self):
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
wd = IWD(True)
device = wd.list_devices(1)[0]
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
auto-t: update all tests to remove bad scanning logic This changes all tests to use the default get_ordered_network behavior rather than some custom or incorrect logic. Any use of scan_if_needed=True has been removed since this is now the default. Also any explicit scanning has been removed for tests which do not require it (where the default behavior is good enough).
2021-08-12 22:38:11 +02:00
ordered_network = device.get_ordered_network('TestFT')
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
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: update testFT-8021x-roam to use roam() API
2021-08-12 22:22:00 +02:00
device.connect_bssid(self.bss_hostapd[0].bssid)
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01: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)
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
auto-t: test-wide replacement of assertTrue(list_sta()) Any test using assertTrue(hostapd.list_sta()) improperly has been replaced with wait_for_event(). There were a few places where this was actually ok (i.e. IWD is already connected) but most needed to be changed since the check was just after IWD connected and hostapd's list_sta() API may not return a fully updated list.
2022-03-30 22:23:15 +02:00
self.bss_hostapd[0].wait_for_event('AP-STA-CONNECTED %s' % device.address)
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
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: update testFT-8021x-roam to use roam() API
2021-08-12 22:22:00 +02:00
(self.bss_hostapd[1].ifname, device.name, True, True))
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
auto-t: update testFT-8021x-roam to use roam() API
2021-08-12 22:22:00 +02:00
device.roam(self.bss_hostapd[1].bssid)
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01: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)
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01: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: test-wide replacement of assertTrue(list_sta()) Any test using assertTrue(hostapd.list_sta()) improperly has been replaced with wait_for_event(). There were a few places where this was actually ok (i.e. IWD is already connected) but most needed to be changed since the check was just after IWD connected and hostapd's list_sta() API may not return a fully updated list.
2022-03-30 22:23:15 +02:00
self.bss_hostapd[1].wait_for_event('AP-STA-CONNECTED %s' % device.address)
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
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: update testFT-8021x-roam to use roam() API
2021-08-12 22:22:00 +02:00
(self.bss_hostapd[0].ifname, device.name, True, True))
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
def tearDown(self):
auto-t: replace ifconfig with ip commands ifconfig has long been deprecated in favor of ip from iproute2. It is usually no longer installed by default.
2021-11-11 03:12:02 +01:00
os.system('ip link set "' + self.bss_hostapd[0].ifname + '" down')
os.system('ip link set "' + self.bss_hostapd[1].ifname + '" down')
os.system('ip link set "' + self.bss_hostapd[0].ifname + '" up')
os.system('ip link set "' + self.bss_hostapd[1].ifname + '" up')
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
@classmethod
def setUpClass(cls):
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') ]
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
# Set interface addresses to those expected by hostapd config files
auto-t: replace ifconfig with ip commands ifconfig has long been deprecated in favor of ip from iproute2. It is usually no longer installed by default.
2021-11-11 03:12:02 +01:00
os.system('ip link set dev "' + cls.bss_hostapd[0].ifname + '" down')
os.system('ip link set dev "' + cls.bss_hostapd[0].ifname + \
'" address 12:00:00:00:00:01 up')
os.system('ip link set dev "' + cls.bss_hostapd[1].ifname + '" down')
os.system('ip link set dev "' + cls.bss_hostapd[1].ifname + \
'" address 12:00:00:00:00:02 up')
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
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")
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01: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")
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01: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
autotests: Add a FT + 8021x roaming test
2018-03-21 07:15:31 +01:00
if __name__ == '__main__':
unittest.main(exit=True)
Copy Permalink