By default it is possible to create an OpenStack router that has an external IP and can route the traffic of an internal network to the internet. To gain more control over the traffic to the internet, create VPN connectivity and allow for more fine-graned security policy’s, it is possible to create an instance or multiple instances to replace the OpenStack router on an internal network This tutorial guides you through the process of creating instances, and configure OpenStack to allow proper routing and HA IP. The tutorial does not include configuring the firewall.
routed
in this tutorial)
We have multiple firewall / router instances within the OpenStack project. All routers have an internal IP, and an IP address on a public network. Next to that, we have one virtual IP on the internal network and one virtual IP on the public network. The firewalls are configured in an active / standby configuration and through CARP or VRRP decide which instance is the master.
Adjust the DHCP allocation pool to provide at least one IP addres for the Virtual IP of the firewall cluster (in this example 10.10.50.254)
Step 1: Log in to the OpenStack dashboard and proceed to the Network
tab.
Step 2: Select Networks
and then select your internal network
Step 3: Select Subnets
and click Edit Subnet
on the subnet where your Virtual IP should live
Step 4: Go to Subnet Details
and modify the Allocation Pools
to remove 10.10.50.254 from the allocation pool
Step 5: Click Save
Repeat the same process for the rented IP range
For this tutorial assumes two instances are created, both in a different availability zone. you can use the following tutorial combined with the specs below:
On the Details tab:
On the Source tab:
On the Flavor tab:
On the Networks tab:
On the Security Groups tab:
Step 1 Go to compute > Instances > FW01 > Interfaces tab
Step 2 Click on Edit port
for the WAN interface
Step 3 Deselect Port Security
and click update
Step 4 Do the same for the LAN interface
Step 5 Do the same for FW02
Install the firewall instances to your liking, but at least configure the following parameters
routed
Edit subnet
for the subnetSubnet Details
0.0.0.0/0,10.10.50.254
and click Save
Create a client instance and validate if internet connectivity is flowing through the firewall cluster.