The site on the lab-server server listens on 192.0.2.10:8080, as the output of ss shows. The lab-client client cannot connect: its request hangs. Take a look yourself.
Start on the card builds the client and the server, and commands containing lab-client run on the client.
A socket, but no answer
Check the listening socket on port 8080 on the server, then request the site from the client and send the server two echo requests.
First, predict
The socket on 192.0.2.10:8080 is there. What will curl print on the client?
Now start the exercise, run the command and compare your prediction with the output.
Why did the client wait until the timeout, although the site listens on 192.0.2.10:8080?
-
Without a way
pingwould printNetwork is unreachable. It sent both requests:2 packets transmitted. -
ssshowed192.0.2.10:8080, exactly where the client went. On another address there would be an immediate refusal, with no wait. -
It is not only the site that is silent:
pinggot no reply either, and the server's kernel answers ping without any site.
The client's packets reach the server and are silently dropped there: neither the site nor the kernel answers.