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.
Learn · Practise · Troubleshoot
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.
Choose the result you need. We will point you to the shortest useful path.
Choose by goal
Networking is easier when the resource matches the job. Pick a goal instead of searching through a long list.
I am learning
Start with addresses, switching, routing and verification in a sensible order.
Choose a learning pathI am revising
Use short tests to discover weak topics, then return to the matching guide or lab.
Browse practice testsI am troubleshooting
Follow a safe check order for connectivity, routing, DNS, HTTPS and switching issues.
Open practical playbooksI need a reference
Download subnetting, Cisco IOS and routing references for fast field use.
Get cheat sheetsAdaptive learning path
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.
Learn what the address, mask, network and default gateway each tell you.
Open subnet calculator →See how VLANs, MAC addresses and trunks move frames inside a network.
Practise switching →Compare static routes and dynamic routing, then inspect a routing table.
Start the OSPF path →Practical explanation approach
Do not jump straight to configuration changes. Use the same five questions for almost every network issue.
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.”
Verify link state, IP address, mask, gateway and VLAN. Bad local information can look like a routing or DNS problem.
Try the gateway, a remote IP, then a hostname. Each result removes possibilities and tells you where to look next.
Check routes, ARP, MAC tables, DNS answers, policies or certificates. Ask which output is different from the design.
Make one controlled change. Repeat the same test, confirm the result, and record what solved the problem.
Reachability
Check: local IP → gateway → route → remote port.
Why: each test separates a host problem from a path or service problem.
Name resolution
Check: requested name → returned record → resolver → authoritative answer.
Why: working IP connectivity with a failing name usually points to DNS, not routing.
HTTPS
Check: hostname → expiry → issuer → chain → system time.
Why: a valid date alone does not prove the certificate matches or is trusted.
Switching
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
Short references for revision, lab notes and live troubleshooting. Use them as prompts—not as a replacement for understanding the output.
Featured visual guide
Use the CIDR table to recall mask and host values, then follow the block-size method to find the network, broadcast and usable range.
Cisco IOS
Show, debug, routing, switching and operational commands with a practical check order.
Download TXTRouting
Compare RIP, EIGRP, OSPF and BGP by metric, scope, use case and verification method.
Download TXTCommand library
Each reference explains what to inspect—not only which command to type.
Cisco IOS
Interfaces, errors, routes, ARP, MAC table, logs, CPU, memory and neighbours.
Open reference →Routing
Neighbour state, LSDB, prefixes, next hop, advertisements and routing policy.
Start with OSPF →Switching
Access VLANs, native VLAN, MAC learning, root bridge, blocked ports and loops.
Open switching guide →Linux and packets
Addresses, routes, sockets, DNS, neighbours, traffic filters and PCAP files.
Start with Linux →Security
Policy, NAT, route lookup, sessions, VPN selectors, MTU, logs and packet proof.
Open checklist →DNS and TLS
Authoritative answers, reverse DNS, expiry, SAN, issuer, chain and SNI checks.
Start with DNS →Study notes
Open the on-site CCNA note collection and continue into the topic you need to review.
Browse CCNA notes →Verify, do not guess
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 toolsGuided practice
Choose one protocol. Read the overview, build the configuration, verify the result, then intentionally break one thing and troubleshoot it.
Best first dynamic protocol
Neighbours, areas, LSAs, cost, DR/BDR, filtering and repair.
Start OSPF → 02Cisco routing
DUAL, successors, metrics, K-values, packets and repair.
Start EIGRP → 03Inter-domain routing
Peering, path attributes, routing policy and troubleshooting.
Start BGP → 04Simple distance vector
Operation, versions, timers, authentication and repair.
Start RIP →Common questions
Small changes in how you study can make technical knowledge much easier to recall during an exam or real incident.
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.
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.
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.
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
That short loop turns a reference page into knowledge you can use under pressure.