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 Web Security Gateway

Directing Traffic to the Barracuda Web Security Gateway Vx

  • Last updated on

There is no need to shut down your virtual machine when making changes to network connections. On your hypervisor, go to Networks and choose from available networks on your switches. If adding a network adaptor to the virtual machine, you must first shut it down.

For Forward Proxy mode deployment limitations, refer to Limitations of this Deployment Type in the article Forward Proxy Deployment of the Barracuda Web Security Gateway.

Determine Your Deployment Scenario

The Barracuda Web Security Gateway Vx can be deployed in any configuration except for inline. Deploy your Vx:

  1. Using a Forward Proxy Deployment. You can deploy the Barracuda Web Security Gateway Vx in forward proxy mode via PAC file or GPO. This is the most common deployment scenario. See Forward Proxy Deployment of the Barracuda Web Security Gateway.
  2. As a WCCP cache engine on a network with a WCCP capable core routing platform.
  3. With the Barracuda Web Security Agent installed on remote Windows and Macintosh machines. See Using the Barracuda WSA With the Barracuda Web Security Gateway.

Once you have installed your Barracuda Web Security Gateway Vx and configured your firewall, you can test the configuration using the ADVANCED > Troubleshooting page in the web interface to ping updates.barracudacentral.com.

Last updated on