<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Muhammad Nuh</title><link>https://hexrogue.github.io/tags/networking/</link><description>Recent content in Networking on Muhammad Nuh</description><generator>Hugo</generator><language>en-us</language><managingEditor>ikanlemas0@gmail.com (Muhammad Nuh)</managingEditor><webMaster>ikanlemas0@gmail.com (Muhammad Nuh)</webMaster><lastBuildDate>Mon, 05 Oct 2026 09:45:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>RSSI is a liar</title><link>https://hexrogue.github.io/blog/rssi-dbm-noise-floor/</link><pubDate>Mon, 05 Oct 2026 09:45:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/rssi-dbm-noise-floor/</guid><description>&lt;p&gt;Your laptop reports -67 dBm and streams video. Your phone reports -67 dBm and stutters. Neither number is lying about the signal. Both are lying about the quality, because the signal alone does not contain the noise. RSSI is the friend who says &amp;ldquo;I&amp;rsquo;m five minutes away&amp;rdquo; from another city.&lt;/p&gt;&#10;&lt;h2 id="dbm-is-a-log-scale"&gt;dBm is a log scale&lt;/h2&gt;&#10;&lt;p&gt;0 dBm is one milliwatt. Every 3 dB doubles or halves the power, and every 10 dB is a factor of ten. So -60 dBm is ten times the power of -70 dBm, and -70 is ten times -80. The gap between &amp;ldquo;fine&amp;rdquo; and &amp;ldquo;dead&amp;rdquo; is smaller than the numbers suggest: -67 to -80 is 13 dB, roughly a factor of twenty in power.&lt;/p&gt;</description></item><item><title>The 2.4 GHz food fight</title><link>https://hexrogue.github.io/blog/24ghz-interference-channel-planning/</link><pubDate>Fri, 07 Aug 2026 08:30:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/24ghz-interference-channel-planning/</guid><description>&lt;p&gt;Your wifi is fine at 8am and unusable at 8pm. Nothing in your house changed. The band did. 2.4 GHz is shared with microwaves, Bluetooth, cordless phones, baby monitors, Zigbee and every neighbour&amp;rsquo;s router, and it has three usable lanes.&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/memes/meme-24ghz-crowded.jpg" alt="This Is Fine dog meme: 2.4 GHz at 8 PM while the microwave, Bluetooth, a baby monitor, and 37 neighbours all share the band"&gt;&#10;&lt;figcaption&gt;The band is not crowded. It is a group project where everyone brought a microwave.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="three-lanes-thirteen-labels"&gt;Three lanes, thirteen labels&lt;/h2&gt;&#10;&lt;p&gt;The band runs from 2.400 to 2.4835 GHz. Channels are numbered 5 MHz apart, but a 20 MHz wifi channel occupies four of those gaps. That is why 1, 6 and 11 are the only non-overlapping choices in the common plan: each takes a 20 MHz slice, and they just touch at the edges.&lt;/p&gt;</description></item><item><title>Why your phone clings to a dead wifi access point</title><link>https://hexrogue.github.io/blog/wifi-roaming-sticky-clients/</link><pubDate>Wed, 15 Jul 2026 10:25:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wifi-roaming-sticky-clients/</guid><description>&lt;p&gt;Walk from the kitchen to the bedroom on a call. The phone still shows two bars, still names the access point you left behind, and the voice turns to gravel. You did not lose wifi. Your phone chose to keep it.&lt;/p&gt;&#10;&lt;p&gt;That choice is the whole story of roaming, and it is the one part of wifi people assume the network controls. It does not. The standard gives the client the vote, and the access point gets a suggestion box.&lt;/p&gt;</description></item><item><title>802.11 frames you can read straight off the air</title><link>https://hexrogue.github.io/blog/80211-frames-you-can-read/</link><pubDate>Tue, 10 Feb 2026 10:40:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/80211-frames-you-can-read/</guid><description>&lt;p&gt;Every wifi packet you will ever capture is the same envelope. Once that clicks, a wall of hex becomes a conversation you can follow with one eye. The first time it clicks, you feel like a wizard. The second time, you realize the wizard is just reading headers and taking notes.&lt;/p&gt;&#10;&lt;h2 id="the-envelope"&gt;The envelope&lt;/h2&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/esp32/80211-mac-frame.svg" alt="802.11 MAC frame layout: frame control, duration, three addresses, sequence control, frame body and FCS"&gt;&#10;&lt;figcaption&gt;The 802.11 MAC frame. Diagram by Superspritz, CC BY-SA 4.0, via Wikimedia Commons.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;The first two bytes are frame control. They answer the two questions that matter: what type of frame is this, and what flavour of that type. Two bits say management, control or data. Four more say the subtype, so a beacon is a management frame of subtype 8, a deauth is management subtype 12, an ACK is control subtype 13.&lt;/p&gt;</description></item><item><title>WiFi in plain words: access points, stations, and the join dance</title><link>https://hexrogue.github.io/blog/wifi-ap-sta-how-devices-join/</link><pubDate>Fri, 30 Jan 2026 14:05:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wifi-ap-sta-how-devices-join/</guid><description>&lt;p&gt;A wifi network is not a thing you connect to. It is one device that decided to be a landlord, plus every device that agreed to rent. The landlord sends a name tag ten times a second and calls it customer service.&lt;/p&gt;&#10;&lt;p&gt;The landlord is the access point, or AP. It holds the network name, sets the rules, and bridges the air to the wired side of the world. The tenants are stations, or STA. Your phone is a station. Your laptop is a station. The TV, the printer, and the ESP32 on my desk are stations. In most homes the AP and the router are the same plastic box, which is why everyone uses the two words for one thing.&lt;/p&gt;</description></item><item><title>I Pointed Shodan at My Own IP</title><link>https://hexrogue.github.io/blog/i-pointed-shodan-at-my-own-ip/</link><pubDate>Thu, 14 Aug 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/i-pointed-shodan-at-my-own-ip/</guid><description>&lt;p&gt;Last month I searched for myself on the internet. Not my name. My IP address. What came back was a list of my open doors, written up neatly like a menu. It was the digital equivalent of finding your house listed on a tour guide, with photos of the unlocked windows. I had published myself and never noticed.&lt;/p&gt;&#10;&lt;h2 id="shodan-is-google-for-machines"&gt;Shodan is Google for machines&lt;/h2&gt;&#10;&lt;p&gt;Google indexes websites. Shodan indexes everything else: routers, cameras, servers, smart fridges with opinions. It knocks on every door on the internet, writes down who answers and what they say about themselves, and puts it in a search bar.&lt;/p&gt;</description></item><item><title>What Your Smart TV Says at 3 AM</title><link>https://hexrogue.github.io/blog/wireshark-tips-read-your-network/</link><pubDate>Mon, 28 Apr 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wireshark-tips-read-your-network/</guid><description>&lt;p&gt;Wireshark does not ease you in. My first capture was a wall of packets, and I understood zero of them. It looked like a spreadsheet had a panic attack. Three filters later, it looked like a spreadsheet with a therapist. The panic turned into a reading list.&lt;/p&gt;&#10;&lt;p&gt;I wish someone had handed me this version on day one.&lt;/p&gt;&#10;&lt;h2 id="capture-everything-then-filter-like-you-mean-it"&gt;Capture everything, then filter like you mean it&lt;/h2&gt;&#10;&lt;p&gt;Start a capture on your WiFi interface and you will see hundreds of packets per second. Do not read them. You would be drinking from a firehose. Learn three filters on day one. &lt;code&gt;ip.addr == x.x.x.x&lt;/code&gt; shows one device. &lt;code&gt;dns&lt;/code&gt; shows name lookups. &lt;code&gt;http&lt;/code&gt; shows unencrypted web traffic. Ninety percent of beginner questions die to one of these three.&lt;/p&gt;</description></item><item><title>I Deleted Ads at the DNS Level</title><link>https://hexrogue.github.io/blog/dns-level-ad-blocking/</link><pubDate>Mon, 08 Jul 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/dns-level-ad-blocking/</guid><description>&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/green-hills.jpg" alt="What the internet looks like with DNS filtering"&gt;&#10;&lt;figcaption&gt;What the internet looks like with DNS filtering. Probably.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;Last time I caught my TV phoning home at 3 AM. Readers asked what I did after the VLAN. The answer: I stopped the calls from leaving the house at all. Not with an ad blocker in the browser. With a bouncer at the DNS. The bouncer is a text file and a bad attitude.&lt;/p&gt;</description></item><item><title>My TV Was Spying on Me</title><link>https://hexrogue.github.io/blog/my-tv-spying-homelab/</link><pubDate>Mon, 09 Oct 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/my-tv-spying-homelab/</guid><description>&lt;p&gt;I bought a used router to flash OpenWrt on a bored Saturday. The plan was simple: better WiFi. Three weeks later I had VLANs, WireGuard back home, and a spreadsheet of every domain my TV talks to at 3 AM. The spreadsheet was not part of the plan. The spreadsheet is never part of the plan. This is how that happens. Nobody plans a homelab. It accretes.&lt;/p&gt;&#10;&lt;h2 id="it-started-with-one-vlan"&gt;It started with one VLAN&lt;/h2&gt;&#10;&lt;p&gt;The TV was the trigger. It wanted internet for Netflix and nothing else, but it knocked on telemetry endpoints all night. So it got its own VLAN with no access to the rest of the LAN, DNS forced through my filter, and inter-VLAN routing denied by default.&lt;/p&gt;</description></item></channel></rss>