Publish a DMZ web server with a virtual IP
Map a public address to a server in the DMZ with a VIP, allow only web traffic in, let the server fetch updates, and keep it from opening anything towards the LAN.
Scenario
The company web server WEB (10.0.3.10) sits in the DMZ on port3 (10.0.3.1/24). The ISP has routed the spare address 203.0.113.10 to you for it. Internet users must reach WEB on 203.0.113.10 with HTTP and HTTPS, and nothing else. WEB downloads updates from the Internet over HTTP and HTTPS (it needs DNS too), but if it is ever compromised it must not be able to reach the LAN. Staff on the LAN use the site directly at 10.0.3.10 over HTTPS.
Your tasks
- From the Internet, INET opens 203.0.113.10 on TCP 80 and 443, but not on TCP 22.
- WEB can reach 8.8.8.8 on TCP 80 and UDP 53, but cannot reach PC1 in the LAN.
- PC1 opens https://10.0.3.10 (TCP 443) directly.
The lab checks the result, not the exact commands. For example, a ping task passes only when the ping really succeeds through the network you built.