I’m considering buying NetSpot for Windows, but noticed something in the channel graph that I can’t quite make sense of.
Say an AP is configured with channel 128 as its primary channel and an 80 MHz channel width. As I understand it, that 80 MHz block spans the lower channels as well, so channel 128 isn’t actually sitting in the middle of the occupied spectrum.
But in NetSpot, the graph seems to draw the network as if 128 is the center of the whole 80 MHz block.
That makes the visualization a little confusing when you’re trying to see which parts of 5 GHz are actually free.
Am I misunderstanding how NetSpot represents the primary/control channel vs the full channel width, or is the graph actually being drawn wrong?
No, I don’t think you’re misunderstanding it. If NetSpot is centering the entire 80 MHz block around the reported primary channel instead of showing the actual bonded channel range, that sounds more like a visualization issue. Do you have a screenshot of what it’s showing?
@ED_Sniper Yeah, that’s exactly what I’m seeing. The AP reports 128 as the channel, 80 MHz width, but visually NetSpot puts 128 right in the middle of the curve. That’s what threw me off because I’m trying to use the graph to find the least occupied part of the band.
Honestly looks like a bug to me.
I’d send it to the NetSpot devs with the screenshot + AP channel/width settings. This is the kind of thing that’s probably easy for them to reproduce once they know where to look. Their support has fixed display quirks before, so I’d report it rather than assuming that’s intentional behavior.
@juanramonblanco Yeah, I’ll do that. Wanted to make sure I wasn’t completely misunderstanding channel bonding before reporting it
They got back to me. Sounds like it may actually be a rendering bug, and they said they’ll probably patch it in an update.