Monday, July 30, 2018

High Availability Firewalls in Azure issue with public IPs

Hey Guys,

So, I have the following scenario and issues:
-External Standard load balancer with multiple public IPs
-Two Firewalls with their own standard public IP (as required to be able to be inserted on the back end pool of the LB)
-Internal standard load balancer (All ports being load balanced to the Firewalls, this is the gateway of all subnets)
-LB are all standard

Issues:
-Cant do NAT one to one because public IPs are on the external Load Balancer. Even if they were on the box there was no way I could assign the same IP to the two Firewall VMs
-Because the Firewalls have their own public IP, and this takes precedence over the LB IP for outbound traffic, VMs go out of a different IP then the traffic that comes in (this will most likely create issues for email server, not sure)
-Incoming connections come from the external IP of the LB but outgoing goes out of the IP on the Firewalls.

Not that knowledgeable on the Azure but is there a way I can make some of this work?

Thanks!



No comments:

Post a Comment