A Home Wi-Fi Extender That Stays on the House LAN

A home Wi-Fi extender is a small board that joins the router you already pay for and offers a second WPA2 network a room or a yard farther away. rusty_esp_wifi_extender is the Janus crate for that job. The radio physics, and why one hop costs about half the rate, are on an ESP device as a Wi-Fi repeater and extender. This page is the bench. It says what ran, how dldeploy is meant to hand the image to a house, and how that same board talks to the home computer. It does not offer a download.

The family the crate belongs to is Remade With Rust. The machine that should own the household's access, rather than a vendor account, is the MATA home computer. The extender does not replace that computer. It gives the rooms the router cannot hear a way to stay on the same LAN.

What a home Wi-Fi extender does on one radio

One ESP32-C6 is a WPA2 station on the house network and a WPA2 access point for its own clients at the same time. Phones and laptops that join the second network can reach the house LAN. There is no vendor cloud in that forward. Espressif's Wi-Fi guide is the vendor description of a station and an access point sharing one radio. The firmware around that radio is house Rust. The radio blob itself remains Espressif's. The language of the house crates is Rust.

A station toward the router, an access point toward the room

The station faces the parent, which is the router or another extender. The access point faces the laptop, the phone, or the next board. Both sides are WPA2. The network name and the passphrase come from the board's settings, not from a binary baked for one kitchen. A home Wi-Fi extender that shipped with a stranger's passphrase compiled in would be the wrong object to leave on a shelf. Updates are accepted only from an image the maker signed. The key that signed the bench images is not the production key this site will use for a catalogue.

The rate a home Wi-Fi extender actually delivered

One client through the C6, measured on the bench: TCP down 5.7 to 6.2 Mbit/s, TCP up 166 kbit/s, a UDP echo of 49 or 50 packets out of 50, and a round trip of 3.4 to 4.4 ms. Ten minutes dropped 2 frames. Five stations held for ten minutes on the product firmware. An earlier open build held eight. Upload at 166 kbit/s is enough for a sensor and a thin page. It is a poor video call. A home Wi-Fi extender adds a place to stand, not a faster plan. The old public repeater trees people still flash, such as esp_wifi_repeater, were already in this neighborhood of a few megabits. The new number is that the house firmware held it, with WPA2 on both sides, without becoming a second authority for the whole network.

How dldeploy and the home computer take a home Wi-Fi extender

dldeploy is the door a household uses to put a cell on the shelf. Deploy an ESP32 at home in an afternoon is that door for a camera or a microphone today. A home Wi-Fi extender is the next image in the same shape: a signed firmware, a settings partition for the house network, and a device that mints its own identity. The C6 image and the camera image exist. They are signed with a bench maker key. A catalogue copy on this site waits on the production maker key. Until that key signs them, this page is the record, not the download.

A signed image, not a public download

You will not find rusty_esp_wifi_extender on crates.io, and this page does not link a repository. The tool is private, for houses that flash from dldeploy, the way the rest of the household tools are offered when they are ready. The product C6 reads its network from settings. The camera cell's network is still compiled in for the bench, which is a smaller change than a new radio. Choosing an ESP32 board is where the C6 and the XIAO ESP32-S3 Sense sit among the cells this house actually flashes.

The home node, and what MATA Home does not show yet

On the bench router the extender is its own device. It mints a did:mata, reports the stations behind it to the home's network node, and takes its parent from that node. That is the local-networking half: the extension stays in the house, and the node can see who is standing behind which board. Sticky placement, and routes that clear after the node restarts, ran on that bench and are not yet the build a household runs. The home computer's own screen for the device is a different wire. The MATA Home integration says that screen is still being built. Identity, the part that is already real, is rusty_esp_mid. Smart home access on your home computer is the access this extender is not pretending to replace.

Rooms where a home Wi-Fi extender earns its keep

The useful picture is a dead corner, not a second internet bill. A bedroom past a brick wall, a yard the router cannot hear, a garage one more hop out. A home Wi-Fi extender is the board already going to live there, doing this with the airtime it has left.

The porch camera that also covers the yard

A XIAO ESP32-S3 Sense ran the camera stream and the extender together. Over 16 minutes the stream held 16.31 frames per second while a client's traffic was relayed, against 16.26 frames per second with the camera alone. The relayed client still had about 1 Mbit/s down at 4 ms, because the camera declares its need and the relay yields. Outdoors, on a power bank, the same shape ran two hours on the porch: no restart, 27.68 frames per second, and 197,779 frames. rusty_esp_video is the camera page those frames belong to. That afternoon is a real use: a party in the yard, a laptop that needs the house LAN, a camera that does not drop its picture to carry the laptop. It is not a permanent outdoor install. No enclosure and no mains supply were part of the test. Bring the board in when the afternoon ends.

A second extender behind the first is the guest cottage or the garage. On the bench, traffic through two hops measured about 6.3 Mbit/s up and 6.4 Mbit/s down, at 4 ms, with no drops on that row. That chain is a different test from the single-client upload of 166 kbit/s. Both numbers stay in the article so neither one gets to wear the other's coat. The home node is what places the second board. Five hops of a store mesh, with a phone app and a claim about whole-home speed, is a different product.

The jobs a home Wi-Fi extender will not take

It will not do 5 GHz. It will not draw a map: fine timing on bare boards could not tell 1 metre from 3 metres, and this house does not claim a distance. A report of probe requests, for presence, exists and stays off unless the household turns it on. The report stays in the house. It is also not the device-to-device mesh. That mesh is rusty_esp_iroh, and it dials household devices by key. Repeating Wi-Fi so a laptop can join is a different sentence. The Connect vision keeps both in view. The Learn index lists what is timed on a board.

A home Wi-Fi extender is worth having when the router is fine and one room is not. The C6 carries WPA2 on both sides at a few megabits down. The porch camera can extend without giving up its frames. dldeploy is where the signed image belongs, once the production key signs it. The home node is where the board reports who joined. None of that is a public file today.