Yes, the Wyebot dashboard not only identifies problems happening in your Wi-Fi environment in real-time, it also tells you how to resolve those problems.
To bring a Wyebot sensor online, it will need to be initially connected via ethernet, and powered via PoE or a power adapter. The sensor must receive DHCP and have access to the internet. Once it establishes a connection to our cloud servers, it will show as “Active” on your dashboard. For further reading, including troubleshooting tips and specific hostnames/ports read through the Getting Started Guide.
The recommended switch configuration can be found in this knowledge base article: Configuring Switch Ports for Wyebot Sensors.
Wi-Fi 6 also known as “AX Wi-Fi" or 802.11ax
Wi-Fi 5 also known as 802.11ac
Wi-Fi 6E is the designation for spectrum expansion into the 6GHz radio-frequency band under the Wi-Fi 6E standard.
Yes, there are two options for outdoor enclosures. One without a cooling fan and power outlet linked here, and one with a cooling fan and power outlet linked here.
Yes, Wyebot supports SSO integration via the SAML authentication standard. See our SAML Configuration Guide for step by step instructions.
The Wyebot solution is vendor agnostic so we are completely independent of any infrastructure equipment (Access Points and any other devices) or device types you have operating in your environment. Since we passively obtain our data directly from the RF/airwaves full time (24/7), we are not dependent on information contained in or available from specific vendors’ equipment (WLAN controller and or cloud dashboard). This is the primary differentiator in how we approach the solution.
The Wyebot sensor is a completely passive device out-of-the-box. Think of it as a microphone that is recording voice - the mic does not speak, it only records. Wi-Fi radios used in any Access Point (AP) have to speak (transmit) and listen (receive) in order to be able to provide wireless service. If one wants to capture everything that is going on within the RF environment, one needs to be “listening” all the time. This is what the Wyebot sensors do all the time (24 x 7) - they listen to “everything”.
As a normal part of the network testing process, the ethernet port on the sensor is disabled when a Wireless network test is run. At the conclusion of the test, the ethernet port will be re-enabled. This will show in your switch port logs as the port going up and down at a regular interval.
If this port going up and down is problematic for your environment, you can enable a configuration option called "Keep Ethernet Interface Up", which is found in Management > General. When this setting is enabled, the ethernet port will stay up during the network testing process, and you should no longer see the port changing state on your switch.
All sensor provisioning (i.e. assigning and removing sensors from customer accounts) is handled by Wyebot internally in order to streamline the set up for our customers. If you are replacing a sensor for an RMA or swapping out sensor models, you would return the old sensors via a prepaid shipping label. Once they are received back into Wyebot’s inventory, they will be removed from your dashboard.
The WIP solution is an “automated” solution that relies on Wyebot Intelligent Sensors, which capture all wireless packets (24/7), and analyze each of these packets on a bit by bit basis. The sensors generate metadata, which is sent to the cloud via industry-standard MQTT protocol over a secure TLS tunnel. WIP analyzes data from multiple sensors, using an AI-engine, and then provides a list of any problems it detects along with solutions for each of these problems. The WIP solution helps to quickly gain visibility into what is really happening in the WiFi environment, at the RF and packet levels.
This is all accomplished remotely. As a SaaS platform, the easy-to-read, cloud-based dashboard can be viewed from anywhere. Also, network tests can be scheduled to run automatically at user-determined intervals to give proactive insight into how the network is operating and isolate issues between the wired and wireless networks.
The sensors have three WiFi radios, and the sensor analyzes packet capture files (PCAP) from each radio. These are wireless packet captures, and since wireless troubleshooting is only concerned with the packet header, the data payload is discarded. These PCAPs are processed on board and metadata from them is sent to the cloud. The sensor stores the PCAP files on board in the device RAM, and can be downloaded from the Wyebot dashboard. Typically, there should be about 24 hours of PCAP data available to download historically, depending on network activity. If additional storage is needed, we can also provide an external storage device that can be plugged into the USB port - contact your Wyebot representative for more details.
You can download wireless PCAPs from the sensor by navigating to Advanced > Trace Download. The ability to download PCAP files can be disabled by and Admin user under Mangement > General.
The measurements for the sensor are: 23.4 cm x 23.4 cm x 3.5 cm / 9.21 in x 9.21 in x 1.38 in
Operating Temperature: 0°C to 45°C / 32°F to 113°F
The sensor may be powered using an 802.3af or 802.3at PoE power source or an optional 30W DC power adapter with the following specifications (12V @ 2.5A; Model: TE30A1203F01 or similar).
Full DC adapter specifications: 12 Volt Power Supply - 2.5 Amp Standard (12V 2.5A DC) AC Adapter 12VDC 2.5 A 12.0V w/ 5.5mm (Outside barrel) x 2.5mm (Inside Barrel) Center: Positive Tip
The 802.11ac sensors (WIS4200, WIS4250) will function on 802.3af (standard PoE) power. The 802.11ax and 6E sensor (WIS4300, WIS4400), or sensors using the USB storage expansion require 802.3at (PoE+) power.
In typical operation, approximately 12-14 Watts.
The sensor should be located within any area where WiFi operation is critical. It is most desirable to locate it near the access point (but no closer than 3 feet) providing coverage to that particular area. The sensor is shipped with clips for mounting to ceiling tile rails or it may simply be located on a desk/table using the pre-installed rubber mounting feet.
Yes, you can connect the sensor to your network via Ethernet or wireless.
Ethernet: The sensor should be connected through a VLAN that provides DHCP and access to our cloud servers. This does not necessarily have to be the same VLAN as your AP management. Network tests configured for Wired will run on the native/untagged VLAN associated with the switchport they are plugged into. For further reading on switchport configuration, refer to this guide: Configuring Switch Ports for Wyebot Sensors.
Wireless: When the sensor is configured in Wireless mode, it can be removed from a network switch and powered locally via DC adapter. When Wireless mode is enabled, the network test radio is repurposed as the WiFi backhaul, therefore network tests will be disabled.
The sensor is capturing the same wireless data which is present on the airwaves and available for anyone to capture using a basic laptop and free software. In a secure wireless network, this data is encrypted and the sensor does not need to decrypt this data to analyze the information and simply discards any data payload to reduce traffic to the cloud. In addition, metadata sent to the cloud is sent using a secure TLS tunnel.
The sensor contains three WiFi radios in total. Two (2) 802.11ac 4x4 capture radios, One (1) 802.11ax 2x2 radio used for data capture, background scanning, network tests/wireless cloud connectivity and a Bluetooth radio capable of capturing Bluetooth information.
The sensor is an “edge computing device” which means much of the processing is done locally onboard the sensor. All packets are captured, decoded and analyzed on the sensor. Only processed events of interest are sent to the cloud for further processing. In most cases, the bandwidth used by a sensor is less than 10 kbps.
Wyebot supports IdP initiated SAML. See our SAML Guide for more information.
| Hostname | IP |
|---|---|
| data.wyebot.net | 54.158.218.125 |
| eu-data.wyebot.net | 18.185.56.61 |
| command.wyebot.net | 34.192.168.148 |
| ntp.wyebot.net | 3.131.232.249 |
| vidtest2.wyebot.net | 3.137.79.225 |
| vidtest3.wyebot.net | 52.39.203.199 |