SubnetLayer: Learn Protocols Visually

Understand networks, packet by packet

Artificial Intelligence

Tech

Online Learning

Visit WebsiteSee on Product Hunt

I built SubnetLayer because networking protocols are often taught in one of two ways: through dense theory that is difficult to visualise, or through packet captures that already require a strong understanding of the protocol. That creates a major learning gap. A learner may memorise that TCP uses SYN, SYN-ACK, and ACK, but still struggle to understand why the exchange is needed, how sequence and acknowledgement numbers change, what each field represents, and what the packets look like when something goes wrong. SubnetLayer was created to bridge that gap. The idea is simple: first explain the concept in clear language, then show exactly how it appears at the packet level. Learners can move through protocol conversations step by step, inspect headers and fields, follow state changes, explore failure scenarios, and connect theory with practical troubleshooting. The product initially started as an interactive way to teach TCP. As the project evolved, I realised that protocols make the most sense when they are learned together as part of a complete communication flow. That led to expanding the platform across IP, ARP, ICMP, UDP, DNS, DHCP, HTTP, TLS, HTTPS, OSPF, BGP, and other networking concepts. The development process also changed the learning approach. The early version was heavily focused on demonstrations and packet labs. After reviewing it from a beginner’s perspective, I added more conceptual explanations, mental models, terminology, misconceptions, quizzes, and troubleshooting context. The goal became a balanced learning experience: understand the concept first, then prove that understanding by analysing the packets. SubnetLayer is designed for students, certification learners, developers, support engineers, network professionals, and anyone who wants to understand what is actually happening behind a network connection. I would love your feedback: Which networking protocol or troubleshooting scenario should we add next?