TL;DR: An IPv4 address is four numbers, called octets, separated by dots, and each number must sit between 0 and 255. That is the whole notation. A generator is a way to see many legal examples quickly, including awkward ones, so you stop treating the dots as decoration. Read a draw from the random IP generator one octet at a time before you paste it into anything that will trust it.
The spreadsheet that thought dots were thousands separators
A logistics clerk exported a list of scanner gateways into a spreadsheet for a contractor. The column was stored as text until someone “fixed the formatting.” The sheet interpreted 10.2.3.4 as a date or a mangled float, depending on the locale, and the gateway list that came back had lost its dots. The contractor programmed three devices with values that were not addresses at all. The outage was a Saturday. The repair was retyping from a backup that had stayed text. Dotted decimal only works if the dots survive. A generator did not cause this one. A generator is how the clerk’s manager later taught the office to recognize a legal address so the next export would be checked by eye: four fields, three dots, nothing else.
What each piece is allowed to be
Each octet is an eight-bit number. In decimal that means 0 through 255 inclusive. 256 is already too big. Leading zeros are a second trap: 010 may mean 10 to a human and 8 to a tool that still honors octal. Do not pad. Do not write 192.168.001.010 if you can write 192.168.1.10. Spaces around the dots break strict parsers and slip through sloppy ones. A trailing dot is not part of the address. Four fields means four, not three with a port glued on.
- Legal: 203.0.113.5
- Not an octet: 203.0.113.500
- A port sneaked in: 203.0.113.5:443 is an address plus a port, not an address.
- Octal costume: 192.168.001.010 is a gift to the wrong parser.
- Missing a field: 192.168.1 is not a complete IPv4 address in this notation.
Use the generator as a stack of flash cards
Click several times and read every result aloud as four separate numbers. Notice how often a field is a single digit and how often it is three. Both are normal. Notice a 0 in the middle, which is legal and which people “correct” by deleting the field. Notice 255, which is legal as a number and special as a broadcast in many subnets. The notation does not tell you the subnet. It only tells you the four numbers. Meaning beyond that comes from a mask you must state separately.
Compare a bad string you type on purpose. 1.2.3, 1.2.3.4.5, and 1.2.3.999 should all fail a validator. If your form accepts them, the form is wishing. A generator that only emits legal quads will not test that failure. You have to bring the illegal strings yourself. The generator’s role is the positive examples and the variety.
Ports, masks, and brackets
People paste 192.168.1.5/24 into an address field. The /24 is a mask length, useful and not part of the dotted address itself. A good form either accepts the pair deliberately or strips nothing and rejects the slash. Brackets belong to IPv6 literals in URLs, not to IPv4. If a generated IPv4 value grows brackets or a slash on its way into a ticket, someone edited it. Put the mask in the next column.
Reading order in a log line
Logs glue the address to other tokens: a timestamp, a method, a status code. The address is still the token with exactly three dots and four decimal fields. Train your eye on generated examples written beside dates and beside ports until you can pick it out of a noisy line. The clerk’s spreadsheet failed because the cell stopped being text. Your eye is the backup parser. It only works if you remember the four-field rule when the software tries to be helpful.
IPv6 will try to interrupt this lesson with colons. Let it wait. Mixing the two notations in the first afternoon produces students who insert dots into IPv6 and colons into IPv4. Master the dotted quad, including the 0-to-255 rule, and only then put a colon-form address on the same slide with a label.
Ask the clerk to type one generated address into a cell formatted as text and another into a cell formatted as general, side by side, before the next export. The contrast is the lesson. The Saturday devices failed because nobody had seen the dots disappear in captivity. A generator gives you an unlimited supply of legal quads to sacrifice to the spreadsheet until the office believes the formatting warning.
Four numbers, three dots, no help from the spreadsheet
The Saturday outage was a formatting feature doing what it was built to do. Your defense is to recognize a dotted quad before you let a cell, a form, or a ticket rewrite it. Generate a handful, read them field by field, and reject anything that grew a fifth field or a three-digit disaster over 255. The notation is small. The damage from breaking it is a device that can no longer find its gateway.
