forcing my kids to make Ethernet cables // FREE CCNA // EP 11

Making an Ethernet cable is framed as both a practical skill and a CCNA rite of passage: the core takeaway is that most home and business networking problems can be avoided—or at least diagnosed—when someone understands how RJ45 pinouts map to transmit/receive pairs and how cable wiring choices affect real-world behavior. The walkthrough starts with the “why” behind DIY cabling: store-bought cables are convenient, but custom lengths and repairs are often cheaper and more flexible when cables are built to spec.

The supplies list is straightforward—Cat5e UTP cable, an RJ45 crimper, RJ45 connectors, and optionally a cable tester—then the process begins with removing the jacket. The method emphasizes scoring the outer sheath (not cutting into the copper), pulling it back, and exposing the four twisted pairs (eight conductors). From there, the video shifts into the engineering logic of Ethernet: the jacket helps, but the real anti-noise strategy is twisting wires into pairs to reduce electromagnetic interference (EMI) and crosstalk. Because the cable is unshielded twisted pair (UTP), it relies on that twisting plus the outer jacket; shielded twisted pair (STP) adds an extra shielding layer for harsher EMI environments.

The explanation then ties cable construction to how Ethernet endpoints communicate. Copper conductors carry electrical signals that represent data by changing voltage levels. On a basic fast Ethernet model, one pair is used for transmit (TX) and another for receive (RX), and the RJ45 connector’s pinout matters because devices are programmed to send on specific pins and listen on others. A straight-through cable works when connecting dissimilar device types—typically an endpoint (like a PC or Raspberry Pi) to a switch—because the switch’s transmit/receive pin mapping matches the endpoint’s expectations.

That mapping becomes the reason crossover cables exist. When two similar endpoints are connected directly (e.g., Raspberry Pi to Raspberry Pi), a straight-through wiring can cause both ends to transmit on the same pins and listen on the same pins, resulting in a “talking to the ears” failure. A crossover cable fixes this by swapping the relevant pairs so each device transmits to the other device’s receive pins.

The video then updates the story for gigabit Ethernet (1000BASE-T) using Cat5e: with 1000BASE-T, each pair can send and receive simultaneously, so the strict need for crossover largely disappears in practice. Auto MDI-X on switches detects whether pins should be swapped and adjusts automatically. Still, the construction details remain crucial: the straight-through Cat5e pinout uses the 568B standard, with a specific order of white/orange, orange, white/green, blue, white/blue, green, white/brown, brown. The tutorial culminates in a hands-on build and a tester-based verification step, where a properly wired straight-through cable should show matching pin numbers on both ends.

Finally, the session reinforces CCNA-style exam relevance: it quizzes viewers on 568B ordering, which pins handle TX vs RX (pins 1–2 and 3–6 in the fast Ethernet framing), and what can cause late collisions—highlighting that exceeding the 100-meter limit is a known trigger, alongside duplex mismatches. The overall message is that Ethernet cabling isn’t just “making ends fit”—it’s understanding pinouts, signaling, noise control, and distance limits so networks behave predictably.