rusty_esp_wifi_extender Extends House Wi-Fi From the Board

A rusty_esp_wifi_extender is one board doing two radio jobs. It joins the house network as a station, and it offers its own WPA2 access point to the phones and laptops in the corner the router cannot reach. Traffic between those clients and the house crosses a small NAT on the board. The board does not become a second landlord. It is a funnel into the network the house already has.

Janus built the crate for that job. A camera, a sense node, or a plain ESP32-C6 can carry it. The household flash path is DLDeploy. The machine that should hold the result is the Home Computer, and the companion those rooms plug into is Era 4. The family of crates is Remade with Rust.

Trust is a device key on the board, so the home node sees that board and not a stranger. Security is WPA2 on both sides, a maker-signed update, and a rollback when a new image never comes up. Incentive is coverage you get because a board was already going to live in that room, not a mesh subscription for the back bedroom. The Electronic Frontier Foundation has the file on home gadgets that phone a vendor for a feature the hallway could have kept. This one stays on the LAN.

A rusty_esp_wifi_extender Is a Funnel, Not a Second Router

The extender forwards, and it attributes. It does not decide who may join, and it does not run its own firewall, its own DNS, or a rate policy. Those questions belong to the home network node. A phone behind the extender stays a phone, not one blob named after the board.

One radio does both jobs, so a relayed frame is received and then sent again. Coverage is the point. A direct link to the router will still be faster. On a clean bench link, one client through the extender moved 8.4 Mbit/s up and 10.7 Mbit/s down, with a ping of 3 ms. Straight to the router the same laptop was several times that, and the bench sat close to the router. A long hallway will not copy those rates. Five stations, three boards and two phones, held for 10 minutes on the product firmware with no reset. NISTIR 8259 is the baseline for a connected device that should say what it does. This firmware is not Wi-Fi certified. The address rewrite follows the usual home pattern in RFC 4787: the board lets the corner share the house link, and it does not invent a policy on top.

Updates ride the board's own page. A signed image that is newer can land. The same version is refused. A bad signature is refused. An image that boots and never becomes valid rolls back to the one that did. On a chip that has a key, the Wi-Fi passphrase and the device key are sealed. A dumped flash is not a readable passphrase.

DLDeploy Puts a rusty_esp_wifi_extender on the Home Computer

DLDeploy is how a household flashes an ESP32 and grants it to the owner. rusty_esp_wifi_extender is the firmware for when the job is the dead corner. First run does not start in a vendor console. The phone sends the house Wi-Fi over Bluetooth. The network name lives in the board settings, not baked into the image. Hold the boot button and the board can be set up again. The catalogue card that offers this exact image on dldeploy.com is the step we are putting on that path now. The firmware, the Bluetooth handoff, and the report to the home node are already what the bench runs.

The house network arrives over Bluetooth

You are standing in the room that needs the signal. The portal walks the flash, then the phone hands the board the network it should join. The board comes up as a station on that network and as an access point for whatever you point at it. Its own page lists who is associated, and a newer signed image is posted to that same page. No cloud is assumed for the update. There is no account in someone else's region required for the page to exist. If the house router is a 2.4 GHz network the board can hear, that is the parent. The corner then has a network of its own, still inside the house.

The ESP32 Wi-Fi extender reports each phone as itself

Once the board can see the home network node, it peers with a device key the node can verify. On the bench that peering admitted the board, and the moment a client joined, the node logged one station behind that extender. The listing is the attribution. The phone is not metered as if the board were the customer. mID on the chip is the same idea of a key that is still the device after a reflash. Janus is the doorway that key uses to reach the house. Local networking here means the node in the house learns who joined, and the packet did not leave to ask a vendor who is in the back room.

The Home tab is where a paired board shows up

DLDeploy already tells the owner what a MATA home does after setup. A Home Computer on the same network finds a paired device, checks that it belongs to you, and places it on the Home tab. Nothing else to click for that placement. The extender's verified report is the station list to the node that lives with that Home Computer. That is how an ESP32 Wi-Fi extender deploys into the home tool: flash, pair, and the corner's clients become stations the house can name. The Freedom Guide is the longer walk through putting the Home Computer in the house first. The extender assumes that computer is the address. It does not recruit a second one.

Rooms a rusty_esp_wifi_extender Already Covered on the Bench

These are bench rooms, not a promise for every floor plan. One radio, the router still the fast path, the board there because something else needed to be there. The access point can also report the probe requests it hears, for a presence check that stays in the house. That report is off unless the household turns it on. It is not a floor plan. Ranging on bare boards could not tell one meter from three, so this crate does not draw a map.

The back room where the router gives up

Put the ESP32-C6 where the hallway dies. It joins the router you can still hear and offers WPA2 to the room you are standing in. Five stations held together for 10 minutes. That is a couple of phones and the other boards in the room, not a crowd. A call on that link held on the bench. A giant upload still wants the router. The win is that the back room has a network at all, and the authority for that network is still the house. A laptop on the bed joins the board. The board joins the router. Nobody opens an account to watch the signal bars.

A porch camera that is also the rusty_esp_wifi_extender

A XIAO ESP32-S3 Sense can run the camera and the extender on one board. On the bench the MJPEG stream held about 16 frames a second while a client's traffic was relayed through it, and about the same rate with nobody relaying. The camera declares what it needs. Relayed traffic yields. The same shape ran two hours on a power bank on a porch, still streaming, still associated to the router, and it did not restart. That is a visit outside, not a weatherproof enclosure and not a claim about permanent power. The stream itself is the work in a camera without a cloud. The extender is what the radio does with the airtime the camera is not using. Someone on that porch joins the board instead of begging the router through the wall.

A shed one hop past the first board

An extender can sit behind another extender. The home node picks the parent, so the second board does not guess forever and loop. On the bench, two hops still moved about 6 Mbit/s each way, around 4 ms, with no drops in that run. A shed, a garage, or the far side of a yard is the room that sentence is for. The second board does not open a second account. It is another funnel, and the node still sees the stations behind it as themselves. Era 4 is the companion those rooms report to. esp32 iroh is the mesh for the jobs that are not this Wi-Fi hop. rusty_esp_wifi_extender is the hop: house Wi-Fi, one more room out, still on the LAN.