we have multiple locations with Meraki Firewalls that are using the Meraki Site-to-site VPN connection in a Hub configuration.

We would like to add our VPC to our Site-to-Site VPN so that if any location goes down, other branches will have a connection. I'm not sure what the best way to do this. It appears that we'd need a literal VPN connection to each and every location, which I assume would be $0.05/hr/connection... That would be extremely cost prohibitive.

I was able to get the location I'm at to connect to the VPC with no issues, however, other branches were not able to ping our EC2 server nor were they (obviously) connecting to the VPN directly.

What are your thoughts? What would be the best method for bringing our VPC to all of our branches?

  • This is a very good case for Meraki phone support. You've already paid for it :) – ewwhite Aug 11 '16 at 23:02
  • Through the nose, too! – JeremyT Aug 11 '16 at 23:05

Short of using Meraki support, I'd recommend adding static routes to the remote site Meraki firewalls using the main Meraki firewall's IP as the next hop.

enter image description here

  • Yeah, I heard back from Meraki and it looks like this might be the best way to do it... We were hoping for better support for downtime in the event that the network it was VPN'd into went down... – JeremyT Aug 12 '16 at 18:15
  • Yes, then you create direction connections to AWS. There are only two options here. – ewwhite Aug 12 '16 at 18:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.