We Shouldn’t Need Wyebot, But We Do

Just a taste of the Wyebot UI

Wireless network systems are expensive- like insanely expensive- and they are only one part of a given enterprise network environment. You can spend top dollar on market-leading WLAN hardware, switches, RADIUS servers, DNS and DHCP systems, Active Directory resources, security stuff and more You can have veteran IT craftspeople design, install and configure it all- and still have problems that are not only hard to solve but also hard to even start looking at when an end user tells you they aren’t happy. It is what it is, and many of the built-in tools that SHOULD help don’t do a particularly good job when you most need them.

Enter Wyebot.

I’ve been dipping toes in the Wyebot waters for a few years now, and was happy to see the Massachusetts-based company presenting at Mobility Field Day 8. Through the years I have been less than impressed after testing other 3rd party sensors and monitoring overlays (excluding 7signal, whose methodology I find to be quite effective), as false alarms are the norm and the systems frequently become just another high-cost glass of pain to ignore shortly after implementation.

I’ve personally found Wyebot to work well in effectively characterizing the WLAN space it operates in, exposing all of the WLAN-oriented details a wireless admin needs to know about. What’s there? How are the SSIDs configured? Where is contention and the potential for trouble? Which Wi-Fi networks are deviating from best practices? That’s the easy stuff. It also does highly-reliable synthetic testing that you define (one area where other sensors just don’t get it right) to help tell when any of the non-WLAN parts of the network are misbehaving in ways that frequently tarnish the WLAN’s reputation. I like the information delivered from the monitoring of spectrum, client behavior, and testing of upstream network resources. I find Wyebot to be a force multiplier in that it watches and ACCURATELY reports on what I care about when my pricey wireless system can’t natively get it done.

All network problems feel wireless to wireless users.

I particularly like that Wyebot not only has a robust packet capture capability for problem analysis, but you can also import wireless pcap files taken outside elsewhere using Wireshark on a laptop (just one example) and display that capture through the graphical Wyebot UI for Wyebot’s analysis of that capture. I also like that I can do wireless backhaul from the Wyebot sensors if needed.

The company is generous with free trials, and has some interesting case studies that show how organizations are using the solution.

Have a look at the Mobility Field Day 8 presentations by Wyebot. Also, see my past blogs about Wyebot here,

Well-designed and maintained wireless networks ought to not need outside tools to help keep them running well. Unfortunately, WLAN professionals know that we live in a very imperfect world. Unfortunately, not all of those outside tools are particularly effective, but I personally like what I get out of Wyebot.

2 thoughts on “We Shouldn’t Need Wyebot, But We Do

  1. Pingback: We Shouldn’t Need Wyebot, but We Do | Wirednot - Tech Field Day

Tell me what YOU think.

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s