<?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: VSX anti-spoofing DETECT behavior question in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10492#M639</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Probably silly question but I assume that pushed both topology and policy after you set spoofing to detect mode? I'm still confused how it failed to work correctly when you have tooiloto set to automatic. Sounds really strange.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Mar 2019 21:08:39 GMT</pubDate>
    <dc:creator>Kaspars_Zibarts</dc:creator>
    <dc:date>2019-03-07T21:08:39Z</dc:date>
    <item>
      <title>VSX anti-spoofing DETECT behavior question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10489#M636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everyone!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm wondering, is there someone, who already face the following issue with r77.30 VSX:&lt;/P&gt;&lt;P&gt;I set an interface anti-spoofing of a VS to DETECT, because I had many drops and have no time to set all the routings.&lt;/P&gt;&lt;P&gt;However the traffic is still not went through the firewall as it should be, but in the tracker, I saw the detect events.&lt;/P&gt;&lt;P&gt;So I had to completely turned off the ants-spoofing protection on that interface, then all is good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What do you think, this is a bug, an undocumented feature or just I missed something in the official documentation?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx for the answers!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Balint&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Mar 2019 11:33:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10489#M636</guid>
      <dc:creator>Balint_Elteto</dc:creator>
      <dc:date>2019-03-06T11:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: VSX anti-spoofing DETECT behavior question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10490#M637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is it possible that traffic passed multiple VSes and/or interfaces so it was dropped somewhere else by spoofing? And when you disabled spoofing completely it covered missing interfaces?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In any case - instead of trying to fix this detect issue I would rather spend time to fix routing and spoofing &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://community.checkpoint.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You know that you can use automatic spoofing calculation based on existing routing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" src="https://community.checkpoint.com/legacyfs/online/checkpoint/79837_pastedImage_2.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Mar 2019 14:44:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10490#M637</guid>
      <dc:creator>Kaspars_Zibarts</dc:creator>
      <dc:date>2019-03-06T14:44:35Z</dc:date>
    </item>
    <item>
      <title>Re: VSX anti-spoofing DETECT behavior question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10491#M638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the answer!&lt;/P&gt;&lt;P&gt;No other vs/interface involved. Also I see the traffic with DETECT action in the tracker.&lt;/P&gt;&lt;P&gt;Just not arrives to the destination.&lt;/P&gt;&lt;P&gt;Of course, my plan is to correct the routing for sure. But it was a strange behavior which surprised me and cause some uncomfortable hours.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using the auto cal on every VS with prevent settings. But there were lot of routes missing and the "set to detect" was the fastest solution to my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;btw, the interface is a wrp to a virtual switch. Maybe that had something do with this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2019 12:11:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10491#M638</guid>
      <dc:creator>Balint_Elteto</dc:creator>
      <dc:date>2019-03-07T12:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: VSX anti-spoofing DETECT behavior question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10492#M639</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Probably silly question but I assume that pushed both topology and policy after you set spoofing to detect mode? I'm still confused how it failed to work correctly when you have tooiloto set to automatic. Sounds really strange.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2019 21:08:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10492#M639</guid>
      <dc:creator>Kaspars_Zibarts</dc:creator>
      <dc:date>2019-03-07T21:08:39Z</dc:date>
    </item>
    <item>
      <title>Re: VSX anti-spoofing DETECT behavior question</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10493#M640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://community.checkpoint.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&amp;nbsp; I pushed the policy.&lt;/P&gt;&lt;P&gt;Anyway, when I'll have more time to play, I'll set up a test VS on this vsx cluster and do some test/troubleshoot.&lt;/P&gt;&lt;P&gt;Maybe this was some mysterious event, which will never come up again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx for your notes&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Mar 2019 07:17:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-anti-spoofing-DETECT-behavior-question/m-p/10493#M640</guid>
      <dc:creator>Balint_Elteto</dc:creator>
      <dc:date>2019-03-08T07:17:16Z</dc:date>
    </item>
  </channel>
</rss>

