Kernel/iwd
3
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-11-09 05:29:23 +01:00
Code Releases Activity
908dff807e
iwd/autotests/testPSK-roam/connection_test.py

203 lines
7.5 KiB
Python
Raw Normal View History

autotests: Add FT roaming test and utility functions This tests the FT-PSK initial Mobility Domain authentication, neighbor reports, scanning on a subset of frequencies and FT transition.
2017-03-26 03:16:57 +02:00
#! /usr/bin/python3
import unittest
import sys, os
sys.path.append('../util')
import iwd
from iwd import IWD
from iwd import PSKAgent
from iwd import NetworkType
from hwsim import Hwsim
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: Test communication when iwd reports connected Test that the AP interface and the station interface managed by iwd can actually send and receive ethernet traffic when iwd is in the connected state. Due to linux routing none of the high level utilities like ping or arping can be easily used to test communication between two interfaces of the same machine so use a method based on the mac80211_hwsim/tools/hwsim_test.c utility in the wpa_supplicant tree that uses a raw socket to inject unicast and broadcast frames. Add this check in three tests of different security type connections that simulate a single AP, and the two roaming tests with two APs. Check that the station can't communicate with the other AP's interface.
2017-05-22 10:49:47 +02:00
import testutil
autotests: Add FT roaming test and utility functions This tests the FT-PSK initial Mobility Domain authentication, neighbor reports, scanning on a subset of frequencies and FT transition.
2017-03-26 03:16:57 +02:00
class Test(unittest.TestCase):
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
def validate_connection(self, wd, over_ds=False):
auto-t: removed ';' from many autotests At some point a stray ';' got added into an autotest in a section of code that is heavily copy pasted. So in turn nearly all the autotests have this stray ';' after list_devices (and a few in other places).
2018-12-14 20:15:26 +01:00
device = wd.list_devices(1)[0]
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
condition = 'not obj.scanning'
wd.wait_for_object_condition(device, condition)
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
# Scanning is unavoidable in this case since several hostapd
# configurations are tested and changed mid-test
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +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)
auto-t: update tests to use get_ordered_network call
2018-12-14 20:15:28 +01:00
ordered_network = device.get_ordered_network('TestFT')
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
self.assertEqual(ordered_network.type, NetworkType.psk)
autotests: Add FT roaming test and utility functions This tests the FT-PSK initial Mobility Domain authentication, neighbor reports, scanning on a subset of frequencies and FT transition.
2017-03-26 03:16:57 +02:00
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
condition = 'not obj.connected'
wd.wait_for_object_condition(ordered_network.network_object, condition)
self.assertFalse(self.bss_hostapd[0].list_sta())
self.assertFalse(self.bss_hostapd[1].list_sta())
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
device.connect_bssid(self.bss_hostapd[0].bssid)
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
auto-t: fix testFT-PSK-roam Switched around hwsim rules with the IWD initializer to avoid IWD periodically scanning before hwsim rules are in place. Removed some unneeded code during teardown.
2020-09-11 01:12:47 +02:00
condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_condition(device, condition)
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
self.assertTrue(self.bss_hostapd[0].list_sta())
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
# list_sta actually reports any authenticated stations. Due to the
# nature of FT-over-DS IWD should authenticate to all stations with
# the same mobility domain. This means both APs should show our station.
if over_ds:
self.assertTrue(self.bss_hostapd[1].list_sta())
else:
self.assertFalse(self.bss_hostapd[1].list_sta())
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
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: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
(self.bss_hostapd[1].ifname, device.name, True, True))
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
auto-t: block auth frames for FT-over-DS test The FT-over-DS test was allowed to fail as it stood. If FT-over-DS failed it would just do a normal over-Air transition which satisfied all the checks. To prevent this Authenticate frames are blocked after the initial connection so if FT-over-DS fails there is no other way to roam.
2021-09-29 00:36:06 +02:00
if over_ds:
self.rule0.enabled = True
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
device.roam(self.bss_hostapd[1].bssid)
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +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)
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +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)
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +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)
autotests: Test communication when iwd reports connected Test that the AP interface and the station interface managed by iwd can actually send and receive ethernet traffic when iwd is in the connected state. Due to linux routing none of the high level utilities like ping or arping can be easily used to test communication between two interfaces of the same machine so use a method based on the mac80211_hwsim/tools/hwsim_test.c utility in the wpa_supplicant tree that uses a raw socket to inject unicast and broadcast frames. Add this check in three tests of different security type connections that simulate a single AP, and the two roaming tests with two APs. Check that the station can't communicate with the other AP's interface.
2017-05-22 10:49:47 +02:00
self.assertRaises(Exception, testutil.test_ifaces_connected,
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
(self.bss_hostapd[0].ifname, device.name, True, True))
autotests: Test communication when iwd reports connected Test that the AP interface and the station interface managed by iwd can actually send and receive ethernet traffic when iwd is in the connected state. Due to linux routing none of the high level utilities like ping or arping can be easily used to test communication between two interfaces of the same machine so use a method based on the mac80211_hwsim/tools/hwsim_test.c utility in the wpa_supplicant tree that uses a raw socket to inject unicast and broadcast frames. Add this check in three tests of different security type connections that simulate a single AP, and the two roaming tests with two APs. Check that the station can't communicate with the other AP's interface.
2017-05-22 10:49:47 +02:00
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
device.roam(self.bss_hostapd[0].bssid)
auto-t: add FT-back to original AP on FT-PSK-roam
2021-04-30 20:20:36 +02:00
condition = 'obj.state == DeviceState.roaming'
wd.wait_for_object_condition(device, condition)
# Check that iwd is on BSS 0 once out of roaming state and doesn't
# go through 'disconnected', 'autoconnect', 'connecting' in between
from_condition = 'obj.state == DeviceState.roaming'
to_condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_change(device, from_condition, to_condition)
self.assertTrue(self.bss_hostapd[0].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: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
(self.bss_hostapd[1].ifname, device.name, True, True))
def test_ft_psk(self):
wd = IWD(True)
self.bss_hostapd[0].set_value('wpa_key_mgmt', 'FT-PSK')
self.bss_hostapd[0].set_value('ft_over_ds', '0')
auto-t: set ocv on PSK FT test
2021-09-28 17:46:56 +02:00
self.bss_hostapd[0].set_value('ocv', '1')
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
self.bss_hostapd[0].reload()
self.bss_hostapd[0].wait_for_event("AP-ENABLED")
self.bss_hostapd[1].set_value('wpa_key_mgmt', 'FT-PSK')
self.bss_hostapd[1].set_value('ft_over_ds', '0')
auto-t: set ocv on PSK FT test
2021-09-28 17:46:56 +02:00
self.bss_hostapd[0].set_value('ocv', '1')
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
self.bss_hostapd[1].reload()
self.bss_hostapd[1].wait_for_event("AP-ENABLED")
self.validate_connection(wd)
def test_ft_psk_over_ds(self):
wd = IWD(True)
self.bss_hostapd[0].set_value('wpa_key_mgmt', 'FT-PSK')
self.bss_hostapd[0].set_value('ft_over_ds', '1')
auto-t: set ocv on PSK FT test
2021-09-28 17:46:56 +02:00
self.bss_hostapd[0].set_value('ocv', '1')
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
self.bss_hostapd[0].reload()
self.bss_hostapd[0].wait_for_event("AP-ENABLED")
self.bss_hostapd[1].set_value('wpa_key_mgmt', 'FT-PSK')
self.bss_hostapd[1].set_value('ft_over_ds', '1')
auto-t: set ocv on PSK FT test
2021-09-28 17:46:56 +02:00
self.bss_hostapd[1].set_value('ocv', '1')
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
self.bss_hostapd[1].reload()
self.bss_hostapd[1].wait_for_event("AP-ENABLED")
self.validate_connection(wd, over_ds=True)
def test_reassociate_psk(self):
wd = IWD(True)
self.bss_hostapd[0].set_value('wpa_key_mgmt', 'WPA-PSK')
self.bss_hostapd[0].set_value('ft_over_ds', '0')
self.bss_hostapd[0].reload()
self.bss_hostapd[0].wait_for_event("AP-ENABLED")
self.bss_hostapd[1].set_value('wpa_key_mgmt', 'WPA-PSK')
self.bss_hostapd[1].set_value('ft_over_ds', '0')
self.bss_hostapd[1].reload()
self.bss_hostapd[1].wait_for_event("AP-ENABLED")
self.validate_connection(wd)
auto-t: add FT-back to original AP on FT-PSK-roam
2021-04-30 20:20:36 +02:00
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
def tearDown(self):
autotests: Restore AP beacons after timeout in testFT-PSK-roam In the beacon loss test try to simulate a periodic communication problem because we don't support roaming if the AP goes away completely. 2 seconds seems to be enough to consistently trigger the beacon_loss event without triggering a disconnect by the linux kernel or hiding the AP from the roam scan. Also set the RSSI for that AP lower so that it is not reselected by iwd.
2017-08-23 18:18:50 +02:00
os.system('ifconfig "' + self.bss_hostapd[0].ifname + '" down')
os.system('ifconfig "' + self.bss_hostapd[1].ifname + '" down')
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
os.system('ifconfig "' + self.bss_hostapd[0].ifname + '" up')
os.system('ifconfig "' + self.bss_hostapd[1].ifname + '" up')
autotests: Add FT roaming test and utility functions This tests the FT-PSK initial Mobility Domain authentication, neighbor reports, scanning on a subset of frequencies and FT transition.
2017-03-26 03:16:57 +02:00
auto-t: block auth frames for FT-over-DS test The FT-over-DS test was allowed to fail as it stood. If FT-over-DS failed it would just do a normal over-Air transition which satisfied all the checks. To prevent this Authenticate frames are blocked after the initial connection so if FT-over-DS fails there is no other way to roam.
2021-09-29 00:36:06 +02:00
self.rule0.enabled = False
autotests: Add FT roaming test and utility functions This tests the FT-PSK initial Mobility Domain authentication, neighbor reports, scanning on a subset of frequencies and FT transition.
2017-03-26 03:16:57 +02:00
@classmethod
def setUpClass(cls):
auto-t: block auth frames for FT-over-DS test The FT-over-DS test was allowed to fail as it stood. If FT-over-DS failed it would just do a normal over-Air transition which satisfied all the checks. To prevent this Authenticate frames are blocked after the initial connection so if FT-over-DS fails there is no other way to roam.
2021-09-29 00:36:06 +02:00
hwsim = Hwsim()
auto-t: use connect_bssid/roam APIs in testFT-PSK-roam This also adds FT-over-DS into this test, as well as a reassociation test for good measure.
2021-08-12 22:22:04 +02:00
IWD.copy_to_storage('TestFT.psk')
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
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-psk-ccmp-1.conf'),
HostapdCLI(config='ft-psk-ccmp-2.conf') ]
auto-t: block auth frames for FT-over-DS test The FT-over-DS test was allowed to fail as it stood. If FT-over-DS failed it would just do a normal over-Air transition which satisfied all the checks. To prevent this Authenticate frames are blocked after the initial connection so if FT-over-DS fails there is no other way to roam.
2021-09-29 00:36:06 +02:00
rad2 = hwsim.get_radio('rad2')
cls.rule0 = hwsim.rules.create()
cls.rule0.source = rad2.addresses[0]
cls.rule0.bidirectional = True
cls.rule0.signal = -2000
cls.rule0.prefix = 'b0'
cls.rule0.drop = True
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +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: Restructure FT-PSK-roam to be like other FT roam tests
2021-05-21 19:33:23 +02:00
cls.bss_hostapd[0].wait_for_event("AP-ENABLED")
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +02:00
cls.bss_hostapd[1].reload()
auto-t: Restructure FT-PSK-roam to be like other FT roam tests
2021-05-21 19:33:23 +02:00
cls.bss_hostapd[1].wait_for_event("AP-ENABLED")
autotests: Add test for roam triggered by beacon loss The two tests in test.py are similar except for the way that the roaming is triggered.
2017-08-14 14:31:22 +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')
autotests: Add FT roaming test and utility functions This tests the FT-PSK initial Mobility Domain authentication, neighbor reports, scanning on a subset of frequencies and FT transition.
2017-03-26 03:16:57 +02:00
@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 FT roaming test and utility functions This tests the FT-PSK initial Mobility Domain authentication, neighbor reports, scanning on a subset of frequencies and FT transition.
2017-03-26 03:16:57 +02:00
if __name__ == '__main__':
unittest.main(exit=True)
Copy Permalink