- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Non Meraki VPN tunnel up but I can't ping the DNS server
Hi Everyone,
I have established a site to site vpn between MX 68CW and AWS. the tunnel is up on AWS and Meraki Dashboard. The problem is that I can't ping my DNS server which is on AWS. It looks like something is missing . The routing is enabled on AWS and Meraki . I suspect something to add on security group but I am not sure.
My local Lan is 10.200.45.0/24 and the vpc is CIDR is 172.31.0.0/16. Could you help me please , I am kind new .
- Labels:
-
3rd Party VPN
-
ACLs
-
AWS
-
Firewall
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Make sure you don't have any ACLs in Azure that are blocking ICMP (this is most likely).
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've already checked that , nothing blocked my ICMP packets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How about routes?
Have you tried disabling your server's local firewall?
Otherwise, open a support case.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
By the way check this.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I did use this link to setup my site to site vpn. the tunnel is up but still the ping is unseccessfull.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have checked the ACL everything looks fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Don't forget that you can restrict both ACLs and the security group. If you don't have an ACL, review the security group, otherwise open a support case as suggested previously.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More specifically on inbound rules.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok so it's better to open support case with AWS because I do not think it's meraki issue ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You have to check with Cisco TAC and Your AWS support Person jointly.
Surely, his issue with AWS side.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And Which Firmware version are you using in MX Meraki ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Current version: MX 18.107.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Nabil,
Have a look at this tshoot guide from Meraki and AWS . There has been some known road blocks with IKEv1 with "one unique security association per Tunnel".
https://docs.aws.amazon.com/vpn/latest/s2svpn/your-cgw.html
Cheers,
Ivan Jukić
Cheers,
Ivan Jukić,
Meraki APJC
If you found this post helpful, please give it kudos. If it solved your problem, click "accept as solution" so that others can benefit from it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The #1 issue I run into when investigating these is - Windows Firewall. Try disabling it temporarily.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's disabled
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, Nabil
Did you enable the LAN under Addressing & Vlans? Also check if under DHCP to what your DNS nameservers are set to and what IP's were assigned for Customs nameservers.
Thanks.
