WiFi interop lab needs to be resurrected. Below is a list of things that were done to get it going:
1. Analyze all existing 250+ APs in chaos chamber with a plan to remove older APs that matched the following criteria:
- APs that are EOL (end of line); no longer supported by the manufacturer
- APs that only support A/B/G and don't support N or AC
2. Plan the split of remaining ~190 APs across 3 RF chambers to get provide similar coverage across all chambers
3. Remove all APs from chaos lab
4. Install APs across 3 chambers per #2
5. Come up with configuration parameters for each AP in chaos chamber (chromeos3)
6. Reset and reconfigure all APs per new configurations
7. Update DHCP based on new AP install locations
8. Enable remote management on each AP to allow for making changes remotely as necessary during the bring up / testing phase
9. Update AP hostname -> RPM mapping to reflect new setup
10. Create new .conf file containing current set of APs with appropriate configurations
11. Create new control files to split the runs for all 2Ghz and 5Ghz channels
12. Make other necessary changes to the exiting code to get the new static setup working
Note - I may have missed some items that were necessary to get this going and most of the items listed above required multiple iterations and lots of testing.
Wifi interop lab will allow for testing ChromeOS DUTs against 50+ commercially sold APs across different channels/frequencies. All the APs are statically configured and this configuration is reflected in chaos_ap_list.conf file.
Due to the time it takes to test a given DUT against all APs (~3hrs) and the fact that we can only run the test on 1 DUT at a time (due to current design limitations), the plan is to split the test runs across different DUTs on different days such that the test(s) will be run on each DUT once per week.
We also plan to continue adding newer APs to the interop lab as needed.
Comment 1 by harpreet@chromium.org
, Nov 20