<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by nick legger on Medium]]></title>
        <description><![CDATA[Stories by nick legger on Medium]]></description>
        <link>https://medium.com/@nick.legger?source=rss-7453edc94375------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uQQj9tJVdMgiFyWy.</url>
            <title>Stories by nick legger on Medium</title>
            <link>https://medium.com/@nick.legger?source=rss-7453edc94375------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:32:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nick.legger/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The “Empty” Wi-Fi Channel That Can Make Things Worse]]></title>
            <link>https://medium.com/@nick.legger/the-empty-wi-fi-channel-that-can-make-things-worse-68277180aec4?source=rss-7453edc94375------2</link>
            <guid isPermaLink="false">https://medium.com/p/68277180aec4</guid>
            <dc:creator><![CDATA[nick legger]]></dc:creator>
            <pubDate>Tue, 22 Sep 2026 17:27:21 GMT</pubDate>
            <atom:updated>2026-09-22T17:27:21.119Z</atom:updated>
            <content:encoded><![CDATA[<h3>Different channel numbers don’t always mean separate airspace.</h3><p>You open a Wi-Fi scanner. Channels 1 and 6 look crowded. Somewhere between them looks quieter. Easy decision, right? On 2.4 GHz, that apparently clever move can put your signal in the middle of both conversations.</p><p><em>Author’s note: This article uses my Wi-Fi scan and observations, with AI assistance for drafting and source research.</em></p><p>Your router has options. Physics has opinions.</p><p>While looking at a WiFiman scan, I noticed a nearby network on channel 4. The app also rated channel 4’s health “Good.” That makes this a useful example of why a channel chart deserves a closer look before we start changing settings.</p><figure><img alt="WiFiman Desktop scan. Blue arrows point to a weak nearby network centered on 2.4 GHz channel 4, around minus 90 dBm. The channel-health table rates channel 4 Good. The connected NetworkNickOfficial network is separately listed on channels 1 and 149." src="https://cdn-images-1.medium.com/max/1024/1*jX21IwAcvVl-eICmvQE31Q.png" /><figcaption>WiFiman scan supplied by Nicholas Legger. The arrows identify a nearby 2.4 GHz network on channel 4.</figcaption></figure><p><em>The arrows identify a nearby channel 4 network. Its plotted signal is roughly −90 dBm at the scanner’s location. The −43 dBm reading at the top belongs to the connected network, not the highlighted neighbor. The scan shows overlap, not measured performance loss.</em></p><h3>Different numbers, some of the same airspace</h3><p>Wi-Fi channels sound like parking spaces. If space 1 is occupied, surely space 4 gives everyone room.</p><p>The catch is that a Wi-Fi transmission occupies a range of frequencies. On 2.4 GHz, many channel ranges overlap. Changing the number doesn’t automatically separate your signal from the one next door.</p><p>For typical U.S. deployments using 20 MHz channel widths, <strong>1, 6, and 11 are the standard nonoverlapping choices</strong>. Channel 4 overlaps frequency space used by channels 1 and 6. Cisco explains this plan in its <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/technical-reference/wireless-rf-reference-guide.html">Wireless RF Reference Guide</a>.</p><p>This is a channel-planning recommendation for those conditions. Other channel numbers being available is not a regulatory violation, and this rule should not be copied over to 5 GHz or 6 GHz.</p><h3>Why sharing can beat talking over each other</h3><p>Wi-Fi devices share airtime. On the same channel, devices that can detect one another’s Wi-Fi transmissions can defer and contend for a turn. This still reduces the capacity available to each device, and hidden devices can complicate things. It is no magic cure for a crowded network.</p><p>Partially overlapping channels introduce adjacent-channel interference, or ACI. Interfering transmissions can disrupt reception, corrupt frames, and cause retries. That wastes airtime and can reduce throughput or make delays less predictable. Extreme Networks uses channels 1 and 4 as an example to <a href="https://extreme-networks.my.site.com/ExtrArticleDetail?an=000087241">explain co-channel and adjacent-channel interference</a>.</p><p>Think of a meeting where people try to take turns. Now add another conversation close enough to make their words difficult to hear.</p><p>“Sorry, could you repeat that?”</p><p>Again. And again.</p><p>That is an analogy, but it captures the cost of repeating work. Your devices are trying to finish a conversation while the air becomes increasingly unhelpful.</p><h3>A “Good” rating still needs context</h3><p>In this screenshot, channel 4 receives a “Good” label. We have not verified how WiFiman calculated that particular score. The label alone does not establish whether channel 4 is the best choice for a specific connection.</p><p>The highlighted network also appears weak at the measurement location, roughly −90 dBm. Its effect at another receiver depends on conditions there, including relative signal levels and whether overlapping transmissions happen at the same time. A weak signal on this laptop is not a measurement of every room nearby.</p><p>Nor does the network name tell us who selected the channel. A customer, an installer, or an automatic setting could be involved. This scan does not establish a provider-wide problem or a security failure.</p><p>ACI is a real engineering concern. Establishing its impact on a particular connection takes measurements.</p><h3>What if the hotspot moved?</h3><p>A fair question: what if a hotspot chose its channel somewhere quiet, then someone drove it into a crowded neighborhood? That could explain the setting. This scan cannot establish whether that happened, or even whether the device is a mobile hotspot.</p><p>For a typical U.S. 20 MHz setup, I would want automatic selection to use 1, 6, and 11 as its normal candidates and account for the surrounding conditions.</p><p>I would not expect it to change channels at every traffic light. Channel changes can affect connected devices, so adapting to interference also means considering connection stability. Cisco discusses that tradeoff in its <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/mobility_express/b_RRM_White_Paper/b_RRM_White_Paper_chapter_0100.html">dynamic channel assignment guide</a>. That enterprise example does not tell us when this unidentified device scans or changes channels; its own documentation would be needed.</p><h3>What I would check before blaming the internet plan</h3><p><strong>Start with channel width.</strong> On 2.4 GHz, 20 MHz is a sensible starting point around neighboring networks. Apple recommends it to help avoid performance and reliability problems in its <a href="https://support.apple.com/en-us/102766">router configuration guidance</a>.</p><p><strong>Measure where the trouble happens.</strong> If calls drop at the back-office desk, that desk is part of the investigation. A beautiful reading beside the router does not settle the question.</p><p><strong>Look beyond the number of network names.</strong> A scanner can show who is nearby without telling you how much airtime each network consumes. Use channel utilization and retry information when your equipment makes those measurements available.</p><p><strong>Evaluate automatic selection before taking over manually.</strong> Automatic channel selection can be useful. If manual tuning is justified in a typical U.S. 20 MHz setup, evaluate channels 1, 6, and 11 against actual conditions. Cisco Meraki’s <a href="https://documentation.meraki.com/Wireless/Design_and_Configure/Architecture_and_Best_Practices/Channel_Planning_Best_Practices">channel planning guidance</a> covers automatic adjustments and the use of site measurements for manual tuning.</p><p><strong>Change one thing, then test again.</strong> Keep the device, location, and test conditions as consistent as practical. Compare throughput, delay, and reliability. A prettier graph is encouraging. The connection still needs to perform better.</p><h3>Customers deserve good defaults</h3><p>Providers and equipment manufacturers should make sensible channel planning part of the default experience. Support teams should also be able to investigate unusual choices and explain them using measurements.</p><p>Customers have every reason to expect reliable equipment without first learning radio engineering. Good defaults and useful diagnostics help make that possible.</p><p>Before the next family troubleshooting session turns into router shopping, check the channel width and channel plan. Then test whether the change actually helped.</p><p>The person who always gets asked to “fix the Wi-Fi” deserves a shorter weekend shift.</p><h3>Common questions</h3><p>Here are the questions I would expect over coffee, during troubleshooting, or immediately after someone says, “Have you tried restarting it?”</p><p><strong>Is channel 4 illegal?</strong></p><p>For an ordinary U.S. 2.4 GHz Wi-Fi setup, channel 4 is a permitted channel. The concern here is overlap and performance. Legal availability and a sensible channel plan answer different questions. <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/technical-reference/wireless-rf-reference-guide.html">Cisco’s RF guide</a> explains the planning recommendation.</p><p><strong>Which should I choose: 1, 6, or 11?</strong></p><p>There is no universal winner. Evaluate conditions where your devices actually operate, including channel activity and signal quality. The channel with the fewest network names is not automatically the least busy. <a href="https://documentation.meraki.com/Wireless/Operate_and_Maintain/User_Guides/Monitoring_and_Reporting/RF_Spectrum_Page_Overview">Meraki’s spectrum guide</a> distinguishes neighboring networks from channel utilization.</p><p><strong>What if all three are crowded?</strong></p><p>Moving between them does not create new spectrum. Start with the best-performing standard candidate, then investigate placement, coverage, and available capacity. Where supported and coverage is adequate, moving suitable clients to 5 or 6 GHz can help. More megabits on your internet plan cannot create more local radio spectrum. <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/best-practices/base/b_bp_wlc/rfmgmt.html">Cisco’s RF management guidance</a> discusses using bands and RF resources effectively.</p><p><strong>Should I turn off automatic channel selection?</strong></p><p>Not by default. Automatic selection can be useful, and Apple recommends it. If you suspect a bad choice, check the device’s documentation and compare measured results before taking over manually. The word “Auto” does not tell you how often a particular product rescans. <a href="https://support.apple.com/en-us/102766">Apple’s router settings</a>.</p><p><strong>What if a hotspot picked its channel in the countryside, then moved?</strong></p><p>That is plausible. It explains why the setting deserves investigation without identifying the device or proving how it behaved. As discussed above, my recommendation for a typical U.S. 20 MHz product is a sensible candidate set and adaptation that also considers client stability.</p><p><strong>Does a signal around −90 dBm mean the neighbor cannot matter?</strong></p><p>It is weak at this scanner, but that is not a universal interference verdict. The affected receiver may be elsewhere. Relative signal levels, channel overlap, and simultaneous traffic matter. The screenshot alone cannot establish harmful interference or rule it out everywhere.</p><p><strong>If WiFiman says “Good,” is the app wrong?</strong></p><p>We have not verified how this particular rating is calculated. Treat it as one indicator, then check the connection’s performance. A dashboard label needs a definition before it can answer a specific engineering question.</p><p><strong>Would 40 MHz be faster than 20 MHz on 2.4 GHz?</strong></p><p>Wider channels can offer higher rates under favorable conditions, but consume more of an already cramped band. Around neighboring networks, 20 MHz is the recommended starting point. Apple specifically recommends 20 MHz on 2.4 GHz to help avoid reliability and performance problems. <a href="https://support.apple.com/en-us/102766">Apple’s channel-width guidance</a>.</p><p><strong>Do channels 1, 6, and 11 apply to 5 GHz or 6 GHz?</strong></p><p>No. Those bands have different channel plans and width options. A number is meaningful only with its band and width. Do not transfer the 2.4 GHz rule to another band. <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/technical-reference/wireless-rf-reference-guide.html">Cisco’s band overview</a>.</p><p><strong>Can a speed test prove ACI is the problem?</strong></p><p>A single internet speed test cannot isolate ACI. The remote server, internet connection, device, and Wi-Fi all influence the result. Compare repeated tests, use a local wired endpoint where practical, and inspect retries or packet captures when available. <a href="https://documentation.meraki.com/Wireless/Troubleshooting_and_Support/Troubleshooting/Tools_for_Troubleshooting_Poor_Wireless_Performance">Meraki’s troubleshooting guide</a> describes complementary tests.</p><p><strong>Can Bluetooth or a microwave cause trouble without appearing as a network?</strong></p><p>Yes. A list of Wi-Fi network names is not a complete inventory of radio activity. Non-Wi-Fi devices can also use or interfere with the band. A spectrum-analysis tool provides information that an SSID list cannot. <a href="https://documentation.meraki.com/Wireless/Design_and_Configure/Architecture_and_Best_Practices/Common_Sources_of_Wireless_Interference">Meraki’s interference examples</a>.</p><p><strong>Does this prove the provider configured it badly or exposed customer data?</strong></p><p>No. The network name does not establish who chose the setting, and channel overlap does not establish a security breach. Investigate the configuration and performance first. Security claims need separate evidence.</p><h3>A few edge cases for the curious engineer</h3><p><strong>Is adjacent-channel interference always worse than sharing a channel?</strong></p><p>ACI can corrupt reception and trigger retries, while same-channel devices can often defer to one another. That is why avoiding partial overlap is a strong planning recommendation. But “always worse” is too absolute for comparing arbitrary networks with different traffic and signal levels. <a href="https://extreme-networks.my.site.com/ExtrArticleDetail?an=000087241">Extreme Networks explains the mechanisms</a>.</p><p><strong>What about the 1, 5, 9, and 13 plan?</strong></p><p>It is sometimes proposed where channel 13 is permitted. Cisco advises against it because practical separation and coexistence with neighboring 1/6/11 networks create problems. Availability of channel 13 does not make this an equally safe default in a mixed neighborhood. <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/technical-reference/wireless-rf-reference-guide.html">Cisco’s discussion of four-channel plans</a>.</p><p><strong>Are there channels 14 and 15? Can I change my router’s country setting?</strong></p><p>Conventional 2.4 GHz Wi-Fi numbering ends at 14. Channel 14 is a special Japanese 802.11b case, not a normal extra channel for modern Wi-Fi. There is no conventional 2.4 GHz Wi-Fi channel 15. Use settings approved for the device and its actual location. <a href="https://www.cisco.com/web/JP/solution/netsol/mobility/literature/pdf/14435_01.pdf">Cisco’s regional channel table</a>.</p><p><strong>Can networks on 1, 6, and 11 still affect each other?</strong></p><p>Nonoverlapping channel planning is not a guarantee of perfect radio isolation. Very close radios, strong signals, and receiver limitations can still matter. Channel planning belongs alongside placement and power design. <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/technical-reference/wireless-rf-reference-guide.html">Cisco’s RF reference</a> covers separation and co-location considerations.</p><p><strong>Should every mesh node use a different channel?</strong></p><p>No. Radios forming a wireless backhaul link need a compatible channel arrangement, often the same channel on that link. Client-serving radios may follow a different plan. Follow the mesh system’s design before forcing settings that could break its connection. <a href="https://documentation.meraki.com/Wireless/Design_and_Configure/Deployment_Guides/Mesh_Deployment_Guide">Meraki’s mesh deployment guide</a>.</p><p><strong>Does Wi-Fi 6 solve this with BSS coloring?</strong></p><p>BSS coloring helps compatible devices distinguish wireless networks and supports spatial reuse. It does not make overlapping frequencies disappear or give every receiver immunity to interference. The feature helps manage shared spectrum; good RF design still matters. <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-4/config-guide/b_wl_17_4_cg/m_bss_coloring_ewlc.html">Cisco’s BSS coloring guide</a>.</p><p><strong>Would maximum transmit power fix it?</strong></p><p>More power is not a universal fix. Wi-Fi needs communication in both directions, and the client may not match the access point’s reach. Adjust power using measurements rather than treating the slider like a volume knob at a party. <a href="https://www.cisco.com/c/dam/en/us/td/docs/wireless/controller/technotes/8-5/cisco-enterprise-mobility-design-guide-8-5.pdf">Cisco’s enterprise mobility design guide</a> discusses matching power to client capabilities.</p><p><strong>Could channel 4 work perfectly well in an isolated setup?</strong></p><p>Yes, a setup with no meaningful competing interference may work well on it. That does not make channel 4 a good default for equipment entering a shared environment. Successful operation in one place and robust default behavior across many places are different tests.</p><p><strong>What if two devices share a channel but cannot hear each other?</strong></p><p>That is the hidden-node problem: two transmitters may both reach a receiver while failing to hear one another, so their transmissions can collide there. RTS/CTS can help in suitable conditions, with extra airtime overhead. It is not a general cure for ACI. The <a href="https://inet.omnetpp.org/docs/showcases/wireless/hiddennode/doc/">INET project demonstrates the mechanism</a> in a reproducible simulation.</p><p><strong>Is a channel graph the same as a spectrum-analyzer measurement?</strong></p><p>No. A graph of discovered access points, channel widths, and received signal levels is not a direct measurement of every signal or of packet corruption. Meraki documents separate views for <a href="https://documentation.meraki.com/Wireless/Operate_and_Maintain/User_Guides/Monitoring_and_Reporting/RF_Spectrum_Page_Overview">AP neighbors and spectrum/channel activity</a>. Read the tool’s documentation before treating its drawn shapes as measured emissions.</p><p><strong>Could radar explain a channel change?</strong></p><p>On certain 5 GHz channels, Dynamic Frequency Selection requires radar detection and channel evacuation when applicable. That is a different mechanism from the 2.4 GHz channel 4 issue here. Check the band and the device’s event logs before connecting those dots. <a href="https://documentation.meraki.com/Wireless/Operate_and_Maintain/User_Guides/Radio_Settings/Dynamic_Frequency_Selection_%28DFS%29">Meraki’s DFS explanation</a>.</p><p><em>Follow </em><a href="https://medium.com/@nick.legger"><em>Nicholas Legger on Medium</em></a><em> for practical networking explanations, or connect with me on </em><a href="https://www.linkedin.com/in/nicklegger/"><em>LinkedIn</em></a><em>. You can also follow </em><a href="https://www.linkedin.com/company/apex-nextgen-networking/"><em>APEX NextGen Networking</em></a><em> for practical network engineering and </em><a href="https://www.linkedin.com/company/nextgengalactic/"><em>NextGenGalactic</em></a><em> for more approachable technology explainers.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68277180aec4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>