A laptop is plugged into the home network and cannot load a page. Walk up the layers from the cable to the web page, find the three faults, and fix each one where it lives.
Give the laptop an address from the router's DHCP service.
Make the laptop reach the outside server at 203.0.113.80.
Make the name web.test resolve, and the page at http://web.test:8080/ load.
Fix it with commands only. Reset puts the faults back.
Checks
1 of 6 pass
✓Link: the laptop's cable is plugged in and uplaptop has a link on eth0: yes
✗Address: the laptop has one from the router's DHCP servicelaptop has an address on eth0: not yet
✗Gateway: the laptop reaches its router, 192.168.1.1laptop pings 192.168.1.1: not reached
✗Route out: the laptop reaches 203.0.113.80laptop pings 203.0.113.80: not reached
✗Name: web.test resolveslaptop looks up web.test: not yet
✗Page: http://web.test:8080/ loadslaptop connects to web.test:8080: not reached
Stuck, or done and want to compare? Try it yourself first.
Type a command, for example ip addr, then press Enter. Type help for the list.
IPv4 only, one packet at a time, Linux behaviour (iproute2, dig and udhcpc output from Ubuntu 24.04). One DHCP server and one DNS server on the router. Times are made up but stable.