Quick Start — Set Up a VPN Between Two Fireboxes
This topic does not provide descriptions for the settings in the BOVPN dialog boxes and the effects they can have on a tunnel. For more detailed information about branch office VPN settings, go to:
- About Manual IPSec Branch Office VPNs
- Configure Manual BOVPN Gateways
- Configure Manual BOVPN Tunnels
For detailed configuration examples, go to Manual BOVPN Configuration Examples.
The procedures in this topic describe how to set up a branch office VPN between two Fireboxes that have static external IP addresses. For information about how to set up a BOVPN gateway to a device that uses a dynamic external IP address, go to Define Gateway Endpoints for a BOVPN Gateway.
Quick Start with Fireware Web UI
If both Fireboxes have a static public IP address, you must have this information before you begin:
- Public IP address of each Firebox — This is the IP address that the peer gateway connects to.
- Private IP addresses for each Firebox — This is an IP address used to identify a local network. These are the IP addresses of the computers on each device that are allowed to send traffic through the VPN tunnel.
- Pre-shared key — This is a passphrase used to encrypt and decrypt the data that goes through the VPN tunnel.
Here is a checklist of the information you must collect:
Site A device
Site A External (Public) IP address: ______________________________
Site A Private IP addresses: _____________________________
Site B device
Site B External (Public) IP address: ______________________________
Site B Private IP addresses: _____________________________
Common VPN settings
Pre-shared key: _____________________________
You must also decide what Phase 1 and Phase 2 settings to use. For a VPN between two Fireboxes, you can use the default Phase 1 and Phase 2 settings on both devices. You can select IKEv2 in the Phase 1 settings for improved tunnel reliability.
For a complete list of settings, and a detailed example of how to configure settings for a BOVPN between two Fireboxes, go to Set up a VPN Between Two Fireware Devices (Web UI).
- Select VPN > Branch Office VPN.
- Below the Gateways list, click Add.
- In the Gateway Name text box, type a name to identify this gateway.
- (Fireware v12.4 or higher) From the Address Family drop-down list, select IPv4 Addresses or IPv6 Addresses.
- In the Credential Method section, select Use Pre-Shared Key.
- (Fireware v12.5.4 or higher) Select String-Based or Hex-Based. The default setting is String-Based. For information about hex-based keys, go to Hex-Based Pre-Shared Keys.
- Type the shared key.
- Below the Gateway Endpoint list, click Add.
- From the External Interface drop-down list, select the interface that has the external IP address.
- From the Interface IP Address drop-down list, select Primary Interface IPv4 Address or Primary Interface IPv6 Address.
- Select By IP Address.
- In the By IP Address text box, type the external (public) IP address of the Site A Firebox.
- Select the Remote Gateway tab.
- Select Static IP Address.
- In the Static IP Address text box, type the external (public) IP address of the Site B Firebox.
- Select By IP Address. In the By IP Address text box, type the external IP address of the Site B Firebox.
- Click OK to close the Gateway Endpoint Settings dialog box.
- Click Save to save the gateway settings.
- On the Branch Office VPN page, below the Tunnels list, click Add.
- In the Name text box, type a name for the tunnel.
- From the Gateway drop-down list, select the gateway you created.
- Below the Addresses list, click Add.
- In the Local IP section, from the Choose Type drop-down list, select the type of local address. For example, select Network IPv4 to add an IPv4 subnet.
- In the adjacent text box, type the private network address at Site A.
- In the Remote IP section, from the Choose Type drop-down list, select the type of remote address. For example, select Network IPv4 to add an IPv4 subnet.
- In the adjacent text box, type the private network address at Site B.
- From the Direction drop-down list, select the tunnel direction. The tunnel direction determines which endpoint of the VPN tunnel can start a VPN connection through the tunnel.
- Click OK.
- Click Save to save the tunnel settings.
- Select VPN > Branch Office VPN.
- Below the Gateways list, click Add.
- In the Gateway Name text box, type a name to identify this gateway.
- (Fireware v12.4 or higher) From the Address Family drop-down list, select IPv4 Addresses or IPv6 Addresses.
- In the Credential Method section, select Use Pre-Shared Key.
- (Fireware v12.5.4 or higher) Select String-Based or Hex-Based. The default setting is String-Based. For information about hex-based keys, go to Hex-Based Pre-Shared Keys.
- Type the shared key.
- Below the Gateway Endpoint list, click Add.
- From the External Interface drop-down list, select the interface that has the external IP address.
- Select By IP Address.
- In the By IP Address text box, type the external (public) IP address of the Site B Firebox.
- Select the Remote Gateway tab.
- Select Static IP Address.
- In the Static IP Address text box, type the external (public) IP address of the Site A Firebox.
- Select By IP Address. In the By IP Address text box, type the external IP address of the Site A Firebox.
- Click OK to close the Gateway Endpoint Settings dialog box.
- Click Save to save the gateway settings.
- On the Branch Office VPN page, below the Tunnels list, click Add.
- In the Name text box, type a name for the tunnel.
- From the Gateway drop-down list, select the gateway you created.
- Below the Addresses list, click Add.
- In the Local IP section, from the Choose Type drop-down list, select the type of local address. For example, select Network IPv4 to add an IPv4 subnet.
- In the adjacent text box, type the private network address at Site B.
- In the Remote IP section, from the Choose Type drop-down list, select the type of remote address. For example, select Network IPv4 to add an IPv4 subnet.
- In the adjacent text box, type the private network address at Site A.
- From the Direction drop-down list, select the tunnel direction. The tunnel direction determines which endpoint of the VPN tunnel can start a VPN connection through the tunnel.
- Click OK.
- Click Save to save the tunnel settings.
Quick Start with Policy Manager
If both devices have a static public IP address, you need to know this information before you begin:
- Public IP address of each device — This is the IP address that the peer gateway connects to.
- Private IP addresses for each device — This is an address used to identify a local network. These are the IP addresses of the computers on each device that are allowed to send traffic through the VPN tunnel.
- Pre-shared key — This is a passphrase used to encrypt and decrypt the data that goes through the VPN tunnel.
Here is a checklist of the information you must collect:
Site A device
Site A External (Public) IP address: ______________________________
Site A Private IP addresses: _____________________________
Site B device
Site B External (Public) IP address: ______________________________
Site B Private IP addresses: _____________________________
Common VPN settings
Pre-shared key: _____________________________
You must also decide what Phase 1 and Phase 2 settings to use. For a VPN between two Fireboxes, you can use the default Phase 1 and Phase 2 settings on both devices.
For a complete list of settings, and a detailed example of how to configure settings for a BOVPN between two Fireboxes, go to Set up a VPN Between Two Fireware Devices (WSM).
- In Policy Manager, select VPN > Branch Office Gateways. Click Add.
- In the Gateway Name text box, type a name to identify this gateway in Policy Manager.
- In the Credential Method section, select Use Pre-Shared Key.
- (Fireware v12.5.4 or higher) Select String-Based or Hex-Based. The default setting is String-Based. For information about hex-based keys, go to Hex-Based Pre-Shared Keys.
- Type the shared key.
- In the Gateway Endpoints section, click Add.
- From the External Interface drop-down list, select the interface that has the external IP address.
- Select By IP Address.
- From the IP Address drop-down list, select the external IP address of the Site A device.
- In the Remote Gateway section, select Static IP Address.
- In the IP Address text box, type the external (public) IP address of the Site B device.
- In the for Specify the gateway ID for the tunnel authentication section, select By IP Address.
- In the IP Address text box, type the external IP (public) address of the Site B device.
- Click OK to close the New Gateway Endpoints Settings dialog box.
- Click Close to close the Gateways dialog box.
- In Policy Manager, select VPN > Branch Office Tunnels. Click Add.
- In the Tunnel Name text box, type a name for the tunnel.
- From the Gateway drop-down list, select the gateway you created.
- In the Addresses section, click Add.
- In the Local text box, type the private network address for the Site A local network. You can also click the button adjacent to the Local drop-down list to enter a host IP address, network address, range of host IP addresses, or DNS name.
- In the Remote text box, type the private network address at Site B. You can also click the adjacent button to enter a host IP address, network address, range of host IP addresses, or DNS name.
- From the Direction drop-down list, select the tunnel direction. The tunnel direction determines which endpoint of the VPN tunnel can start a VPN connection through the tunnel.
- Click OK.
- Click Close and save the changes to the Site A device.
- In Policy Manager, select VPN > Branch Office Gateways. Click Add.
- In the Gateway Name text box, type a name to identify this gateway in Policy Manager.
- In the Credential Method section, select Use Pre-Shared Key.
- (Fireware v12.5.4 or higher) Select String-Based or Hex-Based. The default setting is String-Based. For information about hex-based keys, go to Hex-Based Pre-Shared Keys.
- Type the shared key.
- In the Gateway Endpoints section, click Add.
- From the External Interface drop-down list, select the interface that has the external IP address.
- Select By IP Address.
- From the IP Address drop-down list, select the primary static external IP address of the Site B device.
- In the Remote Gateway section, select Static IP Address.
- In the IP Address text box, type the external (public) IP of the Site A device.
- In the for Specify the gateway ID for the tunnel authentication section, select By IP Address.
- In the IP Address text box, type the external (public) IP of the Site A device.
- Click OK to close the New Gateway Endpoints Settings dialog box.
- In Policy Manager, select VPN > Branch Office Tunnels. Click Add.
- In the Tunnel Name text box, type a name for the tunnel.
- From the Gateway drop-down list, select the gateway you created.
- In the Addresses section, click Add.
- In the Local text box, type the local (private) network address for the Site B local network. You can also click the button adjacent to the Local drop-down list to enter a host IP address, network address, range of host IP addresses, or DNS name.
- In the Remote text box, type the private network addresses at the Site A. You can also click the adjacent button to enter a host IP address, network address, range of host IP addresses, or DNS name.
- From the Direction drop-down list, select the tunnel direction. The tunnel direction determines which endpoint of the VPN tunnel can start a VPN connection through the tunnel.
- Click OK.
- Click Close and save the changes to the Site B device.
After you complete and save the VPN configuration on both devices, the devices automatically negotiate the tunnel.
If the devices cannot establish the tunnel, examine the log files on both Fireboxes for the time period you tried to start the tunnel. You should see log messages that show where the failure occurred and which settings could be part of the problem. You can also check the log messages in real time with Firebox System Manager.