Homer and Bart and WiFi

I find myself explaining layer 1 physical spectrum analysis quite a lot these days.

Spectrum Analysis is everywhere today. There is Cisco Spectrum Expert, and CleanAir (now the chip is installed in every Enterprise Cisco AP). There is also Metageek Chanalyzer, and of course Cisco Meraki has it built in.

Identifying the different signals can be quite important to a wireless engineer in their day-to-day job.

I wanted to write this blog entry to introduce you to two of the most common signals that can be seen in the 2.4GHz and 5GHz range: DSSS and OFDM. (DSSS is 2.4GHz only, whilst OFDM operates in 2.4GHz and 5GHz.

DSSS is the mode of operation of 802.11 Prime (DSSS), and of 802.11b (HR-DSSS). OFDM is the mode of operation of 802.11a (OFDM), 802.11g (ERP-OFDM), 802.11n(HT), and 802.11ac (VHT).

So, what is an easy way to identify and remember these signals?

Well, this is where Homer and Bart (two of my favorite Simpsons characters) come into play.

Let’s imagine that Homer and Bart are up to no good (quite a common occurrence for this pair), and for some reason they have decided to hide behind a wall. Now let’s further imagine this wall is not quite tall enough to fully hide them, thus their heads are visible…

What you get is something like we see in Diagram 1

A cartoon of homer simpson and bart simpson on a graph.

DIAGRAM 1

In Diagram 1, we see two shapes, one that looks like Homer, and one that looks like Bart. Homer is effectively the shape of a DSSS transmission, and Bart is the shape of an OFDM transmission. There you have it! Easy to remember spectrum analysis.

So, taking a look at Diagram 2 below, we see again two shapes. At channel 6 we see a DSSS transmission, and at channel 11 we see an OFDM transmission.

A computer screen shows a graph that says real time fft

DIAGRAM 2: Actual Spectrum Expert Capture

 

Frequently people ask me, “Is that a “b” AP at channel 6, and a “g” AP at channel 11?” This is very important to stop and think about. These shapes actually show a “b” (or 802.11 Prime) DSSS transmission at channel 6, and a “g” ERP-OFDM transmission at channel 11. There is a lot of other information to take into account, but that is beyond the scope and intent of this article. This will be addressed in a different blog entry.

The take away is that, at channel 6, there was a “b” (or Prime) DSSS transmission and, at channel 11, there was a “g” ERP-OFDM transmission. Does that mean the AP at channel 6 is a “b” AP? Does it mean the AP at channel 6 was talking to a “b” client? The answer to both of these is maybe! All we know for sure is that there was a “b/Prime” DSSS transmission that we caught on channel 6, it could be a “b/Prime” (DSSS) AP, it could be a “g” (ERP-OFDM) AP talking to a “b/Prime” client, or it could simply be a “g” (ERP-OFDM) AP transmitting a Beacon at its lowest Basic/Mandatory speed – 1Mbps (802.11 Prime speed) that is sent out using DSSS.
So happy hunting for the “Homers” and “Barts”, and we’ll see you next month!

 

 

Blog Update Jun 2018

We all know Ekahau works really well with MetaGeek Chanalyzer, but what you may not know is the super-duper Ekahau SideKick seems to be taking over as a Spectrum Analyzer of choice, in its own right.

Will be doing more blog information on the SideKick soon…

(BTW, that last entry is from Wlan Professionals. Wlan Professionals is great community to get involved with, and is run by Keith Parsons, who is a legend in the WiFi community. They have blogs, podcasts and videos that are a great source of information. They also run great conferences throughout the year, one in the US and one in Europe. I try to attend WlanPros, Phoenix (US), every year.)

 

If you are looking to make your mark in the IT Industry, then NC-Expert offers excellent training courses aimed at relevant IT industry certifications – contact us today to get started.

NC-Expert Blog

Wi-Fi Myth Series - Myth #12: Auto Channel Selection ALWAYS Knows Best

By Rie Morgan • August 28, 2026
Automatic Channel Selection sounds like one of those features we should simply be able to trust: the APs monitor the RF environment, the Controller gathers data, an Algorithm considers interference, utilization, neighboring APs, channel availability, and other metrics, then Radio Resource Management (RRM) does its “thing” and selects the best channels. Wonderful! One less problem for the wireless engineer to worry about... except RF rarely cooperates with anything quite that neatly! Modern RRM systems are remarkably capable, and automatic channel selection can dramatically simplify the management of large wireless environments, but an algorithm can only make decisions based on the information it collects, the parameters it has been given, and the objectives it has been designed to optimize. That makes automation a powerful engineering tool. It does not make it the engineer.

Wi-Fi Myth Series - Myth #11: Interference Is Always Someone Else’s Wi-Fi

By Rie Morgan • August 20, 2026
When Wi-Fi performance suddenly deteriorates, interference is often the first culprit to be suspected and, when this (interference) enters the conversation, attention tends to turn immediately toward neighboring Wi-Fi networks. “Someone must have installed another AP.” “The office next door is probably using our channel.” “There are too many SSIDs around here.” Sometimes, this diagnosis is exactly right, but RF interference has a much larger cast of characters than just neighboring APs. In fact, some of the most frustrating wireless problems occur when the interfering device isn’t speaking 802.11 at all! The spectrum doesn’t particularly care whether the energy occupying it came from an enterprise AP, a Bluetooth headset, a microwave oven, or something considerably stranger. To a Wi-Fi radio trying to communicate, unwanted RF energy is simply unwanted RF energy. Wi-Fi Has to Share the Neighborhood The 2.4 GHz band has always been something of an RF “community center”. Wi-Fi operates alongside Bluetooth, Zigbee and other technologies, while various consumer, industrial, medical, and electronic devices may also generate energy within or around the same spectrum. Microwave ovens are perhaps the most famous example. Their emissions can interfere with 2.4 GHz Wi-Fi, particularly when clients are operating nearby. Bluetooth devices, cordless equipment, wireless cameras, sensors, and other transmitters can also contribute RF energy. Some interferers transmit continuously. Others appear periodically. Some hop frequencies. Others produce wideband noise. That last category can be particularly entertaining to troubleshoot... in the very specific sense of “entertaining” that wireless engineers use when they have been staring at spectrum analysis for three hours! The important point is that interference doesn’t need to understand Wi-Fi to disrupt it.

Wi-Fi Myth Series - Myth #10: The AP Is Up, So the Wi-Fi Must Be Fine

By Rie Morgan • August 13, 2026
There is something wonderfully reassuring about seeing a row of green APs on a wireless dashboard: APs connected; radios operational; no obvious alarms; everything green. Excellent! The Wi-Fi must be fine... Except, of course, the users are complaining that Teams calls are breaking up, handheld scanners keep disconnecting, authentication takes forever, and someone in Accounting has discovered that turning Wi-Fi off and back on again temporarily fixes everything. Welcome to one of the more persistent myths in enterprise wireless: if the AP is up, the Wi-Fi must be working. An operational AP tells us something useful... but it tells us surprisingly little about the experience of the clients actually using the network. “Up” is an Infrastructure State When a monitoring platform reports that an AP is up, it usually means the infrastructure can communicate with it. It tells us: - the AP has power - its Ethernet connection is functioning - it may have established its management or CAPWAP connection - its radios are probably operational - it hasn't disappeared into the networking equivalent of a “black hole” ...all good things. But none of those things proves that a client can successfully use an application. Consider what still has to happen after the AP proudly announces its existence. A client must: discover the WLAN associate authenticate obtain the appropriate network configuration reach its default gateway resolve DNS access the required network resources, and maintain sufficient RF performance to exchange data reliably. Depending on the environment, that journey may involve: 802.1X RADIUS DHCP DNS VLANs ACLs firewalls roaming mechanisms upstream switching WAN connectivity cloud services ...and several other systems waiting for their opportunity to make your afternoon more “interesting”. ;-) The AP actually being operational is merely one part of that chain!