The process · Article 13
What an extender keeps in its own memory
Once paired, an extender remembers the router’s network name and key, the name and key it publishes itself, and the password to its own configuration page. Those stored copies are what let it come back after a power cut, and what stop it coming back when the router changes.
- Published by[OPERATOR NAME]
- Last checked27 September 2026
- Reading timeAbout 5 minutes
- ScopeGeneric, not model-specific
The short answer
An extender writes the settings it is given to non-volatile memory, the same kind a phone uses to remember networks. From then on it rejoins the router on its own each time it is powered, using the stored name and key, and publishes its own network using the stored settings for that. Nothing has to be repeated after the first pairing, and nothing is forgotten when the plug comes out. That is convenient until the router’s key changes, at which point the extender is faithfully offering a key the router no longer accepts.
What is stored
| Item | What it is for |
|---|---|
| The router’s network name and key | Rejoining the router as a client at every start. Some units store the key itself; others store a value derived from it that serves the same purpose. |
| The extender’s own network name and key | Publishing its network to devices. Either a distinct name with a suffix, or a copy of the router’s. The second network name explains the two. |
| The configuration-page password | Protecting the unit’s own settings page. Either the value printed on the unit, or one an owner has set. This is separate from every wireless key. |
| Band and channel settings | Which bands are in use, whether one is reserved for the link to the router, and any channel that has been pinned rather than left automatic. |
| Its network address, if set by hand | Most units accept whatever address the router assigns; one set by hand, where that has been done, is stored too. |
| Firmware | The unit’s own operating software, replaced as a whole when the maker issues a new version. |
| A short log | Recent events, kept in a small buffer and overwritten as it fills. Not kept across a return to factory state. |
What survives a power cut
Everything in the table. The memory is non-volatile, so a unit unplugged for a month and plugged in again starts, reads its stored settings, looks for the router by name, offers the stored key, and resumes. The only thing lost is the log buffer and the address the router had lent it, both of which are replaced within a minute of starting.
What the unit cannot store is the router’s consent. Each time it starts, it has to be accepted again by the router, using the stored key, and the router accepts or refuses on the key as it stands today.
What changes when the router changes
The extender knows the router by its network name and proves itself with the key. Anything that changes either breaks the pairing, and the extender has no way of learning the new value on its own.
- The router’s key is changed. The extender keeps offering the old one, is refused, and keeps trying. Its link light reports a lost link until it is paired again with the new key.
- The router is replaced by one with a different name. The extender looks for a name that no longer exists. It has never heard of the new router and cannot join it until paired.
- The router is replaced by one given the same name and key. The extender finds a network with the name it knows, offers the key, and is usually accepted, because it identifies the network by name and key rather than by the router’s hardware. Units that had noted the old router’s hardware address may take longer to accept the new one, but most resume.
- The household moves house. The extender arrives knowing a network that is now streets away, and behaves exactly as in the first case until it is paired with the new router.
The pairing itself does not need repeating for the extender’s own devices. Phones and laptops that joined the extender’s network keep their own stored copies of its name and key, which are unaffected by anything that happens on the router side. Once the extender is paired again, they rejoin it as before. Under the one-name arrangement, where the extender copies the router’s name and key, a change to the router’s key changes both, and every device in the house needs the new one.
A second-hand unit knows its previous home
A unit sold, lent or passed on without being returned to factory state still holds its previous owner’s network name and key in memory. Powered up within range of that network it will rejoin it; powered up elsewhere it will search for it. Its configuration page, opened by whoever now holds it, shows the stored name in plain text and may allow the key to be read.
The reverse case matters too. A unit bought second-hand arrives with someone else’s settings, someone else’s configuration password, and possibly a hand-set address that clashes with the new home’s. The return to factory state, described next, is what makes it a clean unit.
The return to factory state
Every unit has a way of erasing everything it has been given and returning to the state it left the factory in: no router, no keys, the printed configuration password, and the temporary pairing network it first published. The maker’s leaflet describes how that is invoked on a given model. What it does is the same everywhere: the stored settings in the table above are wiped, and the firmware is left in place.
Afterwards the unit is exactly as new, which means it is again advertising a temporary network and again waiting for the pairing exchange described in how extender setup works. Nothing about the return to factory state involves a website, a telephone call or anyone outside the home; it is a physical act on the unit, and the only party able to perform it is the one holding it.
The stored items and the behaviour after a change of key or router were compared against the published manuals of several makers of consumer extenders on 27 September 2026. Whether a given unit stores the key or a derived value, and how it identifies a replacement router, differ by model and are stated only in that model’s documentation.