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
An IPv4 address is four octets. Binary is how a mask lines up. Decimal and hex show up in captures and in some identifiers. The converters change the form. They do not configure a host.
Convert one address you may hold, or a documentation address. A page of other people's addresses is not practice. Check that the binary has 32 bits and that the dotted form still has four octets.
The converted form is not a new address plan. Write it beside the original so the next person can see they are the same address.
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.
- Pick one address.
- Convert it.
- Count the bits.
- Write the original beside the result.
- Do not build a plan from the conversion.
- Do not configure a device.
Mistakes that outlive the command
How to Convert IP Addresses to Binary, Decimal and Hex goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Dropping a leading zero in hex and changing the value.
- A binary string that is not 32 bits.
- Converting a list you were not allowed to hold.
- Treating the hex form as a different host.
Decisions to write down
One decision for How to Convert IP Addresses to Binary, Decimal and Hex: One address was converted. The bit length is 32. The original is still in the note. The address is yours or documentation. And no device was changed.
Checks before you call it done
Confirm this before you call the change done: Both forms are written. The bits were counted. They name the same address. No list was harvested. And the device was left alone. If one of those fails, stop.
Before you leave the device
How to Convert IP Addresses to Binary, Decimal and Hex 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.