This website requires JavaScript.
Explore
Help
Sign In
Kernel
/
iwd
Watch
3
Star
0
Fork
0
You've already forked iwd
mirror of
https://git.kernel.org/pub/scm/network/wireless/iwd.git
synced
2024-12-28 12:12:32 +01:00
Code
Releases
Activity
2e55e00662
iwd
/
autotests
/
testNetconfig
/
hw.conf
11 lines
102 B
Plaintext
Raw
Normal View
History
Unescape
Escape
auto-t: add netconfig autotest Tests that DHCP using IWD's internal netconfig functions properly. The actual IP address assignment is not verified, but since IWD does not signal the connection as successful unless DHCP succeeds we can assume it was successful by checking that the device is connected. The process of actually starting dhcpd and configuring the interfaces is quite simple so it was left in the autotest itself. If (or when) more tests require IP capabilities (p2p, FILS, etc) this could be moved into test-runner itself and be made common. The reason I did not put it in there now is a) because this is the only test and b) more complex DHCP cases are likely to develop and may require more than this simplistic setup (like multiple APs/interfaces)
2020-09-16 02:00:22 +02:00
[SETUP]
auto-t: add static netconfig test Tests netconfig with a static configuration, as well as tests ACD functionality. The test has two IWD radios which will eventually use the same IP. One is configured statically, one will receive the IP via DHCP. The static client sets its IP first and begins using it. Then the DHCP client is started. Since ACD in a DHCP client is configured to use its address indefinitely, the static client *should* give up its address.
2020-12-10 22:22:10 +01:00
num_radios=3
start_iwd=0
hwsim_medium=no
auto-t: add netconfig autotest Tests that DHCP using IWD's internal netconfig functions properly. The actual IP address assignment is not verified, but since IWD does not signal the connection as successful unless DHCP succeeds we can assume it was successful by checking that the device is connected. The process of actually starting dhcpd and configuring the interfaces is quite simple so it was left in the autotest itself. If (or when) more tests require IP capabilities (p2p, FILS, etc) this could be moved into test-runner itself and be made common. The reason I did not put it in there now is a) because this is the only test and b) more complex DHCP cases are likely to develop and may require more than this simplistic setup (like multiple APs/interfaces)
2020-09-16 02:00:22 +02:00
[HOSTAPD]
rad0=ssidTKIP.conf
auto-t: add static netconfig test Tests netconfig with a static configuration, as well as tests ACD functionality. The test has two IWD radios which will eventually use the same IP. One is configured statically, one will receive the IP via DHCP. The static client sets its IP first and begins using it. Then the DHCP client is started. Since ACD in a DHCP client is configured to use its address indefinitely, the static client *should* give up its address.
2020-12-10 22:22:10 +01:00
[NameSpaces]
ns0=rad2
Copy Permalink
