Clear To Send is a podcast about wireless engineering where we educate you on WiFi technology, talk about design tips, troubleshooting, interviews, and the tools.
CTS 394: Would You Recommend Your Wi-Fi Vendor? (Audience Poll)
Sep 21, 2026
Show notes
https://youtu.be/hafv5cJT_fM
In this episode, François and I dig into a question we put directly to our audience: would you recommend your current Wi-Fi vendor? The results were telling. About 42 percent said yes without hesitation, 52 percent said yes but with a caveat, and only 6 percent said no, they’re looking to switch. So most people are happy, even if that happiness comes with an asterisk. We spend the episode unpacking what those caveats really mean and why they matter.
We start with why organizations stay put, because switching a Wi-Fi vendor is a big undertaking. It’s not just the cost of getting people on ladders to swap out APs. It’s the sunk time in the tools, templates, and custom integrations your team has already built, plus the risk management sees in trading known limitations for a set of unknowns. Relationships carry a lot of weight here too, since moving to a new vendor means building a whole new relationship from scratch. From there we get into the reasons people actually make the leap: recurring bugs the vendor can’t seem to fix, licensing and pricing changes nobody budgeted for, painful lead times, weak support, and RFP processes that sometimes reward the lowest price over the best fit.
If you do decide to evaluate someone new, we walk through how to do it well. Start with your real business requirements and run a proper proof of concept, but plan it like a full install rather than a one for one replacement. Give it time, because a single week won’t show you much; you need to burn the gear in, test capacity, and see how it holds up under real load. And keep in mind the work isn’t done once you sign, since migration, supporting two vendors for a while, training, and day two operations are all part of the picture. If you weren’t part of our poll, let us know where you land and what your caveat is, because that’s the conversation we want to keep having.
CTS 393 What is happening when the Wi-Fi Alliance certifies devices?
Sep 14, 2026
Show notes
https://youtu.be/LLXQlzicXEc
Ever wonder what actually happens behind the scenes when a device gets Wi-Fi Certified? In this episode, we sit down with Daryl K., who brings years of hands-on experience working inside Authorized Test Labs (ATLs).
We dive deep into how Wi-Fi Alliance testing works, how test beds are constructed, why some standard features fail in the real world, and what it takes to get products certified.
Key Takeaways & Timestamps
[00:08] – Introduction
Hosts welcome guest Daryl K. to share his background in network testing and his transition into the Wi-Fi industry.
[03:13] – What is an Authorized Test Lab (ATL)?
Role of ATLs: Third-party labs (ATLs) run the actual hardware and software tests inside anechoic chambers; the Wi-Fi Alliance acts as the issuing body that approves the certification.
Value of Certification: Certification ensures interoperability across multi-vendor chipsets and validates proper behavior in edge cases.
[07:08] – Test Complexity & Duration
Time Requirements: Wi-Fi 5 (802.11ac) testing could be finished in ~2 weeks. Wi-Fi 6 takes about a month, and Wi-Fi 7 can take 6 to 7 weeks due to cumulative backward-compatibility testing and hundreds of test cases.
Test Bed Setup: Test environments use standardized hardware racks stacked with modified laptops, access points, and sniffers connected to central control consoles.
Devices with 802.11 radios can be sold without certification, but major retailers (e.g., Target, Costco) often require it.
Certification is mandatory for integration into major ecosystems like Matter, Apple CarPlay, Android Auto, and Alexa.
[14:45] – Handling Test Failures & Interoperability
Different ATLs handle failures differently—some offer debugging support and lab time to revise firmware, while others enforce strict “three strikes” policies.
Discussion on vendor “Plugfests” where chipset engineers (Qualcomm, Broadcom, Intel, MediaTek) collaborate to resolve root-cause interoperability issues before programs launch to ATLs.
[28:36] – Mandatory vs. Optional Features in the Field
Protected Management Frames (PMF): Originally optional, PMF was made mandatory after testing showed nearly half of legacy devices failed when connecting to PMF-enabled APs.
Vendor “Special Sauce”: How proprietary features (like early band-steering implementations) sometimes broke client connectivity due to unhandled information elements.
[8:03] – Promising Tech That Missed the Mark
Wi-Fi Direct Services: Designed for simple one-click printing, but superseded by higher-layer network solutions.
Wi-Gig (60 GHz / 802.11ad): Originally pitched as wireless HDMI, but extremely tight beamforming and short range made it impractical for consumer adoption.
[40:36] – Resources for Wi-Fi Professionals
Product Finder: Using the Wi-Fi Alliance online tool to look up certified features once product non-disclosure periods expire.
Finding Chipset Details: Navigating FCC documentation (and tools like FCCID.io) to identify real underlying hardware specs for client troubleshooting.
CTS 392: Navigating Ekahau’s New Licensing Model (Sponsored)
Sep 08, 2026
Show notes
In this special sponsored episode of the Clear To Send podcast, hosts Rowell Dionicio and Francois Verges sit down with Troy Martin and Matt from Ekahau to discuss a major, fundamental shift in the company’s product licensing structure.
Effective September 1, 2026, Ekahau is introducing a new software as a service (SaaS) licensing model designed to provide organizations with role-based flexibility across the wireless project life cycle.
This new strategy allows companies to assign specific tools to specific team members based on their day-to-day functions, such as field data collection or corporate office design, rather than forcing the purchase of an all-inclusive software package.
Matt and Troy break down the three primary SaaS options: Ekahau Plan for RF predictive designs, Ekahau Measure Pro for field surveying and live troubleshooting, and the comprehensive Ekahau Software Suite. Additionally, they highlight a baseline Ekahau Measure option for survey-only needs and reassure existing customers that perpetual licenses and connect subscriptions are not being sunsetted. Listeners can find the transparent MSRP pricing and a detailed feature breakdown by visiting ekahau.com.
CTS 391 – How to Perform an AP-on-a-Stick Survey Effectively
Aug 31, 2026
Show notes
https://youtu.be/gDR38L1sOfQ
An AP-on-a-Stick (APoS) survey is the most reliable way to know how a Wi-Fi design will behave in a difficult environment. You mount a real access point on a tripod, place it where you plan to install it, and measure. It is also the survey type where the most time gets wasted — and almost never on RF.
In this episode we go through how we prepare and run APoS surveys: the conversation with the client, the equipment decisions, the configuration work that belongs in the office, and the way we organise the survey files we bring back.
What we cover
When an APoS survey is justified, and when a predictive design plus a validation survey is the better answer
Preparing the work on site with the client: escorts, access, PPE, production constraints, and communicating what our equipment entails
Choosing the right equipment for the site: stick height, antennas, brackets, PoE batteries
Why the access points must be configured and tested before leaving the office
The case for a two-person crew
Planning the measurements in advance so the on-site day is pure execution
Using one survey file per variable to compare antennas, locations, heights and power levels
APoS preparation checklist
[ ] Escorts confirmed, with names and time slots
[ ] Site access, parking and PPE requirements documented
[ ] Client informed of the equipment coming on site and its footprint
[ ] APs configured, labelled and tested: SSID, channel, width, tx power, name broadcast
[ ] Full kit tested end to end, batteries charged, spares packed
[ ] Velcro wraps, zip ties, duct tape and screwdriver kit in the bag
[ ] Measurement plan built from the predictive model, test points numbered on the floor plan
[ ] Survey file naming convention agreed before the first walk
Key takeaway
An APoS survey is won or lost before you get on site. Prepare off site, execute on site.
CTS 390: Which tools have we used this year?
Aug 24, 2026
Show notes
In this episode, Rowell and François discuss the tools they have been using so far in 2026. From the hardware that’s used on a day-to-day or at a client site to the software they use to help them run their business, fix Wi-Fi issues, and conduct surveys, to AI and Automation.
At the end of 2026, they will record another episode discussing which tools made it through and will show long-term usage.
CTS 389: SSID Spaghetti – How Many SSIDs Is Too Many?
Aug 17, 2026
Show notes
In this episode of the Clear to Send podcast, the hosts revisit the classic Wi-Fi design question: “How many SSIDs is too many?” While the long-standing technical advice has always been to minimize SSIDs to conserve airtime, the discussion explores how modern standards—like 6 GHz, multiple BSSIDs, and changing client habits—impact this rule of thumb.
The episode provides technical discussion on management overhead, strategies for network consolidation, and advice on how to communicate these technical limitations to management.
Supporting Data
Beacon airtime per SSID, per radio
Beacon data rate
Airtime per SSID
4 SSIDs
8 SSIDs
1 Mbps
~2.0%
~8%
~16%
6 Mbps
~0.35%
~1.4%
~2.8%
12 Mbps
~0.18%
~0.7%
~1.4%
24 Mbps
~0.10%
~0.4%
~0.8%
Based on ~10 beacons/sec at a 100 TU beacon interval and a ~200-byte beacon frame.
Co-channel multiplication – 4 SSIDs on the channel
Beacon data rate
1 AP
3 co-channel APs
5 co-channel APs
1 Mbps
~8%
~24%
~40%
12 Mbps
~0.7%
~2.2%
~3.6%
24 Mbps
~0.4%
~1.2%
~2.0%
The headline stat for the episode: it is not the SSID count that kills you, it is the SSID count multiplied by co-channel APs and divided by your data rate.
“We need a new SSID” → the better answer
The request
Better solution
Different PSK per IoT device type
One SSID with MPSK / iPSK / DPSK
Separate SSID per department
One 802.1X SSID + RADIUS role/VLAN assignment
Contractor network
Same 802.1X SSID, different role
Temporary SSID for an event
Scheduled SSID, scoped to those APs, with an expiry date
CTS 388: Would You Rather, Wi-Fi Edition
Aug 03, 2026
Show notes
We’re trying out something new in this episode. We’re asking each other questions on “Would you rather” to get insight into how we would do Wi-Fi given we had two options.
What you’ll find is that we don’t always agree on the same things. And that’s okay.
More importantly, is diving into the reasons why. If you find that there’s a topic you’d like to learn more about, please let us know in the comments below.
CTS 387: Networking at the Crossroads: Our Impressions of HPE Discover
Jun 23, 2026
Show notes
https://youtu.be/G6K-_qMxRWU
In this episode, co-hosts Rowell Dionicio and François Vergès share their first-time experiences and impressions of HPE Discover. They dive into the pervasive role of AI in modern networking, discuss their individual presentations on automation and agentic AI, and explore how the acquisition of Juniper Networks is influencing the HPE Aruba product ecosystem.
Key Discussion Points
First Impressions of HPE Discover
Unique feel of the conference compared to Aruba Atmosphere and the value of community engagement on the expo floor.
Highlights from the “Misfits” community program, including networking dinners and professional podcast opportunities.
Presenting at a Vendor Conference
Rowell’s Session: A journey into agentic AI, focusing on creating a network operations agent with a “Gilfoyle” (Silicon Valley) personality to handle networking queries.
François’s Session: Exploring Mist APIs for Day 0, Day 1, and Day 2 Wi-Fi operations, including the development of an MCP server to automate Wi-Fi tasks.
The AI and Networking Landscape
Core Message: The central theme of the conference is Agentic AI, AI operations, and AI governance.
Cross-Pollination: New integrations allow CX switches to be managed via the Mist dashboard and Marvis actions to be accessed through Aruba Central.
The Learning Curve: Despite the industry push, many attendees are still hesitant or in the early stages of adopting AI and tools like Marvis.
The Future of the Network Engineer
The evolution from manual tasks (like SSH and troubleshooting) to focusing on architecture, automation, and prompting skills.
Advice on embracing AI as a “must-have” skill to stay relevant in the industry.
Strategies for building “smart” agents that balance reasoning with deterministic actions to manage token costs and efficiency.
Expo Floor Highlights
Interesting hardware displays, including an AP in an aquarium.
Custom in-house tools like a NOC dashboard that visualizes location data and heat maps from AOS8, AOS10, and Mist.
Let me walk through what a day in the life of a WLAN Engineer looks like in Higher Education and in a consulting role.
Both are different but they share similar characteristics.
In Higher Education, the day can start with tickets or with a new Wi-Fi design. We have the flexibility here to design our day. But there’s no doubt it can be filled with unnecessary meetings.
For a WLAN Engineer in a consulting role, those meetings can be absolutely necessary in order to have a positive outcome in an engagement.
I’ve been fortunate to hold hats in both roles and I enjoy doing both.
If you’d like to share what your day looks like as a WLAN Engineer, please leave a comment down below.
In this episode, we’re diving into some Python and APIs to visualize data within Grafana. This episode is part of Rowell’s automation journey. He has been learning Python with his daughter.
For Rowell, this is just the beginning as he starts integrating Grafana with InfluxDB and Telegraf. A lot more has to be learned in addition to Python and API.
Within the video, we look into the Mist API and see how Rowell was able to develop a script to pull specific information that could be part of a dashboard within Grafana.