RUCKCast #121: The Minimum Problem with Minimum Basic Rates
Send us Fan MailYou sit down with your design tool, paint coverage to -67 dBm, target 100+ Mbps everywhere, validate it, and present a beautiful heatmap. Then you open the controller and leave the minimum basic rate at 6 Mbps — an MCS 0. Your design says MCS 0 should never happen. So why are you protecting it?In this episode, Jim walks through the real cost of low MBR settings: beacons and management frames burning airtime at the lowest configured rate, multicast traffic crawling while unicast flies at MCS 9+, inflated cell sizes creating co-channel interference you didn't design for, and neighboring APs deferring to frames serving clients that shouldn't exist in your coverage area. Using field data from a recent network audit, Jim shows what beacon overhead actually looks like when 11b is still enabled and MBR is left at defaults — and what changes when you raise it to 24 Mbps.The episode also tackles the IoT pushback head-on: possible vs. probable, why segmentation beats accommodation, and why the answer to "but what if a device can't connect at 24?" is to handle the exception, not punish a thousand clients for it.Design for probable, adjust for possible. Trust your own design.Intro music by Alex Grohl, available here:https://www.youtube.com/watch?v=ZsRWpx8VJ_Eandhttps://pixabay.com/users/alexgrohl-25289918/
