The scenario
Your-Laptop (192.168.1.10/24) and Web-Server (10.0.0.10/24) are on different subnets joined by Router (192.168.1.1 on the laptop's side, 10.0.0.1 on the server's side). Web-Server runs a web service listening on TCP port 80. A request goes Your-Laptop, Router, Web-Server, and the answer comes back the same way, which only works because each end has a default gateway pointing at the Router.
What you will work out
Learn what a server needs to be reachable: a listening port, a route to it, and a route back.
Why this matters
Every website, API and cloud service depends on the three things in this lab: something listening on the port, a route to the server, and a route back. A cloud virtual machine gets a subnet and a default gateway the same way Web-Server does. When someone says 'the server is down', check them in turn: is something listening on the port, does the request arrive, and can the answer get back?
Running it
Hosting Your First Server opens on a canvas, already wired and addressed. Trace a packet through it hop by hop, or run the same topology live on real Linux network namespaces. How the two modes differ.
Open Hosting Your First Server
Runs in your browser. No install, no signup, and the simulation starts instantly.
Open the lab →