Cisco ASA and Firebox Branch Office VPN Integration Guide (2024)

WatchGuard provides integration instructions to help our customers configure WatchGuard products to work with products created by other organizations. If you need more information or technical support about how to configure a third-party product, refer to the documentation and support resources for that product.

This integration guide describes how to configure a Branch Office VPN (BOVPN) tunnel between a WatchGuard Firebox and a Cisco Adaptive Security Appliance (ASA).

Contents

• Cisco ASA and Firebox Branch Office VPN Integration Guide
• Contents
• Integration Summary
• Topology
• Configure the Firebox
• Configure the Cisco ASA
• Test the Integration

Topology

This diagram shows the topology for a BOVPN connection between a Firebox and a Cisco ASA.

Configure the Firebox

To configure a BOVPNconnection on the Firebox, from Fireware Web UI:

1. Select VPN > Branch Office VPN.
   The Branch Office VPN configuration page opens.
2. In the Gateways section, click Add.
3. In the Gateway Name text box, type a name to identify this Branch Office VPN gateway.
4. From the Address Family drop-down list, select IPv4 Addresses.
5. In the Credential Method section, select Use Pre-Shared Key.
   
6. In the adjacent text box, type the pre-shared key.

8. In the Gateway Endpoint section, click Add.
   The Gateway Endpoint Settings dialog box opens.
9. From the External Interface drop-down list, select External.
10. From the Interface IP Address drop-down list, select Primary Interface IPv4 Address.
    The Primary Interface IP Address is the primary IPaddress you configured on the selected external interface.
11. Select By IP Address.
12. In the adjacent text box, type the primary IP address of the External Firebox interface.
    

13. Select the Remote Gateway tab.
14. Select Static IP Address.
15. In the adjacent text box, type the IP address of your Cisco ASA WANconnection.
16. Select By IP Address.
17. In the adjacent text box, type the IP address of your Cisco ASA WAN connection.
    

18. Click OK.
19. In the Gateway Endpoint section, select the Start Phase 1 tunnel when Firebox starts check box.

20. Select the Phase 1 Settings tab.
21. From the Version drop-down list, select IKEv2.
22. Keep all other Phase 1 settings as the default values.

23. Click Save.
24. In the Tunnels section, click Add.

25. From the Gateway drop-down list, select the gateway that you configured.
26. In the Addresses section, click Add.

27. In the Local IP section, from the Choose Type drop-down list, select Network IPv4.
28. In the Network IP text box, type the local IP segment. This is the local network protected by the Firebox.
29. In the Remote IP section, from the Choose Type drop-down list, select Network IPv4.
30. In the Network IP text box, type the remote IP segment. This is the local network protected by the Cisco ASA.

31. Click OK.
32. Keep Phase 2 Settings as the default values.

33. Click Save.

Configure the Cisco ASA

In our example, we configure a Cisco ASA 5506-X.

To configure the ASA 5506-X basic settings:

1. Log in to the ASA 5506-X with ASDM. The default IP address is 192.168.1.1.
2. Configure the ASA 5506-X interfaces. For information about how to configure interfaces, refer to the Cisco ASA 5506-X documentation.
3. Select the Enable traffic between two or more interfaces which are configured with same security levels check box.
4. Click Apply.

To configure the IPSec VPN settings:

1. Click Configuration.
2. Select Site-to-Site VPN > Advanced > IKE policies.
3. In the IKEv2 Policies section, click Add.
4. In the Priority text box, type 1.
5. From the D-H Group drop-down list, select 14.
6. From the Encryption drop-down list, select aes-256.
7. From the Integrity Hash drop-down list, select sha256.
8. From the Pseudo Random Function (PRF) Hash drop-down list, select sha256.
9. Leave the default value for all other settings.

10. Click OK.
11. Click Apply.

12. Select Configuration > Site-to-Site VPN > Advanced > IPsec Proposals (Transform Sets).
13. In the IKEv2 IPsec Proposals section, click Add.
14. In the Name text box, type an object name. In our example, we specify the name AES256-SHA256.
15. From the Encryption drop-down list, select aes-256.
16. From the Integrity Hash drop-down list, select sha-256.

17. Click OK.
18. Click Apply.

19. From the navigation menu, select Configuration > Firewall > Objects > Network Objects/Groups.
20. Click Add > Network Object.
21. In the Name text box, type the object name. In our example, we specify the name WG_INT. Which is used for the network protected by the WatchGuard Firebox.
22. From the Type drop-down list, select Network.
23. From the IP Version check box, check IPv4.
24. In the IP Address text box, type the IP address. For this example, we use IPaddress 192.168.10.0.
25. In the Netmask text box, type the netmask. For this example, we use netmask 255.255.255.0.

26. Click OK.
27. Repeat Steps 20–26 to create another network object. For this example, we name the network object CISCO_INT. This is used for the network protected by the Cisco ASA.

28. Select Configuration > Site-to-Site VPN > Connection Profiles.
29. In the Connection Profiles section, click Add.

30. In the Peer IP Address text box, type the peer IP address.
31. From the Source Interface drop-down list, select inside.
32. From the Destination Interface drop-down list, select outside.
33. From the Local Network list, select CISCO_INT.
34. From the Remote Network list, select WG_INT.
35. In the IPsec Enabling section, click Manage.
36. Click Add.
37. In the Name text box, type the name. For this example, we use GroupPolicy To WG.
38. In the Tunneling Protocols section, clear the Inherit check box and select IPsec IKEv2.

39. Click OK > OK.
40. Select Local Pre-shared Key.
41. In the adjacent text box, type the pre-shared key.
42. In the Remote Peer Pre-shared Key text box, type the pre-shared key.

43. For the IKE Policy setting, keep the default value.
44. From the IPsec Proposal list, select AES256-SHA256.

45. For the Advanced settings, select Advanced > Crypto Map Entry.
46. In the Perfect Forward Secrecy section, select Enable.
47. From the Diffie-Hellman Group drop-down list, select group14.
48. Leave the default value for all other settings.

49. Click OK.
50. In the Enable interfaces for IPsec access section, select the outside interface and select Allow IKE v2 Access.
51. Click Apply.

52. From the navigation menu, select Configuration > Firewall > NAT Rules.
53. Click Add.
54. In the Match Criteria: Original Packet section, from the Source Interface drop-down list, select inside.
55. From the Source Address drop-down list, select CISCO_INT.
56. From the Destination Interface drop-down list, select outside.
57. From the Destination Address drop-down list, select WG_INT.
58. Under Options, Select the Disable Proxy ARP on egress interface check box.
59. Select the Lookup route table to locate egress interface check box.
60. Leave the default value for all other settings.

61. Click OK.
62. Click Apply.

Test the Integration

To test the integration, from Fireware Web UI:

1. Select System Status > VPN Statistics.
2. Select the Branch Office VPN tab and verify the VPN is established.

3. Verify that the Host behind the Firebox and the Host behind the Cisco ASA can ping each other.