Home > Security Appliances > Site-to-site VPN > Watchguard XTM Site-to-site VPN with MX Series

Watchguard XTM Site-to-site VPN with MX Series

Table of contents
No headers

The Watchguard XTM can form a site-to-site VPN with a Meraki MX series security appliance.

To do this, log in to Watchguard by connecting to its IP address via a web browser. On the left hand side, click on VPN->Branch Office VPN. Under the Gateways tab, click Add and give the gateway an appropriate name:

88b1aaaa-cc04-442d-a9b0-967537a084a6

 

Under the General Settings tab, select the radio button for Pre-Shared Key and enter the key string exactly as it appears on the MX under Configure > VPN > Non-Meraki VPN peers > (peer) > "Preshared secret". In the Gateway Endpoints section, click the Add button to be brought to the Gateway Endpoint Settings page to specify the local and remote peers participating in the VPN tunnel. If the MX is sitting behind a device performing NAT, the Remote IP will be the public address of the MX, while the Remote ID will be the private address.

d1fbb330-f696-48ba-935e-f693ddc33fe3

 

Under Local Gateway, select the radio button for By IP Address and enter the public IP address of the Watchguard. 

Under the section labeled Remote Gateway, select the radio button for Remote Gateway Static IP Address and enter the public IP address of the MX security appliance. Please note that this must be the IP address of the primary interface specified on the MX under Monitor > Appliance status. Therefore if the primary uplink is configured as Internet 1, then use Internet 1's IP address. 

Under the section for Gateway ID for Tunnel Authentication select By IP address and again enter the public IP of the MX security appliance. Select the OK button.

084e456e-4fb0-4c3d-81f5-7eed8168b9b2

 

Note: This section walks through configuring a site-to-site VPN tunnel on the Watchguard XTM, assuming the Cisco Meraki peer is using its default IPsec policy. If Custom IPsec Policies have been configured in Dashboard, please be sure to use those phase 1+2 parameters in Watchguard.

Back on the Gateway page, select the tab Phase 1 Settings and ensure that Main is selected in the drop down menu labeled Mode. NAT traversal and Dead Peer Detection are not required but can remain selected for improved tunnel stability.

Under Transform Settings select Add and ensure that under Phase 1 settings, SHA1-3DES is chosen for the encryption and authentication algorithms and that under Key Group, Diffie-Hellman Group 2 is selected. Click the Save button to be returned to the Branch Office VPN Page.

Under the Tunnels Section select the Add button.

3ed4a4af-fb73-42f5-85a6-dc50667268fc

 

Give the tunnel group a meaningful name, in our case VPN Phase 2. In the drop down menu labeled Gateway, select the name you created in the previous step.

Under the Addresses section select the Add button. In the field for Local IP enter the local IP subnet range. Additionally select Network IP for the Remote IP section and enter the subnet of the MX security appliance. Be sure to check the box for adding the tunnel to the BOVPN-Allow policies and that the tunnel is configured for bi-directional communication. 

67ff56e8-ddd3-496d-bff8-78414ac1bf98

 

Click the tab Phase 2 Settings to move to the next section. Make sure that the checkbox for PFS or Perfect Forwarding Secrecy is unchecked.

Under IPSec Proposals, the drop down menu specifies a variety of encryption and authentication methods. The MX security appliance can accept any of the following Encryption algorithms: DES, 3DES, AES-128, AES-192 and AES-256. Additionally the MX can accept either SHA1 or MD5 as the authentication hashing algorithm. Any combination of encryption and authentication algorithms can work, however please use ESP as the IPSec protocol suite.

Click the Add button to add these to the list and select the Save button to be brought back to the Branch Office VPN page. With the settings saved to the Watchguard, it will attempt to establish a IPsec VPN tunnel with the MX once client traffic attempts to access the remote subnet.

 

For more information on setting up the MX to participate in a site-to-site VPN, please review the following articles:

3rd Party Site-to-Site VPN

Meraki MX Security Appliance Site to Site VPN

You must to post a comment.
Last modified
19:19, 9 Feb 2016

Tags

Classifications

This page has no classifications.

Article ID

ID: 1372

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community