<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Esp32 on Muhammad Nuh</title><link>https://hexrogue.github.io/tags/esp32/</link><description>Recent content in Esp32 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>Fri, 28 Aug 2026 14:55:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/tags/esp32/index.xml" rel="self" type="application/rss+xml"/><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>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>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>