<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wifi on Muhammad Nuh</title><link>https://hexrogue.github.io/tags/wifi/</link><description>Recent content in Wifi 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/wifi/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>Decrypting your own WPA2 traffic in Wireshark</title><link>https://hexrogue.github.io/blog/decrypt-wpa2-traffic-wireshark/</link><pubDate>Fri, 11 Sep 2026 20:10:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/decrypt-wpa2-traffic-wireshark/</guid><description>&lt;p&gt;A monitor mode capture is mostly noise: beacons, management frames, and encrypted data you cannot read. It is the digital equivalent of taping a conversation through a wall and getting a very detailed recording of the wall.&lt;/p&gt;&#10;&lt;p&gt;Wireshark will decrypt your own WPA2 traffic if you give it the passphrase and the capture contains the handshake. Miss either one and you have a very expensive screensaver. The gap between those two conditions is where most people get stuck.&lt;/p&gt;</description></item><item><title>Building the ESP32 recon rig for real</title><link>https://hexrogue.github.io/blog/esp32-recon-rig-build-guide/</link><pubDate>Fri, 28 Aug 2026 14:55:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/esp32-recon-rig-build-guide/</guid><description>&lt;p&gt;The driver post was about the kernel refusing to let the board talk. This one is the build: what to buy, how it is wired, how it flashes, and the things that wasted an evening. It is the IKEA instruction manual of wifi hardware, except the allen key is a USB cable and the missing screw is your evening. It is written for a board pointed at your own network, and the rules for that are on &lt;a href="https://hexrogue.github.io/lab-rules/"&gt;the lab rules&lt;/a&gt; page.&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>WPA3 SAE, without the fairy tales</title><link>https://hexrogue.github.io/blog/wpa3-sae-dragonfly-handshake/</link><pubDate>Sat, 01 Aug 2026 17:40:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wpa3-sae-dragonfly-handshake/</guid><description>&lt;p&gt;WPA3 has a reputation problem. Marketing calls it unhackable, forums call it broken, and both are wrong in useful ways. The honest version is narrower and more interesting: WPA3 kills the offline dictionary attack, which is the technique most people mean when they say their wifi got hacked.&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/memes/meme-wpa3-fine.jpg" alt="This Is Fine dog meme: WPA3 is unhackable while transition mode quietly keeps WPA2 alive"&gt;&#10;&lt;figcaption&gt;Marketing says unhackable. Transition mode says hold my WPA2.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="the-thing-sae-removes"&gt;The thing SAE removes&lt;/h2&gt;&#10;&lt;p&gt;Start with what WPA2 gives an attacker. The passphrase becomes a key, the four-way handshake derives session keys, and the whole exchange is readable on the air. A recording contains everything needed to test guesses at home, at full speed, on a machine that never has to touch the network again. The cracker is not attacking your router. They are attacking a file.&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>How a captive portal works, and how to build one on an ESP</title><link>https://hexrogue.github.io/blog/esp-captive-portal-explained/</link><pubDate>Fri, 03 Jul 2026 21:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/esp-captive-portal-explained/</guid><description>&lt;p&gt;Join a hotel wifi, and before you type anything, your phone opens a login page. Nothing is installed and nobody told you to look, yet the page appears. It is the digital equivalent of a hotel clerk sliding a form under the door before you have taken off your shoes. Two old tricks stacked on each other put it there, and both are small enough to run on the ESP32 on my desk.&lt;/p&gt;</description></item><item><title>Beacon spam: how the air fills with junk network names</title><link>https://hexrogue.github.io/blog/beacon-spam-and-the-wifi-list/</link><pubDate>Tue, 12 May 2026 09:05:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/beacon-spam-and-the-wifi-list/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/80211-frames-you-can-read/"&gt;A beacon&lt;/a&gt; is the simplest frame in wifi. A router announces its name about ten times a second, on its channel, to nobody in particular. It is unsigned, it is unencrypted, and any radio can transmit one.&lt;/p&gt;&#10;&lt;p&gt;Your phone treats that announcement like a guest list. No bouncer, no ID check, no guy named Chad at the door asking if you are on the list. Anyone with a radio can add a name. Copy that frame at scale and you have beacon spam.&lt;/p&gt;</description></item><item><title>Cracking your own password: from PMKID to hashcat</title><link>https://hexrogue.github.io/blog/cracking-your-own-password-pmkid/</link><pubDate>Wed, 29 Apr 2026 19:45:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/cracking-your-own-password-pmkid/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/80211-frames-you-can-read/"&gt;The PMKID is a coat-check ticket&lt;/a&gt;: a blob the router hands out before any real authentication, derived from your wifi passphrase. This post is the other half, the part where the ticket becomes a password. On your own network, in your own lab, which is the only version of this that belongs on a blog. It is also the closest thing wifi has to a receipt that says &amp;ldquo;your password is probably fine, but let&amp;rsquo;s check.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Watching your own air: rogue access points and evil twins</title><link>https://hexrogue.github.io/blog/watching-your-own-air-rogue-aps/</link><pubDate>Tue, 07 Apr 2026 11:10:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/watching-your-own-air-rogue-aps/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/"&gt;Recon&lt;/a&gt; gives you a table of every radio in range. This post is about the one entry that should not be there.&lt;/p&gt;&#10;&lt;p&gt;It is the wifi equivalent of finding a second front door on your house, with a welcome mat that has your name on it.&lt;/p&gt;&#10;&lt;p&gt;A rogue access point is any access point that is not part of your inventory. There are two shapes of it. The boring one is a real access point, plugged into your network, that nobody documented, usually a spare router someone enabled because the wifi was slow. The interesting one is not on your network at all: it is a second radio wearing your network&amp;rsquo;s name, broadcasting to your devices, waiting for them to join it.&lt;/p&gt;</description></item><item><title>WPA2, WPA3 and PMF: what actually stops the attacks I wrote about</title><link>https://hexrogue.github.io/blog/wpa2-wpa3-pmf-what-stops-them/</link><pubDate>Tue, 31 Mar 2026 16:30:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wpa2-wpa3-pmf-what-stops-them/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/"&gt;The deauth post&lt;/a&gt; ends with a promise: the fix is management frame protection, and modern gear just ignores a forged eviction notice. That is the short version. The long version is that wifi security has two generations, and the reason half the networks you can see are still forged-frame food is a compatibility setting. This post is the part where the promise meets the router menu, and the router menu is a swamp.&lt;/p&gt;</description></item><item><title>Passive recon: what a listener learns without joining anything</title><link>https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/</link><pubDate>Sun, 15 Mar 2026 08:50:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/</guid><description>&lt;p&gt;Your phone&amp;rsquo;s wifi chip has opinions. It only hands the operating system frames addressed to it or to the network it belongs to, and it drops the rest without ceremony. It is the digital equivalent of a bouncer who only lets in people on the list, and then someone shows up with a clipboard and a monitor-mode adapter. Promiscuous mode turns that filter off and keeps everything the radio can hear.&lt;/p&gt;</description></item><item><title>Deauth: the 26 bytes anyone can forge</title><link>https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/</link><pubDate>Fri, 06 Mar 2026 20:15:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/</guid><description>&lt;p&gt;A deauth frame is a wifi eviction notice. It says one thing: you are no longer associated with this network. Twenty-six bytes that prove nothing about who sent them.&lt;/p&gt;&#10;&lt;p&gt;That missing proof is the entire story. It is the bureaucratic version of a bouncer throwing you out and then handing you a form that says &amp;ldquo;we have no idea who did this.&amp;rdquo;&lt;/p&gt;&#10;&lt;h2 id="the-frame"&gt;The frame&lt;/h2&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;c0 00 &amp;lt;- frame control: management frame, subtype 12 (deauth)&#10;3a 01 &amp;lt;- duration, filler, ignored&#10;ff:ff:ff:ff:ff:ff &amp;lt;- address 1: the target. broadcast means everyone listening&#10;02:11:22:33:44:55 &amp;lt;- address 2: who sent it (supposed to be the access point)&#10;02:11:22:33:44:55 &amp;lt;- address 3: which network this concerns&#10;f0 ff &amp;lt;- sequence number&#10;02 00 &amp;lt;- reason code 2: previous authentication no longer valid&#10;&lt;/code&gt;&lt;/pre&gt;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/diagrams/deauth-frame-layout.svg" alt="Byte by byte layout of the 26 byte deauthentication frame"&gt;&#10;&lt;figcaption&gt;The whole 26 bytes, laid out. Six of them hold the sender's address, and none of them are proof that the sender is who they claim.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;The first byte pair &lt;code&gt;c0 00&lt;/code&gt; is the giveaway. The top bits of &lt;code&gt;0xc0&lt;/code&gt; say management frame, the rest say subtype 12. Disassociation is the sibling, subtype 10, byte &lt;code&gt;a0&lt;/code&gt;. Over the air the two look nearly identical and are used the same way.&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 Taught a $5 Board to Sniff WiFi, Then Fought Its Driver</title><link>https://hexrogue.github.io/blog/esp32-recon-rig-driver-said-no/</link><pubDate>Mon, 12 Jan 2026 09:20:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/esp32-recon-rig-driver-said-no/</guid><description>&lt;p&gt;It started with an ESP32 plugged into my laptop and a simple question: what can this thing actually hear. It ended one long evening later with me disassembling a closed WiFi driver, downgrading an entire SDK for nothing, and learning more about 802.11 frames than any lecture ever taught me. The answer was &amp;ldquo;more than the driver wanted me to know,&amp;rdquo; which is how a five-dollar board turns into a vendetta. The board now runs a recon dashboard I built from scratch. This is the whole story, including the part where I was wrong in public.&lt;/p&gt;</description></item></channel></rss>