Description

assistance in changing public IP address for a guest WIFI. using NAT

Solution

Example Configuration Changes to create separate Source-Nat Pool on wan interface for guest Tenant

 

Assumptions:

  • guest tenant in place
  • Simple internet 0.0.0.0/0 service in place and source-nat, interface IP working.

 

 

1. Create nat pool on router

 

 

config authority router r1 nat-pool myguestpool name         myguestpool

config authority router r1 nat-pool myguestpool address-pool 192.168.0.3/32 address     192.168.0.3/32

 

 

 

2. Created guest internet service, and removed guest tenant from the previous internet service policy

 

 

config authority service guestInternet name          guestInternet

config authority service guestInternet address       0.0.0.0/0

config authority service guestInternet access-policy guest source guest

 

delete authority service myInternet access-policy corp source guest

 

 

 

3. Created guest service route

 

 

config authority router r1 service-route GuestInternet-Route name         GuestInternet-Route

config authority router r1 service-route GuestInternet-Route service-name guestInternet

 

config authority router r1 service-route GuestInternet-Route next-hop r1-n1 2-wan1 node-name       r1-n1

config authority router r1 service-route GuestInternet-Route next-hop r1-n1 2-wan1 interface       2-wan1

config authority router r1 service-route GuestInternet-Route next-hop r1-n1 2-wan1 source-nat-pool myguestpool

 

 

4. Add Arp response to wan interface for the additional nat IP

 

config authority router r1 node r1-n1 device-interface 2-wan1-di network-interface 2-wan1 address 192.168.0.2 in-subnet-arp-prefix 192.168.0.3/24

 

 

 

Notes:

  • minimal functional lab test results/findings
    • 1 client in each local subnet
    • testing was with ping only

 

 

Another team member provided the following notes about this example config:

 

Note1: I think the nat-pools are designed to work with SVR traffic so I’m not 100% positive it will work if this is local breakout just within a site.

Note2: The nat-pool is a pure NAT not NAPT and there is no overload. So two clients who map to the same IP could cause a collision if they both try to initiate a session using the same source port. Not typically an issue for TCP but could be an issue for certain UDP or applications

Note3: There is additional NAT changes coming in a future release.

Modification History

2023-12-28 : Article Created