rusty_esp_wifi_extender: House Wi-Fi That Stays on the LAN

A dead corner of a house is usually a second router, a store repeater, and another account. rusty_esp_wifi_extender is the other shape. An ESP32 cell that was already going to live in that corner, a camera, a presence board, a mesh node, also extends the house Wi-Fi. The bytes stay on the LAN. The home that places the cell is MATA Home.

The product door is dldeploy.com. The seam those boards already aim at is DLDeploy on MATA Home. The field notes beside it are dldeploy in the wild and MATA.NETWORK in the wild. The public family those cells are built from is Remade with Rust.

A cell that already lives in the dead corner

rusty_esp_wifi_extender is a Janus crate for that job. One ESP32-C6 joins the house network as a WPA2 station and hosts its own WPA2 network for the clients in the room, with translation between them so an ordinary router can be the parent. The network name and passphrase come from the board's own settings, not from the build. A board with no network offers a first-run setup over Bluetooth, then restarts as the extender. Hold the boot button and it forgets the network and returns to setup.

The crate is a funnel, not a second gate. It forwards and it names who is behind it. It does not grow its own firewall, its own access list, or its own story about who may speak. Those questions stay with the home node. A phone behind the cell is still that phone.

One radio, two jobs

One radio receives a frame and sends it again, so the relay is coverage, not a second backbone. On the product firmware, one client through the cell measured about 5.7 to 6.2 Mbit/s down, a round trip of about 3.4 to 4.4 milliseconds, and 49 or 50 of 50 UDP echoes. The uplink on that run was about 166 kbit/s, and the bench notes say the test client's own upload capped it, including on the direct rounds. Five stations held for 10 minutes. A two-hour soak kept a single boot, closed its books, and dropped only the first frames of a new client while the next hop resolved. A 10-minute call-like flow held. When the upstream radio dropped for 15 seconds, clients stayed associated and forwarding resumed.

Those are bench figures on boards close together, a floor rather than a catalogue speed. rusty_esp_wifi_extender is not Wi-Fi certified. The point of the numbers is the shape: a far room can hold a phone, a tablet, and the cell's own job, and the process comes back up by itself.

The camera keeps its frames

The same idea on a camera board is the use people actually feel. A XIAO ESP32-S3 Sense ran the camera stream and the extender together. Across a 16-minute comparison the stream held at about 16.31 frames a second while relaying, against about 16.26 alone. The relayed client still had about 1 Mbit/s down at about 4 milliseconds. The camera declares what it needs, and relayed traffic yields. The public still and video path those frames sit on is rusty_esp_video. The radio family is rusty_esp_signal.

Out on a porch, on a power bank, that camera cell ran two hours without a restart, about 27.68 frames a second, with the router at about −49 dBm. That is an afternoon in the yard, not a weatherproof permanent install. No enclosure and no permanent supply were the thing under test.

How it lands in DLDeploy and MATA Home

dldeploy.com is the household mesh: cameras, microphones, and presence sensors that stay home. rusty_esp_wifi_extender is the role a cell takes beside that job. When the room is out of reach, rusty_esp_wifi_extender is the cell the home node places there. You do not buy a repeater and then wonder where to hide it. The board you were already going to put in the nursery, the garage, or by the back door is the extender. Its own stream or sense reading comes first. The Wi-Fi the room was missing is what the radio does with the airtime that remains.

DLDeploy is the door

rusty_esp_wifi_extender is not on crates.io, and this note does not offer a repository to clone. The household meets it through DLDeploy, the way the rest of the home tools are met. Flashing from the website, and a production catalogue image, are still ahead of a drive-by download. What is true now is the bench: WPA2 on both sides, memory-safe Rust, and an update the device accepts only when the image is signed and newer. A bad signature is refused. An image that never confirms itself rolls back. The mesh those updates ride is local. The argument for keeping a camera's view in the house, rather than on a vendor cloud, is the local camera that still left the house.

The home node places the parent

Deploying into MATA Home means the cell peers with the house Lighthouse node as its own device key. The node sees the stations behind the extender, and it chooses the parent. An extender can sit behind another extender. On that chain the bench measured about 6.3 Mbit/s up and 6.4 Mbit/s down, about 4 milliseconds, and no drops. Sticky placement keeps a cell from flapping to a parent that is only a little louder.

Behind an ordinary router the cell translates, so the house Wi-Fi works without a special parent. Bridge mode, a true layer-2 extension, is for a verified Lighthouse parent, and it is not the mode the one-chip esp-radio product uses. The public endpoint family for local devices is rusty_esp_iroh. The map of the mesh is Vision.

What a house can do with the bench we already ran

The uses below are the ones the measurements already support. They are not a second gigabit network, and they are not a map the boards draw of themselves. Ranging between bare boards could not tell one meter from three, so this note does not claim distance or a self-drawn floor plan.

The far room, the porch, the second hop

A back bedroom where calls drop is the first one. A sense board or a camera was going there anyway. With rusty_esp_wifi_extender, the tablet in that room joins the cell. Five stations held together on the product firmware. The home node can say which phone is behind which cell, so a guest laptop in the garage is still that laptop.

A porch afternoon is the second. You answer the door on a phone that has joined the camera's extended network, and the camera keeps its frames. Two hours on a power bank, then you bring the board in. Presence, if you want it, is a separate switch: the cell can report probe requests it already hears, off unless the household turns it on, and the report stays on the home node. It is not a vendor analytics feed.

A long lot is the third. A second cell by the shed, placed by the node, carries a workshop tablet and a sensor through two hops at about 6 Mbit/s and a few milliseconds. Enough for a call and a reading. Not a reason to retire the house router.

What this note will not claim

rusty_esp_wifi_extender is not certified Wi-Fi, not a public crate, and not a finished weatherproof outdoor product. A rusty_esp_wifi_extender cell extends the household LAN, and it stops there. It does not decide who may join. It does not draw a map. The household door is dldeploy.com. The home that places the parent and keeps the station list is mata.network. Read next: DLDeploy on MATA Home, rusty_esp_video, rusty_esp_signal, rusty_esp_iroh.