A network engineer is configuring an extended Access Control List (ACL) on a stateless router interface. Client workstations on the internal subnet () can successfully transmit outgoing HTTPS requests ( port ) to external web servers, but return web traffic is blocked by the inbound ACL. Which of the following configuration adjustments will allow internal clients to receive return HTTPS traffic from external servers while maintaining stateless security controls? (Select TWO.)
- Add an inbound ACL rule permitting TCP traffic originating from source port 443 directed to the internal subnet on destination ephemeral ports (-).Cevap
- Include the established keyword on the inbound TCP permit rule for port 443 to match packets with the ACK or RST flags set.Cevap
- CModify the inbound ACL rule to permit incoming UDP traffic on port 443 instead of TCP traffic to bypass connection tracking.
- DReplace the router's Layer 3/4 ACL with a Layer 2 MAC filtering rule on the inbound interface to inspect return packets.
Cevap
To allow return HTTPS traffic through a stateless router ACL, the configuration must explicitly permit inbound TCP traffic originating from source port 443 destined for internal ephemeral client ports (-), and utilize the established keyword to restrict permitted packets to established TCP sessions (packets with ACK/RST flags set).
Because stateless firewalls and ACLs do not automatically dynamically track TCP connection states, return traffic from external servers is dropped by default. To permit return HTTPS packets, an explicit inbound ACL rule must be created that matches TCP source port 443 heading to client ephemeral destination ports. Adding the established keyword guarantees that only return packets belonging to established sessions (ACK/RST flags set) are allowed, preventing unsolicited inbound SYN packets.
Adım Adım Çözüm
Anahtar Kavram
Stateless ACL Return Traffic Handling and Established TCP Filtering
Tahmini Süre:1m 30s