Wireless Access

last person joined: 11 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Destination not working as expected

This thread has been viewed 0 times

  • 1.  Destination not working as expected

    Posted Mar 05, 2014 07:11 PM

    Hi Everyone,

     

    We have a wireless users in VLAN 200 in 192.168.80.0 /24 network. I have configured the ACL (any any any dst-nat ip 10.10.10.160) but redirecting is not working. I am not able to ping the 10.10.10.160 from the 192.168.80.0 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 10.10.10.160.

     

    Awaiting your valuable advice on it.

     

    Thanks in advance.



  • 2.  RE: Destination not working as expected

    EMPLOYEE
    Posted Mar 05, 2014 07:14 PM
    Yes, you need an L3 interface on the controller for the source network.






    Sent from Windows Mail


  • 3.  RE: Destination not working as expected

    Posted Mar 05, 2014 08:44 PM

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