A few important notes before we launch the instance:
1 This document complements the existing deployment guide that was designed to help you to associate a Palo Alto VM-Series. We are going to assume that you have completed all the steps from 1 to 6 before launching this firewall instance. Step 7a is not necessary as it is Palo Alto VM-Series specific.
2 Currently we do not have a full integration between the Aviatrix dashboard and the Netgate pfSense, which means that you will not be able to dynamically update the firewall routing table, as it is currently possible with the Palo Alto VM-Series.
Setup Firewall Network(Firenet) for Netgate PFSense¶
Complete steps 1-6 of the Firewall Network Workflow in Aviatrix controller to prepare your Firewall VPC (FireNet VPC). This will also set up the subnets that you will need for launching your PFsense instance.
Deploy PFsense instance From AWS marketplace¶
1 Go to aws.amazon.com/marketplace and search for the pfSense AMI in AWS Marketplace and “Continue to Subscribe”
2 On the next screen, accept the terms and you should be able to continue
3 On the next page, choose “Amazon Machine Image” as fulfillment option, choose the proper region and click on “Launch”
4 On the next page, “Choose Action” should be set to “Launch through EC2” and then click on “Launch”. You might want to use the pfSense docs page as reference as well
5 Now, choose your instance size. For this deployment we are going to need 2 network interfaces: management/egress and LAN. A 3-interface deployment is possible (separating management from egress) but not required, as it will also require a larger instance (due to the extra ENI)
6 You can start with a t2.small for example. Although, for better network performance you might want to select a different instance type (m5, c5 or c5n) and a larger instance size. For more information on this subject we suggest starting at this AWS `document <https://aws.amazon.com/ec2/instance-types/ >`_ and the pfSense docs page as well
7 On the instance details page, the most relevant setting for any deployment is the subnet selection for the ENIs eth0 and eth1. If you have followed all the steps on the Firewall page, then your subnet selection should follow this logic:
- Eth0 for both management and egress and it should be placed in the subnet FireNet-vpc-Public-FW-ingress-egress;
- Eth1 as the LAN interface should be placed in the subnet aviatrix-FW-GW-dmz-firewall (same AZ as eth0);
10 Then click on “Next: Add Tags” – if you use tags in your environment, this is the time
11 Then click on “Next: Configure Security Group” – by default you are going to see pfSense default rules for HTTP, HTTPS, SSH and OpenVPN. You can then click on “Review and Launch” or you should isolate the instance public interfaces with the following three rules
- All inbound traffic allowed for your own public IP (you will have to SSH to the instance)
- All inbound traffic allowed for the controller IP (even though only TCP port 443 and ICMP will be used)
- All inbound traffic allowed for RFC 1918 addresses (this should cover your spoke CIDRs and allow you to perform IDS/IPS)
12 Please note that as soon as you attach an EIP to any instance, it will start receiving random hits from the Internet and you should guarantee that unwanted traffic is simply being dropped, so you don’t pay for “rejects/resets” being sent from of your firewall/VPC.
13 The next page will be a summary containing all of your previous choices, as well as any relevant AWS warning on how you can improve your deployment (e.g: open security groups, AMI usage tier consideration, etc).
14 Once you click on “Launch” you will be prompted to choose the .pem key – please download the key now if you have not done it already and archive it in a secure location, as you are going to use it to SSH into the instance to enable GUI/web interface access
15 If you would like to, you can monitor the instance until it is up via the AWS console (see screen shot below). Once the instance passes all the health checks, please open a terminal and SSH into the instance using the proper keys and the user “admin”, so can grep the auto-generated password
17 Please open a browser and go to https://the_instance_EIP. You will have to accept the self-assigned certificate and then will be prompted with a screen like the one below. Just enter the username as admin and the password you have just saved on the previous step
18 The Setup Wizard will take you through some basic steps, which will allow you to configure:
- On step 2: Hostname and domain for the instance, primary and secondary DNS servers and whether DHCP should be able to override it – if you want to use AWS VPC DNS leave the box checked
- On step 3: The timezone and NTP server – please remember that the AWS NTP server can be reached at 169.254.169.123
- On step 6: You can change your password
- And step 7 reloads the configuration.
19 Once you are done with the Setup Wizard, you should double-check your interfaces assignments (xn0/WAN and xn1/LAN) and set xn1 to DHCP. Also, don’t forget to disable “Source/dest Check” for the eth1 interface in the AWS Console as explained here
20 The next step is to update the route table. For the purpose of this guide, we suggest adding three routes, each for a RFC1918 address pointing to the private IP of the eth2/ENI of the Aviatrix gateway in question (whether you are attaching the instance to the main or to the backup gateway).
21 Please make sure that the gateway of the xn0/WAN interface has been selected as default, so your egress traffic can be routed to the VPC IGW; 22 The next step is to configure the Aviatrix gateway that the instance will be attached to (either the main or the backup) as an object. Please go to System > Routing > Gateway and click on + Add. The IP address of the eth2 interface of the Aviatrix gateway selected can be found in the AWS console: EC2 > Network Interfaces 23 One you have configured the Aviatrix gateway, you can use it as next hop. Just go to System > Routing > Static Routes and click on “+ Add”. Repeat this step for all three RF1918 subnets: 24 Great. Let’s configure the NAT policy. By default, pfSense will perform automatic outbound NAT for both interfaces, which we cannot have for the xn1/LAN interface. So please go to Firewall > NAT > Outbound and create an exception mapping like the one below – to not NAT anything exiting via xn1: 25 Now the next step is to change the default selection of NAT to be the second option: “Hybrid Outbound NAT rule generation (Automatic Outbound NAT + rules below)” – then click on “Save” and then “Apply Changes”;
26 Now we need to double-check the firewall rules are according to your project. If you have already enforced the WAN inbound control at the Security Group level while launching the instance, all you need to confirm is that you are not being more restrictive at the firewall level, so please make sure you are allowing everything at the LAN level 27 The final step is to monitor your traffic to confirm that the inspection is being performed as configured. Please go to Status > System Logs > Firewall > Dynamic View. Use the funnel icon to filter your logs accordingly. In this example we have ICMP traffic being inspected in an East-West flow (192.168.240.22 > 10.10.10.10), as well as egress pings to disney.com from the same host. 28 Great. You are now good to repeat this process to add more instances to talk to the main gateway and also to the backup gateway. The difference regarding the backup gateway attachment is that the subnets will be in a different AZ;
29 For more information on the Firewall network solution, please refer to this link