- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Re: Request from AWS NLB didn't enter vpn tunnel
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Request from AWS NLB didn't enter vpn tunnel
Hi ,
We are deploying a Transit VPC architecture right now.
we tried to publish a service via AWS NLB.
NLB would transfer the request to our Gateway ,and we setup a NAT rule to translate the destination to our internal server.
But we found the gateway did translate the packet but didn't transfer to the internal gw(in transit VPC).
we tried to capture packets via tcpdump and fw monitor.
10.64.6.4 is NLB's addreess.
in tcpdump records,it seems the traffic sent out via physical interface?
in gw logs ,it didn't enter vpn tunnel but did NAT translation.
Regards
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Additional:
Running R80.20GA in AWS.
Running R80.20GA in AWS.
![](/skins/images/BFDD56B372A07FDFABDEF003EE622D96/responsive_peak/images/icon_anonymous_message.png)