Wireless Access

Reply
Occasional Contributor II
Posts: 88
Registered: ‎12-27-2012

Destination not working as expected

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.

Guru Elite
Posts: 8,320
Registered: ‎09-08-2010

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 TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
Aruba
Posts: 1,642
Registered: ‎04-13-2009

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
ACCX | ACDX | ACMX

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