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-11-29 22:19:23 +01:00
Code
Releases
Activity
2e2f6f991d
iwd
/
autotests
/
testNetconfig
/
ap-ns1.conf
8 lines
82 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
hw_mode=g
channel=1
autotests: DHCPv4 renewal/resend test in testNetconfig Test that the DHCPv4 lease got renewed after the T1 timer runs out. Then also simulate the DHCPREQUEST during renew being lost and retransmitted and the lease eventually getting renewed T1 + 60s later. The main downside is that this test will inevitably take a while if running in Qemu without the time travel ability. Update the test and some utility code to run hostapd in an isolated net namespace for connection_test.py. We now need a second hostapd instance though because in static_test.py we test ACD and we need to produce an IP conflict. Moving the hostapd instance unexpectedly fixes dhcpd's internal mechanism to avoid IP conflicts and it would no longer assign 192.168.1.10 to the second client, it'd notice that address was already in use and assign the next free address, or fail if there was none. So add a second hostapd instance that runs in the main namespace together with the statically-configured client, it turns out the test relies on the kernel being unable to deliver IP traffic to interfaces on the same system.
2022-07-09 02:23:32 +02:00
ssid=ap-ns1
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
wpa=1
wpa_pairwise=TKIP
wpa_passphrase=secret123
Copy Permalink
