To dynamically learn BGP propagated routes from a remote location connected via TINA VPN tunnel, VPN next hop interfaces are used to create an intermediary network. The BGP service is configured to use the remote IP address in the intermediary network as a BGP neighbor.
You must complete this configuration on both the local and the remote Barracuda CloudGen Firewall using the respective values below:
Example Values for the Local Barracuda CloudGen Firewall | Example Values for the Remote Barracuda CloudGen Firewall | |
---|---|---|
VPN Next Hop Interface Index | 11 | 11 |
VPN Next Hop Interface IP Address | 192.168.21.16/24 | 192.168.21.17/24 |
Shared Network IP Address | 192.168.21.16 | 192.168.21.17 |
VPN Local Networks | 192.168.21.16 | 192.168.21.17 |
VPN Remote Networks | 192.168.21.17 | 192.168.21.16 |
VPN Interface Index | 11 | 11 |
ASN | 64577 | 64578 |
Router ID | 192.168.21.16 | 192.168.21.17 |
Neighbor IPv4 | 192.168.21.17 | 192.168.21.16 |
Neighbor AS Number | 64578 | 64577 |
Neighbor Update Source Interface | vpnr11 | vpnr11 |
Before You Begin
- A free /24 subnet (e.g.,
192.168.21.0/24
) for the intermediary network is needed. - You must have or assign private Autonomous system numbers (ASNs) for the remote and local networks. The ASNs can be private if you are not propagating these networks to other public networks.
Step 1. Add a VPN Next Hop Interface
Add a VPN next hop interface using a /24 subnet (e.g., 192.168.21.0/24
).
- Go to CONFIGURATION > Configuration Tree > Box > Assigned Services > VPN-Service > VPN Settings.
- Click Lock.
- In the left menu, select Routed VPN.
- Next to the Next Hop Interface Configuration table, click Add.
- In the VPN Interface Properties window, configure the following settings and then click OK.
- In the VPN Interface Index field, enter a number between
0
and999
. E.g.,11
- In the IP Addresses field, enter the VPN interface IP address including the subnet. E.g.,
192.168.21.16/24
for the local or192.168.21.17/24
for the remote firewall. - Click OK. The interface is now listed in the Next Hop Interface Configuration table.
- In the VPN Interface Index field, enter a number between
- Click Send Changes and Activate.
Step 2. Add the VPN Interface IP to the Shared IP Addresses
Introduce the IP address of the VPN next hop interface on the firewall.
- Go to CONFIGURATION > Configuration Tree > Box > Network.
- In the left menu, select IP Configuration.
- Click Lock.
- In the Shared Networks and IPs section, click +. The Shared Network and IPs window opens.
- Select the virtual Interface.
- In the Network Address field, enter the network the virtual interface resides in.
- In the Shared IPs in this Network table, click + and add the intermediary VPN IP address of the VPN interface. E.g., 192.168.21.16 for the local firewall or 192.168.21.17 for the remote firewall.
- Click OK.
- Click Send Changes and Activate.
Step 3. Configure the TINA Site-to-Site VPN Tunnel
Configure a TINA VPN tunnel using the local next hop interface IP address and the VPN next hop interface.
- Go to CONFIGURATION > Configuration Tree > Box > Assigned Services > VPN-Service > Site to Site.
- Click Lock.
- Right-click In the TINA Tunnels tab and select New TINA tunnel. The TINA tunnel window opens.
- Enter a Name.
Configure the Transport, Encryption and Authentication settings as well as the Local and Remote public IP addresses. For more information, see How to Create a TINA VPN Tunnel between CloudGen Firewalls.
Leave the Local and Remote Network empty.
In the Remote Networks tab, enter the VPN Interface Index number that you created in the VPN Interface Configuration in step 1. E.g.
11
- Click OK.
- Click Send Changes and Activate.
Step 4. Configure the BGP Service
Enable and configure the BGP service. Configure the remote VPN interface IP address as a BGP neighbor to dynamically learn the routes of the neighboring network.
Step 4.1 Configure which Routes to Propagate into BGP
You can either enter the networks you want to propagate manually, or set the Advertise Route parameter to yes for routes you want propagated.
- Go to CONFIGURATION > Configuration Tree > Box > Network.
- In the left menu, expand the Configuration Mode section, and click Switch to Advanced View.
- Click Lock.
- To propagate the management network, set Advertise Route to yes in the Management IP and Network section.
- In the left menu, click on Routing.
- Double-click on the directly attached routes and gateway routes you want to propagate. The Routes window opens.
- Set Advertise Route to yes and click OK.
- Click Send Changes and Activate.
Step 4.2 Configure the BGP Router
Enable BGP, and use the VPN next hop interface IP address as the Router ID.
- Go to CONFIGURATION > Configuration Tree > Box > Assigned Services > OSPF-RIP-BGP-Service > OSPF/RIP/BGP Settings.
- Click Lock.
- Set Run BGP Router to Yes.
- (optional) To learn routes from the remote ASN, set Operation Mode to advertise-learn.
- Enter the Router ID. Typically the VPN next hop interface IP address is used. E.g.,
192.168.21.16
for the local or192.168.21.17
for the remote firewall.
- In the left menu, click BGP Router Setup.
- Enter the AS Number. E.g.,
64577
for the local firewall or64578
for the remote firewall.
Enter the Terminal Password. Use this password if you must directly connect to the dynamic routing daemon via command line for debugging purposes.
- To propagate the directly attached routes and gateway routes configured in Step 1, set Connected Routes to yes.
- (alternative) To manually enter the networks you want to propagate, click + in the Networks table and enter the network. E.g.,
172.16.0.0/24
- Click Send Changes and Activate.
Step 4.3. Add a BGP Neighbor
To dynamically learn the routing of the neighboring network, set up a BGP neighbor for the VPN next hop interface.
- In the left menu of the OSPF/RIP/BGP Settings page, click Neighbor Setup IPv4.
Click Lock.
Next to the Neighbors table, click the plus sign (+) to add a new neighbor.
- Enter a Name for the neighbor and click OK. The Neighbors window opens.
Configure the following settings in the Usage and IP section:
- Neighbor IPv4: Enter the remote address for the VPN next hop interface. E.g.,
192.168.21.17
for the local firewall or192.168.21.16
for the remote firewall. - OSPF Routing Protocol Usage – Select no.
- RIP Routing Protocol Usage – Select no.
- BGP Routing Protocol Usage – Select yes.
- Neighbor IPv4: Enter the remote address for the VPN next hop interface. E.g.,
In the BGP Parameters section, configure the following settings:
AS Number – Enter the ASN for the remote network. E.g., 64578 for the local firewall or 64577 for the remote firewall.
Update Source – Select Interface.
Update Source Interface – Enter the VPN next hop interface in the format:
vpnr<interface number>
. E.g.,vpnr11
- Click OK.
- Click Send Changes and Activate.
Step 4.4. (optional) Adjust Keep Alive and Hold Timer
Speed up BGP updates by adjusting the keep alive and hold timer.
- Go to CONFIGURATION > Configuration Tree > Box > Assigned Services > OSPF-RIP-BGP-Service > OSPF/RIP/BGP Settings.
- Click Lock.
- In the left menu, click on BGP Router Setup.
- In the left menu, expand the Configuration Mode section and click on Switch to Advanced View.
- Click the Edit button for the Advanced Settings. The Advanced Settings window opens.
- Adjust the following parameters to influence how fast BGP reacts to connections which are down:
- Keep Alive Timer – Default:
60
Recommended:10
- Hold Timer – Set to three times the Keep Alive Timer. Default:
180
Recommended:30
- Keep Alive Timer – Default:
- Click OK.
- Click Send Changes and Activate.
Step 5. Verify the BGP Service Configuration
On the CONTROL > Network page, verify that BGP routes are learned. Click the BGP tab and expand the relevant AS tree. It can take up to three minutes for new routes to be learned. The Origin column lists incomplete for direct attached or gateway routes or IGP routes learned via BGP including manually entered networks.
Local Firewall CONTROL > Network > BGP page:
Remote Firewall CONTROL > Network > BGP page:
Step 6. Create Access Rules for VPN Traffic
Create access rules on both local and remote firewalls to allow traffic from the learned networks through the VPN tunnel.