Wireless Access

last person joined: 18 hours ago 

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

Source NAT

This thread has been viewed 6 times
  • 1.  Source NAT

    Posted May 06, 2014 03:58 PM

    How to source NAT to different vlan than the one used for WLC , without need for creating policy and rule,

     

    i mean when we enable the source nat in the IP interface configuration, this vlan will be source natted to the WLC ip address,

    but what i need is to be natted to another vlan interface.

     

    sample configuration

     

    VLAN10 : WLC IP address: 10.1.10.2

    VLAN20: 10.1.20.2

    VLAN30: 192.168.30.1

     

    i need all the IPs from VLAN30 to be source natted to IP 10.1.20.2

     

     



  • 2.  RE: Source NAT

    EMPLOYEE
    Posted May 06, 2014 06:35 PM

    The ip nat inside or source nat for each VLAN will be routed out of the next-hop or default gateway interface.  If the controller thinks that the default gateway is on the 10.1.20.x subnet, then traffic will be source-natted out of 10.1.20.2.  You just need to have static routes to any other subnet the controller would need to get to.  

     

    In short, the source nat gets natted out of the interface of the default gateway in general.  Make the router upstream from 10.1.20.2 the default gateway, then put in static routes for other destinations and the ip nat inside will work the way you want it to without creating a policy and rule.

     



  • 3.  RE: Source NAT

    Posted May 08, 2014 01:56 AM

    anks dear,

    but you didn't get the idea, i only need to do this for the 192.168.x.x subnet "to be nated to 10.0.20.x subnet"



  • 4.  RE: Source NAT

    Posted Aug 28, 2015 02:25 PM

    Hi Omran, I wanted to see if you figured out how to complete this source NAT example?  I am trying to do the same type of configuration.