<?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 Re: Azure R81.20 Cloudguard Cluster Deployment - Backend Routing Problem in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/Azure-R81-20-Cloudguard-Cluster-Deployment-Backend-Routing/m-p/185265#M126</link>
    <description>&lt;P&gt;No. Per the documentation, the 3 required routes are as follows.&lt;/P&gt;
&lt;P&gt;default_route 0.0.0.0/0&amp;nbsp;&lt;SPAN&gt;VirtualAppliance&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;172.18.0.69 (backend-lb)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;vm-01-vnet-local&amp;nbsp;172.19.0.0/24 VNetLocal&lt;/P&gt;
&lt;P&gt;vm-01-vnet-other-subnets&amp;nbsp;&lt;SPAN&gt;172.18.0.0/26&amp;nbsp;VirtualAppliance&amp;nbsp;172.18.0.69 (backend-lb)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 30 Jun 2023 07:03:35 GMT</pubDate>
    <dc:creator>Simon_Macpherso</dc:creator>
    <dc:date>2023-06-30T07:03:35Z</dc:date>
    <item>
      <title>Azure R81.20 Cloudguard Cluster Deployment - Backend Routing Problem</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Azure-R81-20-Cloudguard-Cluster-Deployment-Backend-Routing/m-p/185262#M124</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have deployed an R81.20 cloudguard cluster using the following IAC.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://github.com/CheckPointSW/CloudGuardIaaS/tree/master/terraform/azure/high-availability-existing-vnet" target="_blank" rel="nofollow noopener noreferrer"&gt;https://github.com/CheckPointSW/CloudGuardIaaS/tree/master/terraform/azure/high-availability-existin...&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I have a backend routing issue where whereby&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;I have provisioned a test VM in another VNET to test egress connectivity&lt;/LI&gt;
&lt;LI&gt;The VM VNET and FW backend VNETs have been associated with the internal routable&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;The required routes have been added to the internal routable- default route is 0.0.0.0/0 with next hop IP the&amp;nbsp;&lt;SPAN&gt;backend lb&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;VNET peering has been setup between the VM VNET and the connectivity VNET (VNET FW subnets reside in).&lt;/LI&gt;
&lt;LI&gt;Static route to internal subnet has been configured on each gateway i.e.&amp;nbsp;&lt;BR /&gt;set static-route &amp;lt;Virtual-Network-IP-address/Prefix&amp;gt; nexthop gateway address &amp;lt;eth1-router-IP-address&amp;gt; on&lt;/LI&gt;
&lt;LI&gt;Anti-spoofing has been disabled on both eth0 and eth1 interfaces&lt;/LI&gt;
&lt;LI&gt;In Smart Console, a test VM object has been created and allowed access in policy, outbound NAT has been configured translating source to frontend eth0 external private IP.&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;I can see traffic hitting the active member including the a reply. But the on the VM the ICMP requests are timing out.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[Expert@checkpoint-cloudguard-ha1:0]# tcpdump -nnnei any host 172.19.0.4 and host 1.1.1.1&lt;BR /&gt;tcpdump: verbose output suppressed, use -v or -vv for full protocol decode&lt;BR /&gt;listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes&lt;BR /&gt;06:14:29.364296 In fc:bd:67:89:19:6e ethertype IPv4 (0x0800), length 76: 172.19.0.4 &amp;gt; 1.1.1.1: ICMP echo request, id 1, seq 352, length 40&lt;BR /&gt;06:14:29.366766 Out 00:0d:3a:66:8a:a3 ethertype IPv4 (0x0800), length 76: 1.1.1.1 &amp;gt; 172.19.0.4: ICMP echo reply, id 1, seq 352, length 40&lt;BR /&gt;06:14:29.366785 Out 00:0d:3a:66:8a:a3 ethertype IPv4 (0x0800), length 76: 1.1.1.1 &amp;gt; 172.19.0.4: ICMP echo reply, id 1, seq 352, length 40&lt;BR /&gt;06:14:34.107158 In fc:bd:67:89:19:6e ethertype IPv4 (0x0800), length 76: 172.19.0.4 &amp;gt; 1.1.1.1: ICMP echo request, id 1, seq 353, length 40&lt;BR /&gt;06:14:34.109671 Out 00:0d:3a:66:8a:a3 ethertype IPv4 (0x0800), length 76: 1.1.1.1 &amp;gt; 172.19.0.4: ICMP echo reply, id 1, seq 353, length 40&lt;BR /&gt;06:14:34.109692 Out 00:0d:3a:66:8a:a3 ethertype IPv4 (0x0800), length 76: 1.1.1.1 &amp;gt; 172.19.0.4: ICMP echo reply, id 1, seq 353, length 40&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="cf0"&gt;fw monitor -w -F &amp;lt;172.19.0.4&amp;gt;,0,&amp;lt;1.1.1.1&amp;gt;,0,0 -F &amp;lt;1.1.1.1&amp;gt;,0,&amp;lt;172.19.0.4&amp;gt;,0,0&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;[vs_0][ppak_0] eth1:i[60]: 172.19.0.4 -&amp;gt; 1.1.1.1 (ICMP) len=60 id=44093&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=356&lt;BR /&gt;[vs_0][fw_2] eth1:i[60]: 172.19.0.4 -&amp;gt; 1.1.1.1 (ICMP) len=60 id=44093&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=356&lt;BR /&gt;[vs_0][fw_2] eth1:I[60]: 172.19.0.4 -&amp;gt; 1.1.1.1 (ICMP) len=60 id=44093&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=356&lt;BR /&gt;[vs_0][fw_2] eth0:o[60]: 172.19.0.4 -&amp;gt; 1.1.1.1 (ICMP) len=60 id=44093&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=356&lt;BR /&gt;[vs_0][fw_2] eth0:I[60]: 1.1.1.1 -&amp;gt; 172.19.0.4 (ICMP) len=60 id=55497&lt;BR /&gt;ICMP: type=0 code=0 echo reply id=1 seq=356&lt;BR /&gt;[vs_0][fw_2] eth1:o[60]: 1.1.1.1 -&amp;gt; 172.19.0.4 (ICMP) len=60 id=55497&lt;BR /&gt;ICMP: type=0 code=0 echo reply id=1 seq=356&lt;BR /&gt;[vs_0][fw_2] eth1:O[60]: 1.1.1.1 -&amp;gt; 172.19.0.4 (ICMP) len=60 id=55497&lt;BR /&gt;ICMP: type=0 code=0 echo reply id=1 seq=356&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 06:27:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Azure-R81-20-Cloudguard-Cluster-Deployment-Backend-Routing/m-p/185262#M124</guid>
      <dc:creator>Simon_Macpherso</dc:creator>
      <dc:date>2023-06-30T06:27:12Z</dc:date>
    </item>
    <item>
      <title>Re: Azure R81.20 Cloudguard Cluster Deployment - Backend Routing Problem</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Azure-R81-20-Cloudguard-Cluster-Deployment-Backend-Routing/m-p/185264#M125</link>
      <description>&lt;P&gt;Have you set a route in the backend network to the lowest IP address of the VNET on the Check Point FW?&lt;/P&gt;
&lt;P&gt;For example &lt;BR /&gt;Backend network&amp;nbsp;&amp;nbsp; 10.70.22.64/26&lt;BR /&gt;Gateway IP&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.70.22&lt;STRONG&gt;.65&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/STRONG&gt;for Azure internal networks.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 06:47:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Azure-R81-20-Cloudguard-Cluster-Deployment-Backend-Routing/m-p/185264#M125</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2023-06-30T06:47:56Z</dc:date>
    </item>
    <item>
      <title>Re: Azure R81.20 Cloudguard Cluster Deployment - Backend Routing Problem</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Azure-R81-20-Cloudguard-Cluster-Deployment-Backend-Routing/m-p/185265#M126</link>
      <description>&lt;P&gt;No. Per the documentation, the 3 required routes are as follows.&lt;/P&gt;
&lt;P&gt;default_route 0.0.0.0/0&amp;nbsp;&lt;SPAN&gt;VirtualAppliance&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;172.18.0.69 (backend-lb)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;vm-01-vnet-local&amp;nbsp;172.19.0.0/24 VNetLocal&lt;/P&gt;
&lt;P&gt;vm-01-vnet-other-subnets&amp;nbsp;&lt;SPAN&gt;172.18.0.0/26&amp;nbsp;VirtualAppliance&amp;nbsp;172.18.0.69 (backend-lb)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 07:03:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Azure-R81-20-Cloudguard-Cluster-Deployment-Backend-Routing/m-p/185265#M126</guid>
      <dc:creator>Simon_Macpherso</dc:creator>
      <dc:date>2023-06-30T07:03:35Z</dc:date>
    </item>
  </channel>
</rss>

