Datacenter re-location & NAT and new IP's
-
We are migrating our existing infrastructure over to a new datacenter and we are in the process of re-mapping port-forwarding and outbound NAT to the new WAN2 subnet. There is an existing cross-connect between DC1 and DC2.
The existing setup is:
1 x virtual pfsense 2.2.1
8 x LAN interfaces
WAN1 (WAN) subnet is from DC1 upstream
WAN2 (NVDWANIP) subnet is from DC2 upstreamBoth Public IP's were added as virtual IP aliases.
Is the below procedure the correct one to completely switch to WAN2 "NVDWANIP" ? Ideally I would like to avoid any dependencies on existing 'WAN1' after the physical move.
1. Add each new WAN IP /27 subnet to Virtual IP as Alias. (See screenshot)
2. Re-add Port Forwarding for each rule to WAN2. (See screenshot)
3. Change outbound NAT as: (See screenshot)
4. Change LAN interface gateway to "NVDWANIP"Outbound NAT:
- Interface: NVDWANIP
- Protocol: Any
- Source: Network, 192.168.22.0/24
- Destination: Any
- Translation Address: 43.xxx.xx.xx (from the VIP list)
The issue we have with the above rule is that there is no connectivity to other LAN subnets.
We also tried setting some NAT rules as per below - however what will happen when 'WAN' interface becomes unavailable after the physical DC move?
Outbound NAT:
- Interface: WAN
- Protocol: Any
- Source: Network, 192.168.22.44/32
- Destination: Any
- Translation Address: 43.xxx.xx.xx /32
The default gateway is still set to 'WAN1' under routing - we cannot change this to WAN2 GW until equipment is at DC2.
Any help would be much appreciated.







