Site-to-Site VPN MX95 using DDNS or FQDN

mumer1
Comes here often

Site-to-Site VPN MX95 using DDNS or FQDN

Dear Guys.

I want to configure site to site vpn between Cisco Meraki MX95 and Paloalto.

As Paloalto is placed in the Head office and Meraki Mx95 is in the branch office.

Instead of Public or Live IP, i need to use Hostname. I created DYNDNS hostnames on https://account.dyn.com/.

Shall the Mx95 be Hub or Spoke?

What IKE version I shall use?

What will be the Public IP/Hostname?

What will be Local & Remote ID?

Guide me the parameters (Encryption, Hashing) etc. so that it would be easy for me to establish the tunnel.

 

3 Replies 3
Madhan_kumar_G
Getting noticed

Hi,

 

https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings

 

Followup the link for the below topics,

Non-Meraki VPN peers
Non-Meraki VPN Peering with FQDN

PhilipDAth
Kind of a big deal
Kind of a big deal

If there is no other AutoVPN configuration, the MX will have to be a hub.  You can only select a spoke when another Meraki hub is already in the organisation.

 

I would try and use IKEv2.

 

The ID is usually the static public IP address that each party will be known by.  Having dynamic IP addresses will substantially complicate the configuration.  You may not get it working at all.

mumer1
Comes here often

Dear Member.

I had configured the VPN and the status is UP, but the issue that is being faced is i am unable to ping remote networks.

Secondly it is showing (This security appliance is behind a VPN-friendly NAT).

VPN Status.PNG

 

 

 

 

 

 

Kindly guide me on these.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels