Wireless Access

Occasional Contributor II

Destination not working as expected

Hi Everyone,


We have a wireless users in VLAN 200 in /24 network. I have configured the ACL (any any any dst-nat ip but redirecting is not working. I am not able to ping the from the subnet. but if i remove the ACL then i am able to ping it.


I dont have gateway for the user for the VLAN 200. It is in the switch not on the controller and it is tagged to the switch.


Do we have to IP interface configured for the VALN 200 on the controller for dst-nat to work properly?


I do not see any routing issue as removing the dst-nat acl and making allowall is working fine which the users in VLAN 200 is able to ping the


Awaiting your valuable advice on it.


Thanks in advance.

Guru Elite

Re: Destination not working as expected

Yes, you need an L3 interface on the controller for the source network.

Sent from Windows Mail

| Tim Cappalli | Aruba Security | @timcappalli | timcappalli.me |

NOTE: Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba or Hewlett Packard Enterprise.

Re: Destination not working as expected

what is the goal of your dst-nat rule?  To dst-nat all traffic or only certain protocols?

Systems Engineer, Northeast USA

Search Airheads
Showing results for 
Search instead for 
Did you mean: