[PATCH v5 8/8] auto-t: Disable MAC randomization for a few tests

The scan subsets now contains both 2.4GHz and 5GHz channels, this seems
to cause an issue when MAC randomization is used together with the
simulated hardware.

The AP(s) in these tests operate on 2.4GHz. From the logs it's clear
that the station's probe request to the 2.4GHz AP does arrive, and the
AP responds, but the station never processes the response. If the AP is
changed to 5GHz then everything works fine. I believe this is because
2.4GHz is scanned first, then there's a MAC change, then 5GHz is
scanned. For some reason, this causes the simulated hardware to miss the
response from the first scan, possibly because the MAC address doesn't
match.
---
 autotests/testAP-no-support/main.conf   | 2 ++
 autotests/testBasicServiceSet/main.conf | 2 ++
 autotests/testDPP/main.conf             | 2 ++
 autotests/testDisconnectByAP/main.conf  | 2 ++
 4 files changed, 8 insertions(+)

diff --git a/autotests/testAP-no-support/main.conf b/autotests/testAP-no-support/main.conf
new file mode 100644
index 00000000..9452fb6b
--- /dev/null
+++ b/autotests/testAP-no-support/main.conf
@@ -0,0 +1,2 @@
+[Scan]
+DisableMacAddressRandomization=true
diff --git a/autotests/testBasicServiceSet/main.conf b/autotests/testBasicServiceSet/main.conf
new file mode 100644
index 00000000..9452fb6b
--- /dev/null
+++ b/autotests/testBasicServiceSet/main.conf
@@ -0,0 +1,2 @@
+[Scan]
+DisableMacAddressRandomization=true
diff --git a/autotests/testDPP/main.conf b/autotests/testDPP/main.conf
new file mode 100644
index 00000000..9452fb6b
--- /dev/null
+++ b/autotests/testDPP/main.conf
@@ -0,0 +1,2 @@
+[Scan]
+DisableMacAddressRandomization=true
diff --git a/autotests/testDisconnectByAP/main.conf b/autotests/testDisconnectByAP/main.conf
new file mode 100644
index 00000000..9452fb6b
--- /dev/null
+++ b/autotests/testDisconnectByAP/main.conf
@@ -0,0 +1,2 @@
+[Scan]
+DisableMacAddressRandomization=true

-- 
2.39.5