This article contains:1. Explanation for the need of destination NAT rule in IAP2. Configuring destination NAT rule
Instant 3.2 supports Destination NAT rule in ACL. Destination NAT rule is used to direct the traffic to a specific destination irrespective of the original destination that the traffic was intended for.One common usage scenario of this feature is sending all DNS requests to a third-party DNS server.For example, OpenDNS servers provide misspelling correction, phishing protection, and optional content filtering Service. If we add a rule: rule any any match udp 53 53 dst-nat ip 18.104.22.168 53 IAP will rewrite the destination IP of all DNS queries to 22.214.171.124 regardless of the DNS server configured on the client. This allows a customer to control client behavior.
Environment : This article applies to all the IAPs running 126.96.36.199_3.2.0.
Create a Wireless network and go to “Access rules” as shown in the image below. Click Ok.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.