<?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 R81.20 VSX VTI routing in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R81-20-VSX-VTI-routing/m-p/206351#M38983</link>
    <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;This my first post so apologies if I don't follow the expected etticate while I get used to the forum.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway the&amp;nbsp; issue&amp;nbsp; I have created a routed VPN to Azure for our orgs new&amp;nbsp; Remote client VPN . As I can see the VTI tunnels are working . However , outbound traffic routes to the wrp external interface . The logs stat traffic is encrypted by the community. Also traffic does get to the Azure infrastructure.&amp;nbsp; The reason for my post is the logs for inbound traffic from the Azure side show the traffic hitting the VTI tunnel .&lt;/P&gt;&lt;P&gt;Is this normal behaviour ?&lt;/P&gt;</description>
    <pubDate>Fri, 16 Feb 2024 21:05:04 GMT</pubDate>
    <dc:creator>Ninjawalsh</dc:creator>
    <dc:date>2024-02-16T21:05:04Z</dc:date>
    <item>
      <title>R81.20 VSX VTI routing</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R81-20-VSX-VTI-routing/m-p/206351#M38983</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;This my first post so apologies if I don't follow the expected etticate while I get used to the forum.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway the&amp;nbsp; issue&amp;nbsp; I have created a routed VPN to Azure for our orgs new&amp;nbsp; Remote client VPN . As I can see the VTI tunnels are working . However , outbound traffic routes to the wrp external interface . The logs stat traffic is encrypted by the community. Also traffic does get to the Azure infrastructure.&amp;nbsp; The reason for my post is the logs for inbound traffic from the Azure side show the traffic hitting the VTI tunnel .&lt;/P&gt;&lt;P&gt;Is this normal behaviour ?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 21:05:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R81-20-VSX-VTI-routing/m-p/206351#M38983</guid>
      <dc:creator>Ninjawalsh</dc:creator>
      <dc:date>2024-02-16T21:05:04Z</dc:date>
    </item>
    <item>
      <title>Re: R81.20 VSX VTI routing</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R81-20-VSX-VTI-routing/m-p/206390#M38993</link>
      <description>&lt;P&gt;Let me take a "stab" at it, as the saying goes. So, Im fairly experienced with tunnels to Azure, I had helped lots of customers with it, plus had done extensive testing in the lab as well.&lt;/P&gt;
&lt;P&gt;So, I have some question for ya.&lt;/P&gt;
&lt;P&gt;1) is this numbered or unnumbered VTI?&lt;/P&gt;
&lt;P&gt;2) Regardless what answer is to question1 (though it is somewhat important), can you please share how the route is configured for the subnet on Azure side? (please blur out any sensitive info)&lt;/P&gt;
&lt;P&gt;3) As far as topology in smart console, this is SUPER IMPORTANT and it has to be correct...make sure anti-spoofing is disabled and actual remote peer matched EXACTLY how its configured in smart console interoperable object.&lt;/P&gt;
&lt;P&gt;4) Is remote peer external IP added to be exmpred for anti spoof checks on external interface? Because if not, it should be&lt;/P&gt;
&lt;P&gt;5) Do you have a route to external IP of the peer with default gateway of your upstream router IP?&lt;/P&gt;
&lt;P&gt;Thats all I can think of for now.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 19 Feb 2024 02:11:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R81-20-VSX-VTI-routing/m-p/206390#M38993</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-02-19T02:11:19Z</dc:date>
    </item>
  </channel>
</rss>

