A network engineer configures a stateless router Access Control List (ACL) to allow client workstations on subnet to access an internal web server at . The engineer applies the inbound rule `permit tcp 10.50.1.0 0.0.0.255 host 172.16.10.20 eq 80` on the interface facing the web server. Although initial packets reach the server, workstation browsers consistently time out when attempting to load web pages. Which configuration change will resolve this connection failure?
- Add an outbound ACL rule allowing TCP traffic from host 172.16.10.20 using the established keyword back to the 10.50.1.0/24 subnet.Answer
- BChange the destination port in the inbound ACL rule from port 80 to port 8080 to support web server handshake responses.
- CReplace the extended ACL with a standard ACL applied inbound that filters strictly based on the destination IP address 172.16.10.20.
- DConfigure the inbound rule using UDP instead of TCP to eliminate the requirement for bidirectional packet delivery.
Answer
Add an outbound ACL rule allowing TCP traffic from host 172.16.10.20 using the established keyword back to the 10.50.1.0/24 subnet.
Stateless ACLs evaluate each packet in isolation and do not keep track of active connection states. While the inbound rule permits HTTP client requests to reach the web server, the server's TCP return traffic (SYN-ACK / ACK) is blocked by the router interface's implicit deny rule. Adding an outbound rule matching return traffic from the web server using the `established` keyword permits return packets belonging to established TCP connections.
Step-by-Step Solution
Key Concept
Stateless vs Stateful ACL Filtering and Return Traffic