I've built out in the SD-WAN connection group. XGS116 firewall at my remote home office is behind DHCP public IP. Virtual firewall in Azure is behind Azure's NAT. It doesn't seem like an SD-WAN Connection group can handle this as it configures the Gateway address in my home firewall to the firewalls private PortB address, not the public that I have assigned.
I configured the S2S in the remote home office firewall to change the gateway to the public IP assigned to the NIC. Now the tunnel is up and I can access resources in Azure.
Questions
1. Is it correct to say that this will never work automatically in an SD-WAN Connection Group?
2. If I set the address to the public IP in the S2S built by the Central Orchestration, will it be wiped out if the firewall receives some other job?
3. What happens if the home firewall gets a new IP from it's DHCP lease? Will this force an Orchestration update?
This thread was automatically locked due to age.