<?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: SOLVED: Disappearing packets / Incoming S2S VPN (Harmony SASE) in Spark Firewall (SMB)</title>
    <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217780#M10814</link>
    <description>&lt;P&gt;Lesson learned: When you use a a bridged interface (br0) in my case, you must not tcpdump on that interface but on the interface (in my case LAN4) which will receive the traffic. The packet went out.&lt;/P&gt;&lt;P&gt;Essential: do use "fw monitor -F", the you see all packets. Furthermore, the packet did not disappear but was becoming accelerated on the outgoing interface.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Jun 2024 14:01:28 GMT</pubDate>
    <dc:creator>Masek</dc:creator>
    <dc:date>2024-06-17T14:01:28Z</dc:date>
    <item>
      <title>SOLVED: Disappearing packets / Incoming S2S VPN (Harmony SASE)</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217684#M10796</link>
      <description>&lt;P&gt;I have a centrally managed Check Point Spark 1550. Central Management is R81.20 Take 65, the 1550 uses R81.10.10.&lt;/P&gt;&lt;P&gt;For using Harmony SASE I setup a S2S VPN following this guide: &lt;A href="https://support.perimeter81.com/docs/configuring-perimeter-site-to-site-with-check-point-firewall-using-the-check-point-smart-console" target="_self"&gt;https://support.perimeter81.com/docs/configuring-perimeter-site-to-site-with-check-point-firewall-using-the-check-point-smart-console&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;This generally works, but sometimes incoming packets just disappear.&lt;/P&gt;&lt;P&gt;In "fw monitor" it looks like this:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i9 (IP Options Strip (in))[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i10 (vpn multik forward in)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i11 (vpn decrypt)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i12 (l2tp inbound)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i13 (Stateless verifications (in))[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i14 (fw multik misc proto forwarding)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i15 (vpn tagging inbound)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i16 (vpn decrypt verify)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:i17 (fw VM inbound )[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:I18 (vpn policy inbound)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:I19 (vpn before offload)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[vs_0][fw_1] WAN2:I20 (fw offload inbound)[44]: 10.2.3.254 -&amp;gt; 10.0.1.124 (TCP) len=60 id=40353TCP: 40914 -&amp;gt; 80 .S.... seq=d8f1a09d ack=00000000&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;After that, no more is seen from this packet. I checked if it was NATed, but it is just gone. I also checked if it was going through anyway, but it didn't make it to the outgoing interface.&lt;/P&gt;&lt;P&gt;According to the log the connection has been accepted.&lt;/P&gt;&lt;P&gt;This only affects packets that come from a service within Harmony SASE (DNS, Published aplication) which all use the 10.2.3.254 address. Packets from clients connected via Harmony SASE are not affected.&lt;/P&gt;&lt;P&gt;I have to confess, I am a bit baffled.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 13:59:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217684#M10796</guid>
      <dc:creator>Masek</dc:creator>
      <dc:date>2024-06-17T13:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Disappearing packets / Incoming S2S VPN (Harmony SASE)</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217747#M10800</link>
      <description>&lt;P&gt;I think I found it. Now I only need to find out what it means:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;@;1756498;[cpu_2];[fw4_2];fw_log_drop_ex: Packet proto=6 10.2.3.254:47320 -&amp;gt; 10.0.1.124:80 dropped by fwmultik_process_f2p_cookie_inner Reason: fwmultik_f2p_cookie_outbound_and_routing failed;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 11:57:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217747#M10800</guid>
      <dc:creator>Masek</dc:creator>
      <dc:date>2024-06-17T11:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Disappearing packets / Incoming S2S VPN (Harmony SASE)</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217750#M10802</link>
      <description>&lt;P&gt;Bad news, only a fraction of the "lost packets" are visible via "fw ctl zdebug + drop"&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 12:19:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217750#M10802</guid>
      <dc:creator>Masek</dc:creator>
      <dc:date>2024-06-17T12:19:02Z</dc:date>
    </item>
    <item>
      <title>Re: Disappearing packets / Incoming S2S VPN (Harmony SASE)</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217757#M10803</link>
      <description>&lt;P&gt;See if below helps.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk167953" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk167953&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/dropped-by-fwmultik-process-f2p-cookie-inner-Reason-PSL-Drop/td-p/179095" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/dropped-by-fwmultik-process-f2p-cookie-inner-Reason-PSL-Drop/td-p/179095&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 12:56:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217757#M10803</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-06-17T12:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: SOLVED: Disappearing packets / Incoming S2S VPN (Harmony SASE)</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217780#M10814</link>
      <description>&lt;P&gt;Lesson learned: When you use a a bridged interface (br0) in my case, you must not tcpdump on that interface but on the interface (in my case LAN4) which will receive the traffic. The packet went out.&lt;/P&gt;&lt;P&gt;Essential: do use "fw monitor -F", the you see all packets. Furthermore, the packet did not disappear but was becoming accelerated on the outgoing interface.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 14:01:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217780#M10814</guid>
      <dc:creator>Masek</dc:creator>
      <dc:date>2024-06-17T14:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: SOLVED: Disappearing packets / Incoming S2S VPN (Harmony SASE)</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217781#M10815</link>
      <description>&lt;P&gt;Good job!&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 14:03:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/SOLVED-Disappearing-packets-Incoming-S2S-VPN-Harmony-SASE/m-p/217781#M10815</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-06-17T14:03:27Z</dc:date>
    </item>
  </channel>
</rss>

