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 NextGen Firewall X

Example - Configuring a Site-to-Site IPsec VPN Tunnel

  • Last updated on

To configure a Site-to-Site VPN connection between two Barracuda NextGen X-Series Firewalls, in which one unit (Location 1) has a dynamic Internet connection and the peer unit (Location 2) has a static public IP address, create an IPsec tunnel on both units. In this setup, Location 1 acts as the active peer. You will need to add an access rule to allow VPN traffic. Because the WAN IP address of Location 1 is chosen dynamically via DHCP, the remote gateway on Location 2 must use 0.0.0.0/0 so that any incoming IP address is accepted. Using 0.0.0.0/0 as the remote gateway is supported only for site-to-site tunnels in Aggressive mode. This setup does not require third-party DNS services such as DynDNS.

s_to_s_dynamic.png

This example configuration uses the following settings:

 X-Series Firewall Location 1X-Series Firewall Location 2
Published VPN Network172.16.0.0/2410.0.0.0/25
Public IP Addressesdynamic via DHCP62.99.0.74

Before you Begin

On the VPN > Settings page of both X-Series Firewalls, verify that you selected a valid VPN certificate. For more information, see Certificate Manager.

Step 1. Enable VPN Listener on the Dynamic IP Address of the Active Peer

On the X-Series Firewall at Location 1, enable Use Dynamic IPs in the GLOBAL SERVER SETTINGS of the VPN > Settings page for the VPN service to listen on all IP addresses. 

s2s_dynamic_ips.png

Step 2. Create the IPsec Tunnel on Location 1

Configure the X-Series Firewall at Location 1 with the dynamic WAN IP as the active peer.

  1. Log into the X-Series Firewall at Location 1.
  2. Go to the VPN > Site-to-Site VPN page. 
  3. In the Site-to-Site IPSec Tunnels section, click Add.  
  4. Enter a Name for the VPN tunnel.
  5. Configure the settings for Phase 1 and Phase 2.
    s2s_ipsec_settings01.png 
  6. Specify the network settings:
    • Local EndSelect Active.
    • Local AddressSelect Dynamic.
    • Local NetworksEnter 172.16.0.0/24 (the network address for the locally configured LAN), and click +.
    • Remote GatewayEnter 62.99.0.74 (the WAN IP address of Location 2).
    • Remote NetworksEnter 10.0.0.0/25 (the remote LAN), and click +.
  7. Specify the authentication settings:
    • AuthenticationSelect Shared Passphrase.
    • Passphrase Enter the shared secret.
  8. Enable Aggressive Mode.
  9. Define the Aggressive Mode ID.
    s2s_ipsec_settings02.png
  10. Click Add.

Step 3. Create the IPsec Tunnel on Location 2

Configure the X-Series Firewall at Location 2, with the static WAN IP as the passive peer. Use 0.0.0.0/0 as the IP address for the remote gateway to allow the Location 1 unit to use dynamic WAN IP addresses.

  1. Log into the X-Series Firewall at Location 2.
  2. Go to the VPN > Site-to-Site VPN page. 
  3. In the Site-to-Site IPSec Tunnels section, click Add. 
  4. Enter a Name for the VPN tunnel.
  5. Configure the same settings for Phase 1 and Phase 2 as for Location 1.
  6. Specify the network settings:
    • Local End – Select Passive.
    • Local Address – Select 62.99.0.74 (the WAN IP address of Location 2).
    • Local Networks – Enter 10.0.0.0/25 (the network address for the locally configured LAN), and click +.
    • Remote Gateway – Enter 0.0.0.0/0 because the WAN IP address of location 1 is chosen dynamically via DHCP.
    • Remote Networks – Enter 172.16.0.0/24. (the remote LAN), and click +.
  7. Specify the authentication settings:
    • Authentication – Select Shared Passphrase.
    • Passphrase Enter the shared secret.
  8. Enable Aggressive Mode.

  9. Define the Aggressive Mode ID.
    s2s_ipsec_settings04.png 

  10. Click Add. 

Step 4. Configure the Access Rule for VPN Traffic

Remote and local subnets are automatically added to the VPN-Local-Networks and VPN-Remote-Networks network objects when saving the Site-to-Site VPN configuration. If not present, go to FIREWALL > Network Objects and create these network objects. For more information, see Network Objects.

s2s_net_objects.png

Create PASS access rules on both Location 1 and Location 2 X-Series Firewalls to allow traffic in and out of the VPN tunnel.

  1. Log into the X-Series Firewall.
  2. Go to FIREWALL > Firewall Rules page.
  3. Add an access rule with the following settings:
    • ActionAllow
    • ConnectionSelect No SNAT
    • Bi-directionalSelect the Bi–directional checkbox.
    • ServiceSelect Any. All types of network traffic are allowed between the remote and local network.
    • Source – Select the VPN-Local-Networks network object.
    • DestinationSelect the VPN-Remote-Networks network object.

    s2s_access_rule.png

  4. At the top of the Add Access Rule window, click Add.
  5. Use drag and drop to place the access rule above any other access rule matching this traffic.
  6. Click Save.

Step 5. Verify Successful VPN Tunnel Initiation and Traffic Flow

To verify that the VPN tunnel was initiated successfully and traffic is flowing, go to the VPN > Site-to-Site VPN page. Verify that green check marks are displayed in the Status column of the VPN tunnel.

s2s_ipsec_tunnels.png

Use ping to verify that network traffic is passing the VPN tunnel. Open the console of your operating system and ping a host within the remote network. If no host is available, you can ping the management IP address of the remote X-Series Firewall. Go to the NETWORK > IP Configuration page and ensure that Services to Allow: Ping is enabled for the management IP address of the remote firewall.

If network traffic is not passing the VPN tunnel, go to the BASIC > Recent Connections page and ensure that network traffic is not blocked by any other access rule.

Last updated on