Meraki Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

About Sid3

Re: AWS vMX Auto VPN up but no internet for Branch

by in Cloud Security & SD-WAN (vMX)
‎Aug 10 2021 1:52 AM
‎Aug 10 2021 1:52 AM
Thank you for your response PhilipDAth,   That's interesting, so is the only reason someone would utilize a vMX is to access resources in AWS? Just seems odd to have the "Hub" option but it wont route your "Branch" traffic out.    We were wanting to route all branch traffic via VPN out to a hub within US IP Space, but do not have branches in the US to to place a physical device to accomplish this, so we wanted to leverage AWS. Is there anyway to have all branches egress via a "Hub" in the US that you are aware of without a physical device in the US?   ... View more

AWS vMX Auto VPN up but no internet for Branch

by in Cloud Security & SD-WAN (vMX)
‎Aug 5 2021 12:36 AM
‎Aug 5 2021 12:36 AM
Testing Meraki services and have a AWS vMX and a physical MX (no devices in between). vMX is the Hub and the physical MX is the branch. Utilizing full tunneling (default route to the Hub checked) but the branch MX does not get internet access. I believe it's an AWS issue because I can ping the private IP space in AWS from the branch MX but can't ping anything on the internet. I can ping the internet from the vMX though.     vMX: VPN Status up (green) Exported Subnet is the VPC subnet from AWS 172.21.0.0/16 Can ping 8.8.8.8  Can ping branch subnet gateway 192.168.120.1 Route table shows remote subnet up (Green) 192.168.120.0/24 of Branch MX NAT traversal Auto Local Networks VPN Mode Enabled   Branch MX: VPN Status up (green) Exported Subnet is the local VLAN 192.168.120.0/24 Can't ping 8.8.8.8 Can ping VPC subnet 172.21.x.x Route table shows vMX subnet 172.21.0.0/16 NAT traversal Auto Local Networks VPN Mode Enabled   AWS configuration - followed the AWS guide: Disabled source destination check on the interface Created subnet 172.21.4.0/24 and attached to routing table Added private subnet from branch 192.168.120.0/24 to route table attached to instance and tried interface Added internet gateway of 0.0.0.0/0 to route table  Route table contains local route of 172.21.0.0/16   I'm lost and not sure what else to try. I tore down the vMX and VPC and built it from scratch following the same steps and still the same result. The Meraki rep doesn't really work with AWS. Any help would be appreciated.  ... View more
Labels:
© 2024 Cisco Systems, Inc.