Barracuda NG Firewall

Barracuda NG Firewall



5.4 5.2

 


How to Deploy the Barracuda NG Firewall in an Amazon Virtual Private Cloud

Last update: Wednesday, 29. Jan 2014

The Barracuda NG Firewall can run as a virtual appliance in the Amazon cloud as a gateway device for Amazon EC2 instances in an Amazon Virtual Private Cloud (VPC).

Follow the steps in this article to deploy the Barracuda NG Firewall in an Amazon VPC.

Amazon AWS charges apply. For more information, see Amazon's monthly pricing calculator at http://calculator.s3.amazonaws.com/calc5.html.

AmazonCloudNG.png

In this article:

Before You Begin

Before you deploy the Barracuda NG Firewall in the Amazon VPC:

  • Get an Amazon Web Service (AWS) account.
  • Get a Barracuda NG Firewall AWS license. The Barracuda NG Firewall AMI itself is free.
  • Choose the country and availability zone in which you want to create the Amazon VPC. All instances and services must be in the same availability zone.  

Step 1. Set Up the Amazon VPC Cloud

The Amazon VPC is a smaller, isolated version of the public Amazon Elastic Compute Cloud (EC2). The VPC is restricted to its own /16 network subnet. Create a VPC in the 192.168.0.0/16 subnet.

  1. Go to the Amazon Web Services Console (https://console.aws.amazon.com).
  2. In the Compute & Networking section, click VPC - Isolated Cloud Resources.
  3. In the left pane of the VPC console, click Your VPCs.
  4. Create a VPC with the following settings:
    • CIDR Block – Enter 192.168.0.0/16.
    • Tenancy – Select Default.
      AwsCreateVPC.png
  5. Click Yes, Create.

Your VPC is now listed on the Your VPCs page.

AwsListVPCs.png  

Step 2. Create an Internet Gateway

Create an Internet gateway to enable devices in the Amazon VPC to access the Internet.

  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, click Internet Gateways
  3. Click Create Internet Gateway. 
  4. In the Create Internet Gateway window, click Yes, Create.
    AwsCreateInternetGateway.png
  5. Select the new Internet gateway, and then click Attach to VPC
    AwsInternetGateway.png
  6. Select the VPC that you created in Step 1 (e.g., vpc-b0a9a0db (192.168.0.0/16)), and then click Yes, Attach.
    AwsAssociateInternetGateway.png

The Internet gateway is now associated with the Amazon VPC.
AwsInternetGatewayFinished.png  

Step 3. Create Subnets

Create two /24 subnets inside the Amazon VPC:

  • A private network for the eth0 interface on the Barracuda NG Firewall and the EC2 instances in the VPC.
  • A public network that connects the eth1 interface of the Barracuda NG Firewall to the Internet gateway. 
Step 3.1. Create the Private Subnet
  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, click Subnets.
  3. Click Create Subnet.
  4. In the Create Subnet window, configure the following settings:
    • VPC – Select the VPC with the 192.168.0.0./16 subnet (e.g., vpc-abcd1234568 (192.168.0.0/16)).
    • Availability Zone – Select the availability zone that your VPC is in (e.g., eu-west-1a).
    • CIDR Block – Enter 192.168.200.0/24.
  5. Click Yes, Create. 
Step 3.2. Create the Public Subnet
  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. Click Subnets.
  3. Click Create Subnet.
  4. In the Create Subnet window, configure the following settings:
    • VPC – Select the VPC with the 192.168.0.0./16 subnet (e.g., vpc-abcd1234568 (192.168.0.0/16)).
    • Availability Zone – Select the availability zone that your VPC is in (e.g., eu-west-1a).
    • CIDR Block – Enter any 192.168.XX.0/24 subnet, except for 192.168.200.0/24 (e.g., you can enter 192.168.10.0/24).
  5. Click Yes, Create.

The private (192.168.200.0/24) and public (192.168.10.0/24) subnets are now in your VPN.
AwsSubnetsList.png  

Step 4. Set Up Amazon Security Groups and Network ACLs

To secure incoming and outgoing connections to the VPC, set up the following features:

  • Security Groups – Act as stateful firewalls that control traffic to one or more Amazon EC2 instances. Every instance must be associated with one or more security groups. With security groups, you can only allow specific connections; by default, connections are blocked.
  • Network ACLs – Act as a stateless firewall that controls traffic going in and out of a subnet. With network ACLs, you can allow and block connections. By default, an Amazon network ACL blocks all traffic.

Amazon_aws.png 
For more information on Amazon security groups and network ACLs, see http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Security.html. 

Step 4.1. Create a Security Group for Barracuda NG Admin Access
  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, expand SECURITY and then click Security Groups.
  3. Click Create Security Group.
  4. In the Create Security Group window, configure the following settings:
    • Name – Enter NGSecurityGroup.
    • Description – Enter Access for NG Admin.
    • VPC – Select the VPC from the list (e.g., vpc-b0a9a0db).
  5. Click Yes, Create.
    AwsCreateNGSecurityGroup.png
  6. Select NGSecurityGroup.
  7. In the lower pane, click the Inbound tab.
  8. Add rules with the following settings to allow inbound traffic for the SSH daemon and ping:

    Create a new RuleSource

    SSH

    0.0.0.0/0

    All ICMP

    0.0.0.0/0
    DNS0.0.0.0/0
  9. Add custom rules with the following settings to allow inbound traffic for Barracuda NG Admin (port 807), the VPN service (port 691), and the management tunnel (port 692):

    Create a new RulePort rangeSource

    Custom TCP rule

    8070.0.0.0/0

    Custom UDP rule

    8070.0.0.0/0

    Custom TCP rule

    691-6920.0.0.0/0

    Custom UDP rule

    691-6920.0.0.0/0
  10. Create additional rules for all services running on the Barracuda NG Firewall and all services forwarded for EC2 Instances in the Amazon VPC (e.g., port 80/443 for web servers, port 25 for SMTP, etc.).
  11. Click Apply Rule Changes.

All inbound rules are now listed under the Inbound tab of the security group.  

Step 4.2. Configure a Security Group for the Private Subnetwork

Instances in the private subnetwork are only accessed by connections passing through the Barracuda NG Firewall EC2 instance. Configure the default security group to only allow traffic that is coming from the NGSecurityGroup.

  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, expand SECURITY and then click Security Groups.
  3. Select the default security group. 
  4. In the lower pane, click the Inbound tab.
  5. Add rules with the following settings to allow incoming traffic for the default security group coming from the NGSecurityGroup and for traffic within in the default security group.

    RuleRule Settings
    To allow incoming traffic from the NGSecurityGroup.
    • Create a new Rule – Select All Traffic.
    • Source – Enter the group ID for NGSecurityGroup (e.g., sg-cf49bca0). You can find the group ID by selecting the NGSecurityGroup security group and then clicking the Details tab.
    To allow incoming traffic from the default security group.
    • Create a new Rule – Select All Traffic.
    • Source – Enter the group ID for the default security group (e.g., sg-ae4ebbc1). You can find the group ID by selecting the default security group and then clicking the Details tab.
  6. Click Apply Rule Changes.
  7. Click the Outbound tab.
  8. Add the following rules to allow all outgoing traffic coming from the default security group going to the NGSecurityGroup or for traffic within the default security group.

    RuleRule Settings
    To allow outgoing traffic to the NGSecurityGroup.
    • Create a new Rule – Select All Traffic.
    • Source – Enter the group ID for NGSecurityGroup (e.g., sg-cf49bca0). You can find the group ID by selecting the NGSecurityGroup security group and then clicking the Details tab.
    To allow outgoing traffic within the default security group.
    • Create a new Rule – Select All Traffic.
    • Source – Enter the group ID for the default security group (e.g., sg-ae4ebbc1). You can find the group ID by selecting the default security group and then clicking the Details tab.
  9. Click Apply Rule Changes.

The default security group now lets all traffic pass between the two security groups.
AwsDefaultSecurityGroupList.png  

Step 4.3. Set Up the Network ACLs

By default, network ACLs block all incoming and outgoing traffic. To use the Barracuda NG Firewall instead of the Amazon network ACL, add rules to allow all inbound and outbound traffic.

To use the Barracuda NG Firewall as a gateway device, allow all traffic into the private network.

  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, expand SECURITY and then click Network ACLs.
  3. Click Create Network ACL.
  4. Select the VPC with the 192.168.0.0./16 subnet (e.g., vpc-abcd1234568 (192.168.0.0/16)), and then click Yes, Create
  5. Click the Inbound tab.
  6. Add a rule with the following settings to allow inbound traffic.

    TrafficRule Settings
    Inbound
    • Create a new Rule: All Traffic
    • Rule #: 100
    • Source: 0.0.0.0/0
    • Allow/Deny: ALLOW
  7. Click the Outbound tab.
  8. Add a rule with the following settings to allow outbound traffic.

    TrafficRule Settings
    Outbound
    • Create a new Rule: All Traffic
    • Rule #: 100
    • Source0.0.0.0/0
    • Allow/Deny: ALLOW

The network ACL now permits all traffic on all ports in and out of the subnets. All hosts in the private network are protected by the Firewall service running on the Barracuda NG Firewall.
AwsNetworkACL.png  

Step 5. Deploy a Barracuda NG Firewall in an Amazon EC2 Instance

In the Amazon VPC that you created in Step 1, launch an Amazon EC2 instance with the Barracuda NG Firewall AMI image. Note that the Barracuda NG Firewall AMI image is EBS backed, so powering down the Barracuda NG Firewall EC2 instance will not result in data loss. The Amazon Launch Instance wizard guides you through the following steps:

Start the Amazon Launch Instance Wizard
  1. Go to the Amazon Web Services EC2 console (https://console.aws.amazon.com/ec2/home).
  2. Click Launch Instance.
Launch Instance Wizard Step 1: Choose AMI
  1. Click on AWS Marketplace in the left navigation.
  2. Enter Barracuda NG Firewall in the search box and click Search.
  3. Click Select next to the Barracuda NG Firewall image you want to install (e.g., Barracuda NG Firewall).
    EC2SearchMarketplace.png
Launch Instance Wizard Step 2: Choose Instance Type
  1. Select an EC2 instance type. Verify that the number of CPUs for your license matches the number of vCPUs of the EC2 instance type.
    awsLWchooseInstance.png
  2. Click Next: Configure Instance Details
Launch Instance Wizard Step 3: Configure Instance
  1. From the Network list, select the VPC created in Step 1 (e.g., vpc-b0a9a0db (192.168.0.0/16)).
  2. From the Subnet list, select the 192.168.200.0/24 subnet created in Step 3.1 (e.g., subnet-6f888104 (192.168.200.0/24)).
  3. Select the Enable termination protection check box.
  4. (Optional) To improve I/O performance, enable EBS-optimized instance.
    awsLWConfInstance.png
  5. In the Network Interfaces section, configure the eth0 network interface. This is the primary network interface for the EC2 instance and cannot be changed after the instance is launched.
    • Subnet – This list is set to the subnet selected in step 2. Verify that the 192.168.200.0/24 subnet is selected.
    • Primary IP – Enter 192.168.200.200. If this IP address is unavailable, select another IP address in the 192.168.200.0/24 subnet. When you choose another IP address, you must also change the management IP address on the Barracuda NG Firewall to match the IP address that you will assign in Step 8
  6. Click Add Device.
  7. Configure the eth1 network interface:
    • Subnet – Select the public subnet from the list (e.g., subnet-f6a8a19d (192.168.10.0/24)).
    • Primary IP – Enter an IP address in the public subnet (e.g., 192.168.10.10).

      Because of the Amazon VPC design, the Barracuda NG Firewall receives the static IP address assigned in the Amazon Launch Wizard Interface via DHCP, using the dhcp interface. After the EC2 instance is started, you can reconfigure the dhcp interface as a static interface (eth1) with Barracuda NG Admin.

      awsLWConfNetworkInterfaces.png

  8. Click Next: Add Storage.
Launch Instance Wizard Step 4: Add Storage
  1. (Optional) If you want the EBS volumes to be deleted after the Barracuda NG Firewall EC2 instance has been terminated (deleted), select the Delete on Termination check boxes.
  2. (Optional) Enter a larger Size for the /dev/sdf EBS volume.
  3. (Optional) To improve the I/O performance of your EC2 instance, select Provisioned IOPS from the Volume Type list.
    awsLWConfStorage.png
  4. Click Next: Tag Instance.
Launch Instance Wizard Step 5: Tag Instance
  1. (Optional) Add tags to identify your EC2 instance.
  2. Click Next: Configure Security Group.
Launch Instance Wizard Step 6: Configure Security Group
  1. From the Assign a security group list, select Select an existing security group.
  2. Select the NGSecurityGroup that you created in Step 4.1 from the list of Security Group (e.g., sg-cf49bca0- NGSecurityGroup).
    awsLWConfSecurityGroup.png
  3. Click Review and Launch.
  4. In the Warning window, click Continue.
Launch Instance Wizard Step 7: Review
  1. Click Launch.
  2. In the Select an existing key pair or create a new key pair window:
    • Select Proceed without a key pair.
    • Click the check box to acknowledge that you will not be able to connect to this instance unless you already know the password built into the AMI.
      awsLWkeyPair.png
  3. Click Launch Instances.
Deactivate the Source/Destination Check
  1. Click View Instances.
  2. Right-click the Barracuda NG EC2 instance that you just created, and then select Change Source/Dest. Check.
  3. Click Yes, Disable.
    awsLWDstSrcCheck.png


Your EC2 Instance appears in the EC2 list. After the instance is up, the State and Status Checks change to green.
AwsEC2InstanceList.png  

Step 6. Allocate and Associate an Amazon Elastic IP Address to the Barracuda NG Firewall EC2 Instance

The private IP address assigned to the external interface (eth1) on the Barracuda NG Firewall instance is not yet reachable from the Internet. Create and attach an Amazon Elastic IP Address (EIP) to the external network interface.

  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, click Elastic IPs.
  3. Click Allocate New Address.
  4. From the EIP used in list, select VPC.
  5. Click Yes, Allocate
  6. Select the new EIP, and then then click Associate Address.
  7. In the Associate Address window, configure the following settings:
    • Instance – Select the Barracuda NG Firewall instance (e.g., i-2adb8d65 (Barracuda NG Firewall 5.4.2)).
    • Private IP address – Select the IP address in the public subnet that you created in Step 3.2 (e.g., 192.168.10.89*).
      AwsAssociateElasticIP.png
  8. Click Yes, Associate.

Your EIP is now listed with the instance ID and ENI ID associated with the Barracuda NG Firewall instance.
AwsElasticIPList.png  

Step 7. Create Route Tables

Create two routing tables to route the networks:

  • A table to route traffic in the private network to the internal interface on the Barracuda NG Firewall. 
  • A table to route traffic from the Barracuda NG Firewall's external interface to the Internet gateway.

These route tables ensure that all traffic in the VPC passes through the Barracuda NG Firewall. 

Step 7.1. Create a Route Table for the Private Network

Route all traffic in the private network to the eth0 interface on the Barracuda NG Firewall.

  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, click Route Tables.
  3. Click Create Route Table.
  4. Select the VPC with the 192.168.0.0./16 subnet (e.g., vpc-abcd1234568 (192.168.0.0/16)), and then click Yes, Create.
  5. From the list of route tables on the page, select the route table that you just created.
  6. In the lower pane, click the Routes tab and then add a routing entry with the following settings:
    • Destination – Enter 0.0.0.0/0.
    • Target – Select Enter network interface ID, and then select the network interface in the private subnet for the Barracuda NG Firewall (e.g., eni-7a696111). To find the network interface ID, go to the AWS EC2 console and click Network Interfaces. The network interface is in the 192.168.200.0/24 subnet. 
  7. Click Add.
  8. Click the Associations tab.
  9. From the Select a subnet list, select the 192.168.200.0/24 subnet (e.g., subnet-d79be8bf (192.168.200.0/24)).
    AwsRoutingPrivateNetworkAssociation.png
  10. Click Associate.
  11. Click Yes, Associate to confirm the association.
    AwsRoutingPrivateNetwork.png  
Step 7.2. Create a Route Table for the Public Network

Route traffic from the Barracuda NG Firewall's external interface to the Internet gateway that you created in Step 2.

  1. Go to the Amazon Web Services VPC console (https://console.aws.amazon.com/vpc/home).
  2. In the left pane, click Route Tables.
  3. Click Create Route Table.
  4. Select the VPC with the 192.168.0.0./16 subnet (e.g., vpc-abcd1234568 (192.168.0.0/16)), and then click Yes, Create.
  5. From the list of route tables on the page, select the route table that you just created.
  6. In the lower pane, click the Routes tab and then add a routing entry with the following settings:
    • Destination – Enter 0.0.0.0/0.
    • Target – Select the Internet gateway that you created in Step 2 (e.g., igw-6e81f206).
  7. Click Add.
  8. Click the Associations tab.
  9. From the Select a subnet list, select the 192.168.XX.0/24 subnet that you created in Step 3.2 (e.g., subnet-2429574c (192.168.10.0./24)).
    AwsRoutingPublicNetworkAssociation.png
  10. Click Associate.
  11. Click Yes, Associate to confirm the association.
    AwsRoutingPublicNetwork.png

Your Barracuda NG Firewall instance is now reachable from the Internet. 

Step 8. Optional: Change the Management IP Address on the Barracuda NG Firewall Instance

You only need to change the management IP address if you assigned an IP address that is different from 192.168.200.200 to the eth0 interface in Step 5. After the Barracuda NG Firewall EC2 instance starts, the internal interface is always set to 192.168.200.200, even if the Amazon network interface is assigned a different IP address. Complete the following steps to set the Amazon network interface as the management IP address.

  1. With Barracuda NG Admin, log into the Barracuda NG Firewall. Use the following settings:
    • Management IP: The Amazon Elastic IP address that you created in Step 6 (e.g., 54.229.198.60).
    • Loginroot
    • Password: <your Instance ID> (e.g., i-2adb8d65)

      Until you successfully license your Barracuda NG Firewall, the default password (ngf1r3wall) also authenticates the root user.

  2. Change the management IP address to the IP address that you configured for eth0 in Step 5.
    1. Open the Network page (Config > Full Config > Box > Network).
    2. Click Lock.
    3. In the Management IP (MIP) field, enter the IP address that you configured for eth0 (e.g., 192.168.200.201).
    4. Click Send Changes. Do not activate.
  3. In the settings for the DHCP-2-MGMT firewall rule, add the IP address that you configured for eth0 in Step 5.
    1. Open the Forwarding Rules page (Config > Full Config > Box > Virtual Servers > S1 EXPORT > NGFW (Firewall) > Forwarding Rules).
    2. Click Lock.
    3. Edit the DHCP-2-MGMT rule.
    4. In the Redirection Local Address field, enter a space-delimited list that includes the IP address that you configured for eth0 and the old management IP address of 192.168.200.200. For example:
      192.168.200.201 192.168.200.200
    5. Click OK.
  4. Click Send Changes and then click Activate.
  5. Activate your network changes with a Force activation.

    You must use Force to activate the network. If you use the Failsafe network activation and lose access to the Barracuda NG Firewall, restart the Barracuda NG EC2 instance to restore the previous working configuration stored in the PAR file.

    1. Open the Box page (Control > Box).
    2. In the left pane, expand Network and then click Activate new network configuration.
    3. In the Network Activation window, click Force.
  6. Close Barracuda NG Admin.
  7. With Barracuda NG Admin, log into the Barracuda NG Firewall.

All Amazon EC2 instances in the private subnet are now reachable via the Barracuda NG Firewall EC2 instance.

Step 9. Optional: Change the External Interface from Dynamic to Static

The external network interface uses a DHCP interface to retrieve the static IP address set in Step 5. Many services cannot run on dynamic interfaces making, so you can choose to reconfigure the external interface. The static eth1 interface must be configured on the box level.

  1. Log into the Barracuda NG Firewall EC2 instance.
  2. Open the Network page (Config > Full Config > Box > Network).
  3. Click Lock.
  4. Disable DHCP and delete the DHCP01 link.
    1. In the left pane, click xDSL/DHCP/ISDN.
    2. Select DHCP01 in the DHCP Links table and click the red X to delete the entry. 
    3. Select no to disable DHCP. 
    4. Click Send Changes. Do not activate!
  5. Configure the eth1 interface.
    1. In the left pane, click IP Configuration.
    2. In the Additional Local IPs section, click the plus sign (+).
    3. Enter a name for the IP address (e.g., ExternalVPCIP).
    4. In the IP Address Configuration window, configure the static IP address with the following settings:
      • Interface Name – Select eth1
      • IP Address Enter the IP address that was assigned to eth1 interface in Step 5 (e.g., 192.168.10.10).
      • Responds to Ping Select yes.
      • Management IP – Select no
      • Trust Level – Select Untrusted
      • Default Gateway – Enter the default gateway. In Amazon VPC subnets, the gateway is X.X.X.1 (e.g., if the subnet is 192.168.10.0/24, the gateway is 192.168.10.1).
    1. Click OK.
    2. Click Send Changes and then click Activate.
  6. Activate your network changes with a Force activation.
    1. Open the Box page (Control > Box).
    2. In the left pane, expand Network and then click Activate new network configuration.
    3. In the Network Activation window, click Force. 

Additional Information

  • Do not delete the default virtual server S1. By deleting the virtual server, the application redirect rule that lets you connect to the Barracuda NG Firewall EC2 is removed.
  • When you add additional IP addresses to network interfaces or virtual servers on the Barracuda NG Firewall, you must also add these IP addresses to the respective Amazon network interfaces as additional IP addresses. Depending on the Amazon EC2 instance type used, there are limitations on the number of IP addresses that you can assign to a single Amazon network interface.
  • To patch or update the Barracuda NG Firewall EC2 instance firmware, it is recommended that you use the Barracuda NG Admin graphic interface and not the SSH shell.
  • When using a Barracuda Control Center to manage the Barracuda NG Firewall EC2 instance, place the PAR file generated by the Control Center in /opt/phion/update and reboot the EC2 instance.

    Do not use NG Admin "Restore from PAR file" feature to import the PAR file generated by the Barracuda Control Center. You will lock yourself out of the Barracuda NG Firewall EC2 instance.

Troubleshooting Tips

  • If you cannot connect to the other Amazon EC2 instances in the private subnet, check the following settings:
    • Network Interfaces – Mismatch between the IP address assigned to the network interface on the Barracuda NG Firewall and the Amazon Network Interface associated with it.
    • Security Groups – If the settings for the Security Group are too restrictive, the traffic will be blocked by the Amazon firewall. For debugging purposes, introduce a Security Group policy allowing all traffic in and out, and all traffic between the two security groups.
    • Network ACLs – If the rules in the Amazon network ACLs are too restrictive, traffic going into the subnet will be blocked by the Amazon firewall.
    • Routing Tables – Verify that the Amazon network interface associated with eth0 on the Barracuda NG Firewall is the default gateway for the private subnet and that the private subnet is associated with the correct routing table.
  • If you cannot connect to the Internet from the Barracuda NG firewall, check the following settings:
    • Security Groups – If the settings for the Security Group are too restrictive, the traffic will be blocked by the Amazon firewall. For debugging purposes, introduce a Security Group policy allowing all traffic in and out, and all traffic between the two security groups.
    • Network ACLs – If the rules in the Amazon Network ACLs are too restrictive, traffic going into the subnet will be blocked by the Amazon firewall.
    • Routing Tables – Verify that the Amazon Internet Gateway (igw) is the default route and that the public subnet is associated with the correct routing table.

Next Steps

To continue setting up the Barracuda NG Firewall, you can proceed with the following tasks:

TaskInstructions
License the Barracuda NG Firewall.How to Install the License Token on a Standalone Barracuda NG Firewall Vx
(Optional) Make the Barracuda NG Firewall centrally manageable without a Barracuda NG Control Center.How to Make a Barracuda NG Firewall Centrally Manageable Without a Barracuda NG Control Center

(Optional) How to Add a Barracuda NG Firewall to the Barracuda NG Control Center

Read Additional Information section to successfully add the Barracuda NG Firewall EC2 Instance to the Barracuda NG Control Center

How to Add a Barracuda NG Firewall to the Barracuda NG Control Center

Feedback
If you have a technical issue with the product, please contact Barracuda Networks Technical Support. Did you find this article helpful: |