<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic issue on route based vpn tunnel with checkpoint VSX and AWS in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/175416#M32002</link>
    <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;I have built a VPN Site to Site tunnel between Checkpoint VSX and AWS VPN gateway, this is route based VPN&amp;nbsp; tunnel.&lt;/P&gt;&lt;P&gt;in high level steps, what i did&lt;/P&gt;&lt;P&gt;1- created virtual tunnel interface VTI - using this command -&lt;/P&gt;&lt;P&gt;vsx_provisioning_tool -o add interface vd vs1 vpn_tunnel numbered peer AWS_Peer local y.y.y.y remote &lt;SPAN&gt;x.x.x.x&lt;/SPAN&gt;&amp;nbsp;tunnel_id 10&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2- Added static route for AWS VPC CIDR and gateway is z.z.z.z&lt;/P&gt;&lt;P&gt;3- created Mesh Community in checkpoint firewall with "Blank Domain Encryption"&lt;/P&gt;&lt;P&gt;4- then Created ACL in firewall with VPN domain in the rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After completing these steps, i asked remoted end part at AWS side to initiate the traffic then&lt;/P&gt;&lt;P&gt;1- both side can be seen UP.&lt;/P&gt;&lt;P&gt;2- But traffic is is getting block on firewall with No Reason For Block.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;then one thing that i noticed is- firewall traffic is coming via VTI interface while tunnel traffic is normal outbound interface of the firewall&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any advice can i fix this issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also any step by step guide for building such route based VPN tunnel with AWS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;your support is much appreciated!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Mar 2023 14:10:22 GMT</pubDate>
    <dc:creator>kuber</dc:creator>
    <dc:date>2023-03-20T14:10:22Z</dc:date>
    <item>
      <title>issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/175416#M32002</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;I have built a VPN Site to Site tunnel between Checkpoint VSX and AWS VPN gateway, this is route based VPN&amp;nbsp; tunnel.&lt;/P&gt;&lt;P&gt;in high level steps, what i did&lt;/P&gt;&lt;P&gt;1- created virtual tunnel interface VTI - using this command -&lt;/P&gt;&lt;P&gt;vsx_provisioning_tool -o add interface vd vs1 vpn_tunnel numbered peer AWS_Peer local y.y.y.y remote &lt;SPAN&gt;x.x.x.x&lt;/SPAN&gt;&amp;nbsp;tunnel_id 10&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2- Added static route for AWS VPC CIDR and gateway is z.z.z.z&lt;/P&gt;&lt;P&gt;3- created Mesh Community in checkpoint firewall with "Blank Domain Encryption"&lt;/P&gt;&lt;P&gt;4- then Created ACL in firewall with VPN domain in the rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After completing these steps, i asked remoted end part at AWS side to initiate the traffic then&lt;/P&gt;&lt;P&gt;1- both side can be seen UP.&lt;/P&gt;&lt;P&gt;2- But traffic is is getting block on firewall with No Reason For Block.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;then one thing that i noticed is- firewall traffic is coming via VTI interface while tunnel traffic is normal outbound interface of the firewall&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any advice can i fix this issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also any step by step guide for building such route based VPN tunnel with AWS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;your support is much appreciated!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2023 14:10:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/175416#M32002</guid>
      <dc:creator>kuber</dc:creator>
      <dc:date>2023-03-20T14:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/175978#M32150</link>
      <description>&lt;P&gt;I presume you've followed the guide for setting up a VPN with Amazon VPC:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk108958" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk108958&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;Please show the full log card where the traffic is dropped (redact sensitive details).&lt;BR /&gt;Also provide version/JHF of your Check Point equipment.&lt;/P&gt;
&lt;P&gt;I suspect some additional debugging will also illuminate the situation:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk180488" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk180488&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 21:25:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/175978#M32150</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-03-23T21:25:03Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176052#M32175</link>
      <description>&lt;P&gt;How did you configure the static route via SmartConsole or CLI?&lt;/P&gt;
&lt;P&gt;That said as I recall R81 and above support VTI only with dynamic routing for VSX.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 11:15:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176052#M32175</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-03-24T11:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176262#M32254</link>
      <description>&lt;P&gt;static route conf i did via CLI via command i mentioned in my first post.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 10:53:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176262#M32254</guid>
      <dc:creator>kuber</dc:creator>
      <dc:date>2023-03-27T10:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176265#M32255</link>
      <description>&lt;P&gt;Whilst I don't see it in your post above, this approach isn't supported on VSX.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:19:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176265#M32255</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-03-27T11:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176266#M32256</link>
      <description>&lt;P&gt;Hi Chris,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in high level steps, what i did&lt;/P&gt;&lt;P&gt;1- created virtual tunnel interface VTI - using this command -&lt;/P&gt;&lt;P&gt;vsx_provisioning_tool -o add interface vd vs1 vpn_tunnel numbered peer AWS_Peer local y.y.y.y remote&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;x.x.x.x&lt;/SPAN&gt;&amp;nbsp;tunnel_id 10&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2- Added static route for AWS VPC CIDR and gateway is z.z.z.z&lt;/P&gt;&lt;P&gt;3- created Mesh Community in checkpoint firewall with "Blank Domain Encryption"&lt;/P&gt;&lt;P&gt;4- then Created ACL in firewall with VPN domain in the rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After completing these steps, i asked remoted end part at AWS side to initiate the traffic then&lt;/P&gt;&lt;P&gt;1- both side can be seen UP.&lt;/P&gt;&lt;P&gt;2- But traffic is is getting block on firewall with No Reason For Block&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:28:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176266#M32256</guid>
      <dc:creator>kuber</dc:creator>
      <dc:date>2023-03-27T11:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176267#M32257</link>
      <description>&lt;P&gt;This (step 2) doesn't show / detail the exact command used for the static route but in VSX this shouldn't be done via CLI unless it is dynamic routing.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:36:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176267#M32257</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-03-27T11:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176269#M32258</link>
      <description>&lt;P&gt;i used this command&amp;nbsp; where i replace the x and y by IP addresses.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;vsx_provisioning_tool -o add interface vd vs1 vpn_tunnel numbered peer AWS_Peer local y.y.y.y remote&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;x.x.x.x&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;tunnel_id 10&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:37:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176269#M32258</guid>
      <dc:creator>kuber</dc:creator>
      <dc:date>2023-03-27T11:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176270#M32259</link>
      <description>&lt;P&gt;That is not creating the static route but the VTI interface.&lt;/P&gt;
&lt;P&gt;Regardless as stated above dynamic routing is needed for this to be successful.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:39:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176270#M32259</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-03-27T11:39:29Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176275#M32262</link>
      <description>&lt;P&gt;yes, sorry, VTI..static route i added through smart console. where destination is VPC and gateway is what mentioned in the configuration file received from aws side&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:52:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176275#M32262</guid>
      <dc:creator>kuber</dc:creator>
      <dc:date>2023-03-27T11:52:21Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176280#M32263</link>
      <description>&lt;P&gt;Per &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk79700" target="_blank" rel="noopener"&gt;sk79700&lt;/A&gt; before R81, VTI on VSX wasn't supported.&lt;/P&gt;
&lt;P&gt;Configure &lt;STRONG&gt;Dynamic Routing&lt;/STRONG&gt; VPN through Virtual Tunnel Interface (VTI) in VSX.&lt;/P&gt;
&lt;P&gt;Source: &lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_RN/Topics-RN/Whats-New.htm" target="_blank" rel="noopener"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_RN/Topics-RN/Whats-New.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 12:10:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/176280#M32263</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-03-27T12:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/177123#M32450</link>
      <description>&lt;P&gt;this solution is not workable, we are using r81.10, VTI can be configured.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the problem is , traffic is passing from the configured VTI and getting block, not sure why not being accepted by firewall ACL since tunnel is showing up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;could anyone help here who has built only this type tunnel,&lt;/P&gt;&lt;P&gt;AWS to CP VSX gateway with routing based using VTI, blank encryption domain, and Mesh topology.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 10:55:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/177123#M32450</guid>
      <dc:creator>kuber</dc:creator>
      <dc:date>2023-04-03T10:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: issue on route based vpn tunnel with checkpoint VSX and AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/177124#M32451</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;FONT face="inherit"&gt;Yes VTI can be configured here but it needs dynamic routing (BGP) to work on VSX. &lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;FONT face="inherit"&gt;If &lt;/FONT&gt;you've&lt;FONT face="inherit"&gt;&amp;nbsp;done this (not using static routes) and the issue persists please consult with TAC for troubleshooting assistance.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 11:18:07 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/issue-on-route-based-vpn-tunnel-with-checkpoint-VSX-and-AWS/m-p/177124#M32451</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-04-03T11:18:07Z</dc:date>
    </item>
  </channel>
</rss>

