Related discussions:
- NAT Mappings vs. Inbound / Outbound Policy for Additional Public IP Address
- Set an Outbound Policy with one of the Additional Public IP Address - #3 by Ron_Case
Currently, although you can set up “Additional IP Addresses” on a WAN, for example:
When setting an outbound policy, although you can select the WAN to use:
…you can not choose a specific IP address for a given WAN, if that wan has one or more “Additional IP Address” set up.
Workaround
Although this can be emulated using NAT Mapping instead, this technique is in some ways more complicated, as it requires one to set up additional firewall rules in order to block incoming connections.
Also, there are some notes that using NAT mapping have additional issues:
- “An outbound policy rule may also be needed” Link
- A user reports that NAT mapping works, but seems to be interfering with InControl2: Link
Feature Request
It would be nice to have the option to choose a specific WAN IP address when setting up an Outbound Policy