Author: Professor Lamb

Before every packet leaves, your computer asks one question: is this destination on my street? Yes means deliver it directly through the switch. No means hand it to the default gateway, the router’s address on your street (a door you cannot reach is not a door).

The subnet mask is how the computer answers. Where the mask says 255, that part of the address is street. Where it says 0, that part is house. So 255.255.255.0 under 192.168.10.5 means the street is 192.168.10 and the house is 5. Change the mask and you move the end of the street. With 255.255.0.0, the street becomes 192.168, and 192.168.20.6 suddenly counts as same street. Same two addresses, different mask, different answer.

Basically, the mask decides where the street ends. One street is one network and one broadcast domain. Every machine on that street has to stop and read every broadcast. Too many machines on one street, and they spend the day listening to shouting. So we cut big streets into smaller ones. Week five only draws the line between street and house. Later weeks take the line apart bit by bit. The skill that matters first is hearing the question: same street?

A MAC address names the network card. It is burned in at the factory. It says which card, and nothing about where the card is right now. Nobody delivers mail to a serial number. So every device gets a second address that says which network it sits on. That is the IPv4 address.

An IPv4 address is a 32-bit number. Humans write it as four numbers from 0 to 255 with dots between them (dotted decimal), like 192.168.10.2. The machine never sees the dots. It sees thirty-two ones and zeros. Each of those four numbers is an octet: eight bits, which is why no octet ever goes past 255. The front of the address is the street (which network). The back is the house number (which device on that street). Routers care about the street.

Basically, MAC is identity of the hardware; IP is location on the map. Floor two never leaves the building. Floor three is the address that does. Everything that sends or receives a packet needs one: laptops, printers, phones, cameras, and managed switches (so you can talk to the switch, not so it can switch). A Mac address names the card. An IP address names where it is.

Most of the copper in a building is twisted pair: eight wires in four pairs, each pair twisted around itself. The twist is not decoration. It is the entire engineering. Two wires twisted together cancel each other’s interference. Alexander Graham Bell patented that idea in 1881 to keep streetlight noise out of telephone lines. We still use it.

Crosstalk is the enemy, signal leaking from one wire into the next. Tighter twists mean less crosstalk and a faster cable. Category ratings are the grade of that fight. Three numbers are worth saying out loud. Cat 5e does one gigabit to 100 meters. Cat 6A does ten gigabit to 100 meters. Cat 8 does forty gigabit, but only about 30 meters, which is why it is a data center answer and not a building answer. Cat 5e is the floor. Nothing below it belongs in a network today.

U T P (unshielded) is almost every cable in the walls. S T P (shielded) wraps the pairs in foil or braid for noisy places: factory floors, elevator shafts, runs beside power. Do not walk the whole Category table from one to eight. Six of those rows are obsolete telephone grades. Students need three facts, not eight rows. The twist is why the cable works. The Category number says how far and how fast before crosstalk ruins it.

Every link in every network on earth is copper, fiber, or radio. There is no fourth thing. That sentence is the organizing idea for a whole week of ITN 101, and it survives long after Category numbers fade.

Copper carries electricity. It is cheap, easy to terminate, and it picks up noise. Fiber carries light down a glass or plastic core. Because there is no electricity in the cable, motors, elevators, and power lines have nothing to grab; the trade is cost, kink sensitivity, and harder troubleshooting. Radio carries nothing at all. It just goes. Convenient, shared, and unpredictable (which is exactly why the wired links win in a classroom with historically bad Wi-Fi).

Transmission media is the physical stuff a signal travels through. Last week’s word was link, the connection between two nodes. This week we open the link and look inside it. The plural is media; the singular is medium. Hold those three families on the board and everything else hangs off them: twisted pair and coax under copper, single-mode and multimode under fiber, Wi-Fi and cellular under radio. If students leave with only one idea from the media day, make it this one. Copper, fiber, or radio. Pick the medium that matches the job.

Nobody frames a photo of a patch panel, but maybe they should. Cable management — the velcro, the horizontal managers, the service loops — is documentation you can touch. A rack where every cable runs in a channel and drops vertically to its port tells you the truth about itself. A rat’s nest tells you nothing, and it lies about everything.

The argument I make in ITN 101 is not about beauty. It is about the 2 a.m. version of you. That person is tired, the building is dark, and something is down. In a dressed rack, the tired person can trace a cable with a finger and be sure. In a tangled rack, the tired person starts unplugging things to see what happens, which is how a small outage becomes a big one.

Two rules do most of the work. First, velcro, never zip ties — because you will need to move that cable someday, and a zip tie turns a five-minute change into surgery. Second, leave a service loop: a little slack, neatly coiled, so the cable can reach one rack-unit up or down without being re-terminated. Slack is forgiveness, built in ahead of time.

Students hear this as housekeeping. It is closer to honesty. A network is a physical thing before it is a logical one, and the physical part keeps score.

Textbooks treat documentation as a chapter near the back. In ITN 101 we treat it as a habit that starts with a four-cent label.

The rule is simple: label both ends of every cable. Not one end — both. Because the end you can see is never the end you need. You are always standing at the wrong end, in a dim closet, holding a flashlight in your teeth, trying to decide whether the blue one goes to the printer or the camera. A label on the far end does not help you. A label in your hand answers the question.

Students groan at this. It feels like busywork, the networking equivalent of being told to clean your room. Then lab week three arrives, somebody’s link will not come up, and the team with labeled cables finds the fault in ninety seconds while everyone else plays cable roulette.

A label is documentation at the exact point of need, readable without logging into anything. Start there. The diagrams can come later, and they will be accurate, because the labels forced them to be.

Once you know a network is nodes connected by links, the next plain question is scale. How big is this thing? Network people answer with scope words: LAN, WAN, and a few cousins. The words are not fashion labels. They tell you roughly how far the links reach and who owns the space between them.

A LAN (local area network) is the network in one place you control: a classroom, a small office, one floor of a building. Ethernet and Wi-Fi live here. A WAN (wide area network) stretches across cities or continents. You usually rent the long haul from a carrier; the internet is the WAN most people mean. Between those poles sit useful middle sizes. A MAN covers a city or campus. A PAN is personal, phone to earbuds, a few meters of radio. A CAN is a controller network on a factory floor or in a vehicle.

Basically, start with distance and ownership, not the acronym. Is everyone under one roof with cables you can pull? That is LAN thinking. Are you crossing public infrastructure you do not own? That is WAN thinking. Day one of class deliberately refuses to chase LAN versus WAN before nodes and links are solid. The mesh lab builds the schema with hands. The labels come after the picture.

Textbooks love to open networking with the OSI model. Seven layers, two mnemonics, a stack of vocabulary before anyone has touched a cable. That is a clean map if you already know the building. It is a bad first week if you do not.

In ITN 101 we skip the layers early on purpose. Week one is nodes, links, and protocols, said in ordinary English. Weeks two and three are the stuff you can trip over: copper, fiber, radio, connectors, and the boxes in the rack. Only after students have held a patch cable and watched a switch learn a MAC address do we put floor numbers on those boxes. A hub is floor one. A switch is floor two. A router is floor three. Suddenly the map has somewhere to hang.

Basically, a model is useful when it names things you have already met. Before that, it is seven labels floating in air. The OSI model is still coming (Network+ tests it, and the industry speaks it). We just refuse to start there. Troubleshooting is the real payoff of layers: you check one floor at a time instead of guessing in a building with no numbers. That skill lands better once the cable, the frame, and the address are already in the room.