The Wi-Fi client can be built on a Rasberry PI system or similar. This device should be secure and should adhere to the security policies and requirements.
The Wi-Fi client should function in configurable Active mode and Passive/Listen only mode.
Active Mode:
The Wi-Fi cleint should be able to connect to all SSIDs with different security profiles including 802.1x,PSK, Open etc.
It should be able to send and execute traffic across various Test protocols.
It should be able to send Alerts, detect anomalies and send it north bound. The Alert thresholds should be configurable from the management platform.
The information from the Clients/Probes should be exposed via Rest/Web APIs to connect to a dashboard.
The dashboard should be able to provide historical and time sensitive metrics per location of deployment or at an aggregated level.
Passive Mode:
The probe should be able to sense the Wi-Fi packets and measure channel utilization across different channels. This might require the probe to sample across various frequencies.
Should be able to measure Noise floor, RSSI and other metrics. These metrics could be used to setup a baseline that could be used in the Dashboard to detect anomalies.
At the system level:
1. The Client should configurable to get an Ip address either statically or dynamically.
2. Data to the Cloud should be over a secure tunnel such as IPSEC.
3. The Client should be able to talk to a Test Traffic server from the management profile.
4. The portal should be able to detect any faults with the synthetic clients itself.
About the recuiterMember since May 20, 2018 Devendra Singh
from Camaguey, Cuba