This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Many devices ship with a private address for the first browser session. The lookup drafts an address from a brand you type. Use it only on an isolated lab lead, with one laptop, not on a network that already uses that address.
This page lists addresses, not passwords. A default password is something you change before you do anything else, and it is not printed here. If a device still has a default password, the hardening page is the next ticket.
Do not use a default address to reach a device you do not own. A sticker address on your lab bench is the whole scope.
After the first login, set an address from your plan and remove the device from the isolated lead only when the password is no longer the default.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Identify the device you own.
- Look up the likely first-boot address.
- Connect it on an isolated lead.
- Change the password before any other work.
- Plan the real address.
- Do not attach it to a live LAN while the password is still the default.
Mistakes that outlive the command
Default Router IP Addresses by Brand goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A default password left in place.
- The device joined a live LAN first.
- A password list collected.
- Someone else's device addressed by a well-known default.
- The lookup treated as a way in.
Decisions to write down
One decision for Default Router IP Addresses by Brand: The device is yours. The first session is isolated. The password is changed. No password was written down here. And the live LAN waits.
Checks before you call it done
Confirm this before you call the change done: The brand and the lab address are in the ticket. The password was changed. The note contains no password. The device was not placed on a live LAN early. And the permanent address is a follow-up. If one of those fails, stop.
Isolated lab lead. Change the password.
This page has no password list.
Before you leave the device
Default Router IP Addresses by Brand ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.