RoleMath

Free training - skill primer

Learn Networking fundamentals for free

A free, source-cited path to learning how networks actually move traffic, practiced on your own connection — this is a learning path, not a certification and not a job guarantee. You learn networking by inspecting real packets and addresses on a machine you own, not by memorizing acronyms.

What it is

Networking fundamentals is the working knowledge of how devices address, connect, route, and exchange traffic across local networks (LANs) and wider networks (WANs). It is the shared foundation under support, system administration, cloud, and cybersecurity work: almost every problem in those fields eventually comes down to whether two machines can reach each other and why. Because the concepts — addressing, naming, and moving data reliably — are the same across every vendor and platform, this is one of the most transferable technical skills you can build, and you can learn it entirely from your own computer and home network.

The core building blocks are a small, durable set. IP addressing and subnets: how a device gets a unique address and how a subnet mask decides which addresses are 'local'. DNS and DHCP: the services that turn a name like a website into an address, and that hand out addresses automatically. Ports and transport: how TCP (reliable, connection-oriented) and UDP (fast, connectionless) carry application traffic, and how port numbers tell a machine which service a packet is for. The OSI and TCP/IP models: the layered mental map — physical, data-link, network, transport, and up to the application — that lets you say exactly where a problem lives. Routing and switching basics: how a switch moves frames inside a LAN and how a router forwards packets between networks. These are not trivia; they are the vocabulary you use to describe and fix real connectivity problems.

The fastest way to make the concepts stick is to inspect your own connection with the tools already on your computer and watch the abstractions become concrete: your machine really does have an IP address and a default gateway, names really do resolve to addresses, and packets really do take a path of hops to reach a destination. This primer sequences free, official-first resources and gives you a first hands-on exercise using built-in commands on your own network only — no special software and nothing that touches anyone else's systems.

Why it matters

Networking fundamentals is the common foundation beneath support, system administration, cloud engineering, and cybersecurity, because reachability and addressing underlie nearly every problem in those fields. The concepts transfer across every vendor and platform, so the skill compounds and follows you between employers rather than locking you to one product.

The free path, in order

  1. Build the mental model: OSI/TCP-IP and addressing. Learn the layered models and IP addressing/subnetting first — they are the map you use to locate every later problem. Cisco's free Networking Basics course and Professor Messer's Network+ videos both cover this cleanly.
  2. Learn the naming and addressing services. Understand DNS (names to addresses) and DHCP (automatic address assignment). Then find your own machine's IP, subnet mask, and default gateway so the concepts stop being abstract.
  3. Understand transport: TCP, UDP, and ports. Learn the difference between reliable TCP and fast UDP, and how port numbers route traffic to the right service. Map a few common services to their well-known ports.
  4. Trace how traffic actually moves. Use ping and traceroute/tracert on your own connection to see reachability and the hop-by-hop path to a public destination, connecting the routing concepts to real output.
  5. Look inside a packet (safely, on your own traffic). Skim the Wireshark documentation and, if you want, capture a little of your own traffic to see real headers. Observe only traffic on a network you own; never capture on networks you do not control.

Best free resources

Every resource is free and dated. Official sources are labeled; vetted community resources are labeled separately. Verify a resource is still free on its own page before relying on it.

Try it (free, safe, hands-on)

Read your own network with built-in commands

Use the networking commands already on your computer to reveal your own machine's address, resolve a name to an address, and trace the path traffic takes — turning IP addressing, DNS, and routing from words into observed facts about your own connection.

You will need: Your own computer (Windows, macOS, or Linux) on your own home network; A terminal or Command Prompt — free, already present; A text file to record what each command reveals

  1. Find your own address: run 'ipconfig' on Windows or 'ip addr' (or 'ifconfig') on macOS/Linux. Write down your IPv4 address, subnet mask, and default gateway, and identify which addresses are 'local' to your subnet.
  2. Test reachability: run 'ping 8.8.8.8' and then 'ping example.com'. Note that pinging by name only works if DNS resolves it first — you are watching two layers work together.
  3. Resolve a name yourself: run 'nslookup example.com' (Windows/most systems) and record the address DNS returns, connecting the name-to-address concept to real output.
  4. Trace the path: run 'tracert example.com' on Windows or 'traceroute example.com' on macOS/Linux, and count the hops between your gateway and the destination — that is routing in action.
  5. Write it up: in your notes, explain in your own words what each command revealed about your own connection (your address, your gateway, how a name became an address, and the path out).

What you should see: Your own machine's IP address, subnet mask, and default gateway; a name resolved to an address by DNS; and a numbered list of hops your traffic takes to reach a public destination — every abstract concept made concrete on a network you own.

Safety: Run these commands only against your own machine and public destinations you are allowed to reach, on a network you own. Never scan, probe, or capture traffic on networks or systems you do not control — that can be unauthorized. These read-only commands touch only your own connection.

Where this skill gets used

Certifications that test it: comptia-network-plus, cisco-ccna, comptia-a-plus, comptia-server-plus, comptia-security-plus, comptia-cysa-plus, isc2-sscp-systems-security-certified-practitioner, comptia-pentest-plus, comptia-tech-plus.

Roles that need it: Network administrator, Systems administrator, Cloud engineer, Cybersecurity analyst.

Sources

Every resource is free and dated; official-first, community clearly labeled. A skill primer is a free learning path, not a certification, not professional experience, and not a job or salary promise. Labs use only your own machine and your own network — never systems you do not control. Born draft, pending human review.

All skill primers