- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- VPN AWS - rules not matching
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VPN AWS - rules not matching
Hello,
I created a VPN to from onprem fw cluster to AWS gateway exactly like desribed in sk100726.
The VPN is up and I see tunneltest packets but the traffic does not match the outgoing rule with the directional match, runs to cleanup and is dropped. Selectig VPN any leads to an "accept" but not to encrypt.
Customer already have another working vpn to aws - actually no idea where to debug the rule match.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And if it hates you to read the doc (which I would not blame you for lol), then make sure vpn column is as below, 3 entries:
internal; clear - vpn communit
vpn community - internal clear
vpn community - vpn community
Push policy, test.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thats why I put my other reply, since I know most of us hate reading documentation, though my doc was short lol. Anyway, if you read it carefully, you would have seen I had in there EXACTLY what I posted after 🙂
Glad its working!
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you send the screenshot of the rule itself?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thats why it fails. Check out my post below on what rule should look like, its in the attached doc.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And if it hates you to read the doc (which I would not blame you for lol), then make sure vpn column is as below, 3 entries:
internal; clear - vpn communit
vpn community - internal clear
vpn community - vpn community
Push policy, test.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi - your doc helped (peer name in tunnel interface was same as interopdevice but with 1 capital letters) but this should have nothing to do with the rule I posted...I had all the 3 relevant rules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thats why I put my other reply, since I know most of us hate reading documentation, though my doc was short lol. Anyway, if you read it carefully, you would have seen I had in there EXACTLY what I posted after 🙂
Glad its working!
Andy
