We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

How to Enable Enhanced Networking in AWS

  • Last updated on

Barracuda F-Series Firewalls using an AWS Instance with enhanced networking support must enable this feature after updating to firmware version 6.2.0 or higher. F-Series Firewalls installed using the 6.2.0 (or higher) HVM image from the marketplace do not need to enable enhanced networking; it is automatically enabled if the image is deployed on an Instance with enhanced networking support.

Before You Begin

  • Verify that you are using an Instance with enhanced networking support. For more information, see Public Cloud.
  • Verify that you are using an HVM image of the Barracuda NextGen Firewall F-Series. PVM images cannot be updated.

    Enabling enhanced networking for PVM Instances will break network connectivity for the Instance.

  • Install AWS CLI. For more information, see https://aws.amazon.com/cli/ 
  • You need the Instance ID for your firewall Instance.

Step 1. Enable Enhanced Networking

  1. Shut down the AWS Instance.
  2. Open a shell and enter:

    aws ec2 modify-instance-attribute --instance-id YOUR_INSTANCE_ID --sriov-net-support simple

    aws_enhanced_networking_set.png

  3. To verify the changes in the AWS configuration, enter:

    aws ec2 describe-instance-attribute --instance-id YOUR_INSTANCE_ID --attribute sriovNetSupport

    aws_enhanced_networking_after.png

  4. Start up the AWS Instance.

Step 2. Verify the Driver

After the Instance is rebooted, you can verify if enhanced network is used by checking the driver used for the network interface.

  1. Log into the firewall via SSH.
  2. Enter ethtool -i INTERFACE_NAME.
    aws_enhanced_networking_driver.png
  3. Verify that you are using the ixgbevf driver.
Last updated on