What to Learn Next

What you can do now

You started this course with the idea that a network is two devices that can send data to each other. Now you can explain how a laptop gets an address, how a name becomes an IP address, how packets cross routers, why HTTPS protects a login, and how to find the broken step when a connection fails.

That is a solid foundation. Most people use networks every day and never learn any of it.

Pick a direction

There is no single next step. The right one depends on what you enjoy.

Path 1: Network engineering

You want to build and run networks.

• Study for CCNA (Cisco Certified Network Associate) or the vendor-neutral Network+.
• Practise in Cisco Packet Tracer (free) or GNS3.
• Learn routing protocols such as OSPF and BGP, plus VLANs and switching in more depth.

Path 2: Cybersecurity

You want to defend networks or test their defences.

• Learn about firewalls, IDS and IPS, and packet analysis with Wireshark.
• Try beginner labs on TryHackMe or Hack The Box.
• Study for Security+, then move to something more hands-on.

Path 3: Cloud and DevOps

You want to work with automation and modern infrastructure.

• Learn VPCs and security groups on AWS, Azure or Google Cloud.
• Pick up Docker, Kubernetes and Terraform.
• Start with a free-tier account and build a small web server with a database.

Path 4: Linux administration

You want to run servers.

• Get comfortable with the Linux command line. The Linux course on this site is a good next step.
• Learn services such as Apache, Nginx and SSH hardening, and firewalls with ufw or iptables.

Things to do this week

1. Capture some traffic. Open Wireshark, visit a website and find the DNS lookup, the TCP handshake and the HTTP request.
2. Map your home network. Run nmap on your own network and list every device. Do you recognise them all?
3. Break something safely. Change your DNS server to a wrong address, then use the troubleshooting steps to find and fix it.
4. Build a small lab. Install Packet Tracer and connect two PCs through a switch and a router.
5. Explain one topic to someone. Try explaining DNS to a friend. If you can do it simply, you understand it.

Check yourself

Can you do each of these without looking anything up?

• Explain the difference between a switch and a router.
• Tell whether an IP address is public or private.
• Work out how many hosts a /24 or a /26 can hold.
• Describe what ARP, DHCP and DNS each do, and in which order they happen when you join a network.
• Draw the TCP three-way handshake.
• Explain why HTTPS is safer than HTTP, and what a padlock does not prove.
• Write a short firewall rule list with default deny.
• Troubleshoot a broken connection from the bottom up with ip addr, ping, dig and traceroute.

If one of these feels shaky, go back to that lesson and run the commands yourself. Practice teaches more than rereading.

A simple 30-day plan

• Week 1: repeat the commands from this course on your own network, and capture one page load in Wireshark.
• Week 2: build a small lab in Packet Tracer with two subnets, a router and DHCP.
• Week 3: set up a Linux machine or virtual machine, install a web server and protect it with ufw.
• Week 4: pick one path from above and start its first free course or lab.

Thirty minutes a day for a month works better than one long weekend. Short, regular practice is what makes skills stick.

Keep going

Nobody knows everything about networking, and you do not need to. The people who get good are not the ones who memorise the most. They are the ones who investigate when something breaks and keep going until they find the cause.

You now have the basics to do exactly that.