Remote access: The port is open for the wrong traffic
The incident
Managed remote clients reach access-service gateways over an enterprise transit chain; unmanaged devices use a separate branch. The partner network branches off near ingress while the service sits three transport hops farther away. The primary service port appears in the access list, but its required transport is blocked. Routing and the secondary service are working. Investigate access gateway transport from R1: 10.180.192.0/24 to 10.180.200.0/24 (TCP/443), and 10.180.193.0/24 to 10.180.201.0/24 (UDP/1194).
Your objective
Restore both authorized service transports and return reachability, including clients and service hosts in both halves of the primary subnet. Keep R6 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R1 and R4. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.
The network
Link addressing (5)
- R1 R2
10.180.208.0/30 - R2 R3
10.180.209.0/30 - R3 R4
10.180.210.0/30 - R4 R5
10.180.211.0/30 - R2 R6
10.180.212.0/30
What you’ll practice
Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.