Persistent networking with Netplan

The reports service on node2 answers itself, but a request from node1 waits and gives up. Find where the path gets lost and fix it so that the fix survives a reboot.

Situation

The lab has two machines: node1 is your terminal and node2 is a server. A reports service runs on node2: it listens on address 10.99.0.1, port 8080. That address belongs to the internal network 10.99.0.0/24, which exists only on node2. On node2 itself curl http://10.99.0.1:8080/ answers with a report line, while the same request from node1 gives up after three seconds.

node1's default route leads to a gateway to outside networks. That gateway is missing in the lab, like the internet, but node1 needs it outside the lab, so leave it alone.

Run commands on node2 from node1 over SSH: ssh node2 'command'.

Task

1. curl http://10.99.0.1:8080/ on node1 gets the answer of the reports service on node2.
2. The fix survives a reboot of node1: it is saved in the Netplan configuration.
3. node1's default route stays as it was, both live and in the Netplan configuration.

The lab has no internet access, only the network between node1 and node2. Everything you need is installed on both machines.