After the successful onboarding of your first sensor, you will have access to the dashboard. If you want to gain a meaningful view of your Dashboard, you need to customize your configuration.
How many networks can the sensor test?
Currently, we limit this to 4 networks (including at least 1 SSID) as the sensor needs to test each network independently one after the other. The sensor will disassociate from one network, associate to the next network, and run the full set of tests.
Set-up Wireless SSIDs and Wired Ethernet from the network settings page.
When ethernet is configured on the sensor, it tries to connect to the ethernet > wifi > mobile and will use the first available connection to connect to the cloud.
The wired or wireless config will first need to be added to the dashboard
Here one can add SSID or ethernet configuration(total of 4 networks).
Once added the user then needs to go to the sensor settings page to add this config to the sensor.
On the sensor config page, click "Add Sensor" or edit an existing sensor config.
SSID Security Specifics
We support 3 types of security configurations:
Open - is a open SSID with no authentication or it could be captive portal authentication
Passphrase - This option can be used for SSIDs that have PSK authentication
Enterprise - We support the following authentication methods for Enterprise SSIDs as per the below screenshot.
Disabling external connectivity suppresses any errors related to external connectivity and prevents external tests from being executed.
Band locking can help with the following use cases:
Benchmarking the performance of 2.4 GHz vs. 5 GHz over time
Understanding whether specific issues are affecting the 2.4 GHz band, such as high channel utilization
How Can I Set up Band Locking?
Under NETWORKS > Wireless > Create a new SSID and give the SSID an Alias ending with the band you would like to test.E.g. SSID = AT-GuestàAlias = Guest-2.4GHz
Click on Advanced > Band Locking and move the slider from Auto to 2.4, Click Save.
Use the same steps to band lock to 5 GHz.
From the Sensor Management page, you can select a particular sensor > open in edit mode> add the SSID and select the Alias you created for 2.4 (Guest - 2.4GHz). Add the SSID again and select the Alias you created for 5 GHz (Guest - 5GHz) and click Save.
Note: sometimes the AP will force you to join 5GHz, so it advisable to disable band steering mode on the AP if you want to test band steering
Automatic Proxy Configuration
We support auto or manual proxy configuration. In networks where complex proxy rules are maintained through common Proxy Auto Configuration (PAC) files, we have added support for the Web Proxy Auto-Discovery Protocol (WPAD). Our platform is now able to retrieve the PAC file on the network using WPAD, from a URL, or by manually uploading it. Uploaded files to have UTF-8 encoding. You can read more about it in the release article. Furthermore, we also support for NTLM proxy authentication. If you have needed your sensor to authenticate against a proxy server that requires NTLM, this is now possible on wired and wireless networks.
You can also set proxies up at a network level. You can send in man in the middle (MITM) certificates for an SSID via email@example.com. The support team will open a case and someone from engineering will add the MITM certificate to the SSID, so all sensors testing the SSID will trust it.
Once you are satisfied with your wired and wireless configuration, you need to go and apply the changes to your sensors by going to the sensors tab.
SSID Aliasing: https://help.capenetworks.com/en/articles/1947194-ssid-aliasing
BSSID Locking: https://help.capenetworks.com/en/articles/1926943-bssid-locking
Below are links to the rest of the onboarding series:
1. Getting Started
3. Onboarding - Sensor Grouping and Hierarchy
4. Onboarding - Testing
5. Onboarding - Thresholds
6. Onboarding - Alerts
7. Onboarding - Company
8. Onboarding Dashboard Troubleshooting