Temporarily change bgscan threshold in MultiSwitchBack

server/site_tests/network_WiFiRoaming/003SSIDMultiSwitchBack

Index: server/site_tests/network_WiFiRoaming/003SSIDMultiSwitchBack
diff --git a/server/site_tests/network_WiFiRoaming/003SSIDMultiSwitchBack b/server/site_tests/network_WiFiRoaming/003SSIDMultiSwitchBack
index 4bbf44bb7d4d4944ec80c02391d7ae51bde59312..e810257d57197b219c126efde9af7e2f68fe6f86 100644
--- a/server/site_tests/network_WiFiRoaming/003SSIDMultiSwitchBack
+++ b/server/site_tests/network_WiFiRoaming/003SSIDMultiSwitchBack
@@ -10,10 +10,18 @@
 
     [ "config",         { "channel":"2412", "mode":"11g", "pureg":None } ],
 
+    # TODO(pstew): This is a very arbitrary limit based on the testbed
+    # characteristics (expected signal and noise, as well as the range
+    # of transmit power from the AP).
+    [ "bgscan_set",     { "signal":"-40" }],

[Sam Leffler, 2011/04/07 19:08:06]

maybe this belongs in the config file and set outside the tests?

[Paul Stewart, 2011/04/07 21:16:00]

This is just a setup so that the "low signal" alert triggers reliably when I
vary the transmit power on the AP.  I don't think (yet) that this is widely
applicable to other tests than this one.  Changing the comment to be more
explicit.

+
     # Connect to the first AP.
     [ "connect",        { "security":"none" } ],
     [ "client_ping",    { "count":"10" } ],
 
+    # Once the connection is up, restore the profile values to flimflam default
+    [ "bgscan_set",     { "reset":None }],
+
     # Create a second AP at the same time on the 5GHz radio, Channel 48
     [ "config",         { "channel":"5240", "ht40-":None, "puren":None,
                           "multi_interface":None } ],