Learn · Practise · Troubleshoot

Learn networking by doing, not memorising.

Build a clear foundation, practise on Cisco labs, and use real troubleshooting workflows. Every topic starts in simple English and ends with something useful you can do.

  • No sign-up
  • Beginner-friendly explanations
  • Practical engineer workflows
Learning boardStart here

What do you want to achieve?

Choose the result you need. We will point you to the shortest useful path.

UnderstandPlain-English concepts
See itExamples and commands
Try itGuided protocol labs
Prove itTools and practice tests

Choose by goal

Start with what you need today

Networking is easier when the resource matches the job. Pick a goal instead of searching through a long list.

Adaptive learning path

Tell us where you are starting

Select the option that sounds most like you. The learning board will change its recommended sequence, so you can focus on the next useful step.

Good learning rule: read until the idea is clear, practise until the output makes sense, then explain it without notes.

Beginner path

Build the map before learning the routes

3 focused sessions
  1. 01
    UnderstandIP addresses and subnets

    Learn what the address, mask, network and default gateway each tell you.

    Open subnet calculator →
  2. 02
    ConnectSwitching and local delivery

    See how VLANs, MAC addresses and trunks move frames inside a network.

    Practise switching →
  3. 03
    RouteMove between networks

    Compare static routes and dynamic routing, then inspect a routing table.

    Start the OSPF path →

Practical explanation approach

Troubleshoot from symptom to proof

Do not jump straight to configuration changes. Use the same five questions for almost every network issue.

  1. 01
    Define the symptom

    Write what fails, who is affected, and when it started. “The internet is down” becomes “VLAN 20 users cannot open external websites since 10:15.”

  2. 02
    Check the local facts

    Verify link state, IP address, mask, gateway and VLAN. Bad local information can look like a routing or DNS problem.

  3. 03
    Test one layer at a time

    Try the gateway, a remote IP, then a hostname. Each result removes possibilities and tells you where to look next.

  4. 04
    Compare expected and actual

    Check routes, ARP, MAC tables, DNS answers, policies or certificates. Ask which output is different from the design.

  5. 05
    Change, verify, record

    Make one controlled change. Repeat the same test, confirm the result, and record what solved the problem.

Reachability

“I cannot reach the server”

Check: local IP → gateway → route → remote port.

Why: each test separates a host problem from a path or service problem.

Name resolution

“The IP works, but the name does not”

Check: requested name → returned record → resolver → authoritative answer.

Why: working IP connectivity with a failing name usually points to DNS, not routing.

HTTPS

“The site opens with a certificate warning”

Check: hostname → expiry → issuer → chain → system time.

Why: a valid date alone does not prove the certificate matches or is trusted.

Switching

“Devices in one VLAN cannot connect”

Check: access VLAN → trunk allowance → STP state → MAC learning.

Why: the frame must enter the right VLAN and have a forwarding path across every switch.

Save for later

Field-ready cheat sheets

Short references for revision, lab notes and live troubleshooting. Use them as prompts—not as a replacement for understanding the output.

Cisco IOS

Troubleshooting commands

Show, debug, routing, switching and operational commands with a practical check order.

Download TXT

Routing

Protocol comparison

Compare RIP, EIGRP, OSPF and BGP by metric, scope, use case and verification method.

Download TXT

Command library

Find the right evidence faster

Each reference explains what to inspect—not only which command to type.

IOS

Cisco IOS

Show commands

Interfaces, errors, routes, ARP, MAC table, logs, CPU, memory and neighbours.

Open reference →
RTE

Routing

OSPF and BGP

Neighbour state, LSDB, prefixes, next hop, advertisements and routing policy.

Start with OSPF →
SW

Switching

VLAN, trunk and STP

Access VLANs, native VLAN, MAC learning, root bridge, blocked ports and loops.

Open switching guide →
LIN

Linux and packets

Linux and tcpdump

Addresses, routes, sockets, DNS, neighbours, traffic filters and PCAP files.

Start with Linux →
SEC

Security

Firewall checklist

Policy, NAT, route lookup, sessions, VPN selectors, MTU, logs and packet proof.

Open checklist →
WEB

DNS and TLS

DNS and SSL

Authoritative answers, reverse DNS, expiry, SAN, issuer, chain and SNI checks.

Start with DNS →
CCNA

Study notes

CCNA notes library

Open the on-site CCNA note collection and continue into the topic you need to review.

Browse CCNA notes →

Verify, do not guess

Use a tool to check your understanding

A calculator or checker is most useful when you can predict the answer first. Make a prediction, run the tool, then explain any difference.

Browse all networking tools

Guided practice

Turn protocol theory into visible behaviour

Choose one protocol. Read the overview, build the configuration, verify the result, then intentionally break one thing and troubleshoot it.

Common questions

How to get more from this library

Small changes in how you study can make technical knowledge much easier to recall during an exam or real incident.

Where should a complete beginner start?

Begin with IPv4 addresses and subnet masks, then learn local switching and VLANs, and only then move to routing. Use the “New to networking” path above; it follows that dependency order.

Should I read a guide or start a lab first?

Read enough to predict what should happen, then start the lab. After each command, inspect the output and explain what changed. This is more effective than reading the full topic before touching a device.

How should I use the practice tests?

Take a short test before revision. Group wrong answers by topic, review only those topics, and repeat with a new test. The score matters less than understanding why each wrong option is wrong.

Can I use these resources during real troubleshooting?

Yes. Start with the five-step evidence workflow and use the relevant checklist or tool. Test only systems you own or are authorised to assess, and record the before-and-after result of every change.

One useful habit

Learn one concept. Verify one output. Explain it simply.

That short loop turns a reference page into knowledge you can use under pressure.

Choose your next lesson