<?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: Does  anti-spoofing heed policy-based routing on R80.40, topology defined by routes? in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Does-anti-spoofing-heed-policy-based-routing-on-R80-40-topology/m-p/108085#M14533</link>
    <description>&lt;P&gt;Your assumption is correct. I would recommend manual anti-spoofing in this case.&lt;/P&gt;</description>
    <pubDate>Mon, 18 Jan 2021 11:28:01 GMT</pubDate>
    <dc:creator>_Val_</dc:creator>
    <dc:date>2021-01-18T11:28:01Z</dc:date>
    <item>
      <title>Does  anti-spoofing heed policy-based routing on R80.40, topology defined by routes?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Does-anti-spoofing-heed-policy-based-routing-on-R80-40-topology/m-p/108067#M14525</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we have a customer firewall running R80.40 using anti-spoofing with topology defined by routes - we receive some routes via OSPF.&lt;/P&gt;&lt;P&gt;Certain internal traffic must take a secondary WAN route - it is a matter of who pays for bandwidth. This is accomplished via policy-based routing - if source matches network A and destination is in network B, then use the table pointing to the secondary WAN router.&lt;/P&gt;&lt;P&gt;Other traffic to B should use the primary WAN link; its return packets will also come in via the primary WAN link.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The PBR setup works, packets get sent out as expected.&lt;/P&gt;&lt;P&gt;However, anti-spoofing denies incoming connections from B to A via the secondary WAN interface.&lt;/P&gt;&lt;P&gt;I would assume that "topology defined by routes" only heeds static and dynamic routes, but not PBR.&lt;/P&gt;&lt;P&gt;Is there a way to solve this while keeping anti-spoofing?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Bernhard&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jan 2021 09:30:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Does-anti-spoofing-heed-policy-based-routing-on-R80-40-topology/m-p/108067#M14525</guid>
      <dc:creator>Toolmaker</dc:creator>
      <dc:date>2021-01-18T09:30:34Z</dc:date>
    </item>
    <item>
      <title>Re: Does  anti-spoofing heed policy-based routing on R80.40, topology defined by routes?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Does-anti-spoofing-heed-policy-based-routing-on-R80-40-topology/m-p/108085#M14533</link>
      <description>&lt;P&gt;Your assumption is correct. I would recommend manual anti-spoofing in this case.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jan 2021 11:28:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Does-anti-spoofing-heed-policy-based-routing-on-R80-40-topology/m-p/108085#M14533</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2021-01-18T11:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: Does  anti-spoofing heed policy-based routing on R80.40, topology defined by routes?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Does-anti-spoofing-heed-policy-based-routing-on-R80-40-topology/m-p/108263#M14595</link>
      <description>&lt;P&gt;Thanks... guess I will have to forgo the comfort of routing-based anti-spoofing then.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2021 08:24:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Does-anti-spoofing-heed-policy-based-routing-on-R80-40-topology/m-p/108263#M14595</guid>
      <dc:creator>Toolmaker</dc:creator>
      <dc:date>2021-01-20T08:24:23Z</dc:date>
    </item>
  </channel>
</rss>

