To make traffic between subnets visible in the firewall, you must add one network interface per subnet. The number of network interfaces you can add to your instance is limited by the instance type. Firewall instances with multiple network interfaces cannot be deployed in a high availability configuration.

AWS Reference Architectures

This article is used in the following AWS reference architectures:

• AWS Reference Architecture - Segmentation Firewall for Single AZ VPCs.

Before You Begin

• Deploy a firewall instance in the public subnet of the VPC. For more information, see How to Deploy a CloudGen Firewall in AWS via AWS Console.

• Verify that the Elastic IP address is associated with the elastic network interface (ENI) of the firewall instance and not with the instance itself.

• Stop the firewall instance. Additional network interfaces cannot be attached to a running system.

Step 1. Add an Elastic Network Interface

Create an elastic network interface. This interface will then be attached to the instance later.

1. Log into the AWS console.

2. Click Services and select EC2.

3. In the Network & Services section of the left menu, click Network Interfaces.

4. Click Create network interface. 

   Open

   

5. The Create network interface window opens. Configure the network interface:

   • Description – Enter a description for the network interface. 

   • Subnet – Select the private subnet in the VPC for the network interface. The subnet must be in the same Availability Zone as the firewall instance.

   • Private IP – Select Custom and enter a free IP address in the subnet. The first three IP addresses in the subnet are reserved by AWS.

     Open

     

   • Security groups – Select the security group assigned to the firewall instance.

     Open

     

6. Click Create network interface.

The elastic network interface is now listed with the Status column showing Available.

Open

Step 2. Disable Source/Destination Check

To be able to perform NAT operations, the source/destination check must be disabled.

1. Log into the AWS console.

2. Click Services and select EC2.

3. In the Network & Services section of the left menu, click Network Interfaces.

4. Right-click on the network interface created in Step 1 and click Change source/dest. check.

   Open

   

5. The Change source/dest. check window opens. Clear the Enable check box to disable the interface.

   Open

   

6. Click Save.

The network interface is now able to handle traffic with destination IP addresses that do not match its own private IP address.

Step 4. Attach the Network Instance to the Firewall Instance

Verify that the firewall instance is shut down, and then add the network interface to the instance.

1. Log into the AWS console.

2. Click Services and select EC2.

3. In the Network & Services section of the left menu, click Network Interfaces.

4. Right-click on the network interface created in Step 1 and click Attach. 
   

5. The Attach Network Interface window opens. In the Instance ID list, select the firewall instance.

   Open

   

6. Click Attach.

Step 5. Start the Firewall Instance

1. Log into the AWS console.

2. Click Services and select EC2.

3. In the Instances section of the left menu, click Instances.

4. Select the firewall instance, expand Instance State, and click Start instance. 

   Open

   

   
   Wait for the firewall instance to start.

5. Log into the Barracuda CloudGen Firewall using Firewall Admin.

6. Go to CONTROL > Network.

7. Verify that the network interface you attached in Step 4 is listed.

   Open

   

Step 6. Add the Network Interface in the Firewall Configuration

The network interface must be added and configured in the firewall configuration.

Step 6.1. Add the Network Interface

1. Log into the Barracuda CloudGen Firewall using Firewall Admin.

2. Go to CONFIGURATION > Configuration Tree > Box > Network.

3. Click Lock.

4. In the left menu, click Interfaces.

5. In the Network Interface Cards table, double-click the 10dynmod entry. 

   Open

   

6. The Network Interface Cards: 10dynmod window opens. From the Number of Interfaces, select the number of network interfaces attached to the firewall instance.

   Open

   

7. Click OK.

8. Click Send Changes and Activate. 

Step 6.2. Add a Shared IP for the Network Interface

1. Go to CONFIGURATION > Configuration Tree > Box > Network.

2. Click Lock.

3. In the left menu, click IP Configuration.

4. In the Shared Networks and IPs section, click +.

5. Enter a name for the shared IP address, and click OK....

6. The Shared Networks and IPs window opens.

   • Interface – Select the interface used to connect to the network. E.g, eth1.
     

   • Network Address – Enter the network of the subnet in CIDR format.

   • Shared IPs in the Network – The Shared IPs in this Network window opens.

     • IP Address – Enter the private IP address configured for the network interface in Step 1. 

     • Alias for this IP – Select None.

     • Responds to Ping – Select yes .

     • Click OK to save this settings.

   • Trust Level – Select Trusted.

     Open

     

7. Click OK.

8. Click Send Changes and Activate.
   

Step 6.3 Activate the Network Configuration

1. Go to CONTROL > Box.

2. In the Network section of the left menu, click Activate new network configuration.

3. The Network Activation window opens. Click Failsafe.

The route is now active and the shared IP is reachable for all clients in the subnet.

Open

Next Steps

• Configure the AWS route table to use the network interface as the default route for all clients in this subnet.

• To send traffic between two subnets over the firewall, the firewall must have a network interface in each subnet. A gateway route must be added on the clients with the private IP address of the firewall used as the gateway. For more information, see AWS Reference Architecture - Segmentation Firewall for Single AZ VPCs.