How to Connect a Barracuda CloudGen Firewall to a SecureEdge Access Point of Presence (PoP)
This article explains how to connect a Barracuda CloudGen Firewall (CGF) to a Barracuda SecureEdge Access Point of Presence (Access PoP). Once connected, SecureEdge Access users in any region can reach resources on the CGF's internal networks. The CGF and Access PoP exchange routes automatically via BGP, so no manual routing is required.
Requirements
Before you begin, ensure that:
The Barracuda CloudGen Firewall is running firmware version 10.5.0 or higher.
The CGF is running in Policy Profile mode. Application Control is not supported.
The CGF has at least one WAN/ISP interface and one LAN interface.
Your SecureEdge workspace has Access PoPs provisioned. If no Access PoP regions are available, contact Barracuda Support.
The Barracuda SecureEdge Access client is installed and licensed for users who need access to resources behind the CGF.
Step 1. Configure the CloudGen Firewall
Before joining the CGF to SecureEdge Manager, complete the following configuration on the firewall using Barracuda Firewall Admin.
1a. Configure the WAN (ISP) Interface
In Barracuda Firewall Admin, go to Configuration and open the WAN/ISP interface (for example, eth2).
Make sure Direct Internet Access is enabled.
For Trust Level, select Untrusted.
Enable the Establish transport to SecureEdge checkbox.
Click OK to save.
For more information, see How to Configure an ISP with Static IP Addresses.
1b. Configure the LAN Interface
Open the LAN interface.
Set Trust Level to Trusted.
Click OK to save.
1c. Create and Activate the VPN Service
In Barracuda Firewall Admin, go to VPN and create the VPN service.
Set the service status to Active.
Configure the service to listen on the WAN/ISP interface you configured in Step 1a.
Save and activate.
1d. Create and Activate the BGP Service
In Barracuda Firewall Admin, open the OSPF-RIP-BGP service (or create a new BGP service).
Set the service status to Active. No additional configuration is required.
Save and activate.
1e. Verify Policy Profile Mode
Confirm that the Next-Generation Firewall (NGFW) is running in Policy Profile mode (not Transparent mode).
Note: All five requirements (ISP interface, LAN as trusted, VPN service active, BGP service active, and Policy Profile mode) must be in place before the CGF can establish a tunnel to an Access PoP.
Step 2. Register the CGF in SecureEdge Manager
Register the CGF with SecureEdge Manager and verify that it appears as online.
Go to https://se.barracudanetworks.com and log in.
The chosen Tenant/Workspace is displayed in the top menu bar.
From the drop-down menu, select the workspace your CGF appliance should be assigned to.
In the left menu, click Integration and select CloudGen Firewall. The CloudGen Firewall page opens.
Click Registration Token and copy the token that is generated.
Connect to the Barracuda CloudGen Firewall using Barracuda Firewall Admin.
Click the SecureEdge icon and enter the registration token.
Submit the token. The CGF begins connecting to SecureEdge Manager.
Verify the CGF Enrollment
To verify that the CGF was successfully enrolled:
In Barracuda Firewall Admin, go to CONTROL > SecureEdge Integration. In the SECUREEDGE INTEGRATION section of the CGF dashboard, verify that SecureEdge displays a green checkmark, indicating that the appliance is connected to SecureEdge Manager.
In SecureEdge Manager, go to Integration > CloudGen Firewall and verify that the CGF appears in the list with a green status indicator.
For more information, see How to Configure a Barracuda CloudGen Firewall in Barracuda SecureEdge.
Step 3. Add a Forwarding Rule on the CloudGen Firewall
Create a firewall forwarding rule that allows traffic arriving from the VPN interface to reach the LAN networks. Without this rule, traffic from SecureEdge Access users will be blocked at the firewall.
In Barracuda Firewall Admin, go to FIREWALL > Forwarding Rules.
In Main Rules, add a new Pass rule with the following settings:
Name: Enter a descriptive name, for example,
SEA-2-LAN.Action: Select Pass.
Source: Select the VPN interface, for example,
0.0.0.0/0 vpnr1.Service: Select Any, including TCP, UDP, ICMP, and ALLIP.
Destination: Select Trusted LAN (Ref: Trusted LAN Networks).
Click OK and activate the rule.
The new forwarding rule appears in the Main Rules list and passes traffic from the VPN interface to Trusted LAN networks.
Step 4. Verify Access PoP in SecureEdge Manager
Verify that Access PoP regions are enabled and visible in your SecureEdge workspace.
In SecureEdge Manager, go to Infrastructure > Points of Presence and verify that Access PoP region is listed with its corresponding IP address. The Points of Presence page displays the available Access PoP regions. If no regions are listed, Access PoPs are not provisioned for your workspace. Contact Barracuda Support for assistance.
Step 5. Configure SecureEdge Access and Connect to an Access PoP
Install the Barracuda SecureEdge Access agent on a client device and connect it to an available Access PoP region.
Download and install the Barracuda SecureEdge Access agent on the client device.
Log in with your Barracuda Cloud Control credentials.
In the agent, open the Resource Tunnels view.
The agent discovers and lists the available Access PoP regions. Wait for at least one region to show an Active status.
Verify that at least one Access PoP region in the SecureEdge Access agent shows an Active status, confirming that the tunnel is established.
Step 6. Verify Cross-Region Connectivity
Confirm that a SecureEdge Access client connected to one Access PoP region can reach resources behind the CGF, even if the CGF is connected to a different region. This validates that inter-region routing is working correctly.
Connect the SecureEdge Access agent to one Access PoP region, for example, UK South.
Connect the CGF to a different Access PoP region, for example, US East.
From the client device, verify that
server1.example.com.resolves successfullyVerify access to the CGF resources using an appropriate tool or protocol, such as
DNS lookup,ping,SSH,HTTP,iperf, orFTP.Confirm that the resources remain reachable when the SecureEdge Access agent and CGF are connected to different Access PoP regions.
The SecureEdge Access agent shows the connected region (for example, UK South) as Main and Active, while the other region (for example, US East) is also Active. This confirms that resources on the CGF LAN remain accessible even when the SecureEdge Access agent and the CGF are connected to different Access PoP regions.
Note: SecureEdge automatically routes traffic between Access PoP regions, so users don’t need to be connected to the same Access PoP region as the CGF to reach its resources.