Logging in to Firewall and Configuring Interfaces

  1. Barracuda recommends configuring its instances with the Firewall Admin, a stand-alone Windows application. Directions on downloading and using it can be found here.

  2. Open the Admin Client and use the Elastic IP, root as the Username, and the instance id from the AWS console as the initial password.

image6

  1. You will be prompted to change the password when you first log in. After changing the password and logging in again, you must choose how you will administer the Firewall. Choose Manage via Firewall Admin and confirm.

image7

  1. These steps follow the Barracuda Documentation for adding an additional interface. Once logged in you will need to configure the second(eth1) interface on Barracuda. Go to Configuration > Configuration Tree > Box > Network.

image8

  1. Click Lock.

  2. In the left menu, click Interfaces.

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

image9

  1. In the resulting Network Interface Configuration dialog,select the number of network interfaces attached to the firewall instance (in this case, 2). Click OK.

image10

  1. Click Send Changes and Activate.

Adding a Direct Attached Route for the Second Network Interfce

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

  2. Click Lock.

  3. In the left menu, click Routing.

  4. Click +in the IPv4 Routing Table to add an attached route.

  5. Target Network address will be the subnet you put on eth1, the aviatrix-fireGW-DMZ-firewall subnet.

    • For the Route Type, select direct attached network.

    • For the Interface Name, select eth1.

    • For the Trust Level, select Trusted.

image11

  1. Click OK.

  2. Click Send Changes and Activate.

Activating the Network Configuration

  1. Go to Control > Box.

  2. In the Network section of the left menu, click Activate new network configuration. The Network Activation window opens.

  3. Click Failsafe.

The route is now pending in Control > Network.

image12

Adding a Virtual IP to the Virtual Server

A virtual IP needs to be added to the Virtual Server. It will be the private IP assigned to your eth1 interface from the AWS console.

  1. Go to Configuration > Configuration Tree > Box > Virtual Servers > your virtual server > Server Properties.

  2. Click Lock.

  3. Click + in the Additional IP table. The Additional IP window opens.

    • In Additional IP, add the private IP address configured for the network interface in step 1.

    • Reply to Ping and select Yes.

image13

  1. Click OK.

  2. Click Send Changes and Activate.