<?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 Simple fw topology script in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Simple-fw-topology-script/m-p/267721#M45048</link>
    <description>&lt;P&gt;Hey boys and girls,&lt;/P&gt;
&lt;P&gt;Happy weekend!&lt;/P&gt;
&lt;P&gt;Here is super simple anti-spoofind/topology script and output from my lab.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;[Expert@CP-GW:0]#&lt;BR /&gt;[Expert@CP-GW:0]# ./cp_topology_suggestion.sh&lt;BR /&gt;Device "erspan0@NONE" does not exist.&lt;BR /&gt;Check Point Topology Recommendation (read-only)&lt;BR /&gt;Host: CP-GW&lt;BR /&gt;Date: Sun Jan 18 14:58:40 EST 2026&lt;BR /&gt;Default route: eth0 via 172.16.10.1&lt;/P&gt;
&lt;P&gt;Guiding principles used:&lt;BR /&gt;• Default-route interface =&amp;gt; usually 'External (Internet)' in topology. (Common practice) [3](&lt;A href="https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349" target="_blank"&gt;https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349&lt;/A&gt;)&lt;BR /&gt;• Internal interfaces:&lt;BR /&gt;- One directly-connected subnet only =&amp;gt; 'Network defined by interface IP and Net Mask' [2](&lt;A href="https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm&lt;/A&gt;)&lt;BR /&gt;- Multiple routed subnets behind =&amp;gt; 'Network defined by routes' (dynamic topology) [2](&lt;A href="https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653" target="_blank"&gt;https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653&lt;/A&gt;)&lt;BR /&gt;• Anti-Spoofing enforcement uses interface topology, so wrong topology can cause drops. [1](&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm&lt;/A&gt;)&lt;BR /&gt;----------------------------------------------------------------------------------------------------&lt;BR /&gt;Interface State IPv4 Role Recommended 'Leads To' option&lt;BR /&gt;----------------------------------------------------------------------------------------------------&lt;BR /&gt;----------------------------------------------------------------------------------------------------&lt;BR /&gt;Next steps (SmartConsole):&lt;BR /&gt;1) Gateway &amp;gt; Network Management &amp;gt; Interface &amp;gt; Topology &amp;gt; Modify&lt;BR /&gt;2) Apply the recommended 'Leads To' option per interface.&lt;BR /&gt;3) Ensure Anti-Spoofing is aligned, because it is enforced based on interface topology. [1](&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Reminder:&lt;BR /&gt;- 'Network defined by routes' dynamically calculates topology behind the interface (reduces manual updates). [2](&lt;A href="https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653" target="_blank"&gt;https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653&lt;/A&gt;)&lt;BR /&gt;- External is typically the interface used to reach the Internet (default route). [3](&lt;A href="https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349" target="_blank"&gt;https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349&lt;/A&gt;)&lt;BR /&gt;[Expert@CP-GW:0]#&lt;/P&gt;</description>
    <pubDate>Sun, 18 Jan 2026 20:02:42 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2026-01-18T20:02:42Z</dc:date>
    <item>
      <title>Simple fw topology script</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Simple-fw-topology-script/m-p/267721#M45048</link>
      <description>&lt;P&gt;Hey boys and girls,&lt;/P&gt;
&lt;P&gt;Happy weekend!&lt;/P&gt;
&lt;P&gt;Here is super simple anti-spoofind/topology script and output from my lab.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;[Expert@CP-GW:0]#&lt;BR /&gt;[Expert@CP-GW:0]# ./cp_topology_suggestion.sh&lt;BR /&gt;Device "erspan0@NONE" does not exist.&lt;BR /&gt;Check Point Topology Recommendation (read-only)&lt;BR /&gt;Host: CP-GW&lt;BR /&gt;Date: Sun Jan 18 14:58:40 EST 2026&lt;BR /&gt;Default route: eth0 via 172.16.10.1&lt;/P&gt;
&lt;P&gt;Guiding principles used:&lt;BR /&gt;• Default-route interface =&amp;gt; usually 'External (Internet)' in topology. (Common practice) [3](&lt;A href="https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349" target="_blank"&gt;https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349&lt;/A&gt;)&lt;BR /&gt;• Internal interfaces:&lt;BR /&gt;- One directly-connected subnet only =&amp;gt; 'Network defined by interface IP and Net Mask' [2](&lt;A href="https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm&lt;/A&gt;)&lt;BR /&gt;- Multiple routed subnets behind =&amp;gt; 'Network defined by routes' (dynamic topology) [2](&lt;A href="https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653" target="_blank"&gt;https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653&lt;/A&gt;)&lt;BR /&gt;• Anti-Spoofing enforcement uses interface topology, so wrong topology can cause drops. [1](&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm&lt;/A&gt;)&lt;BR /&gt;----------------------------------------------------------------------------------------------------&lt;BR /&gt;Interface State IPv4 Role Recommended 'Leads To' option&lt;BR /&gt;----------------------------------------------------------------------------------------------------&lt;BR /&gt;----------------------------------------------------------------------------------------------------&lt;BR /&gt;Next steps (SmartConsole):&lt;BR /&gt;1) Gateway &amp;gt; Network Management &amp;gt; Interface &amp;gt; Topology &amp;gt; Modify&lt;BR /&gt;2) Apply the recommended 'Leads To' option per interface.&lt;BR /&gt;3) Ensure Anti-Spoofing is aligned, because it is enforced based on interface topology. [1](&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/Preventing-IP-Spoofing.htm&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Reminder:&lt;BR /&gt;- 'Network defined by routes' dynamically calculates topology behind the interface (reduces manual updates). [2](&lt;A href="https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653" target="_blank"&gt;https://sc1.checkpoint.com/documents/R80.30/SmartConsole_OLH/EN/ZvkmnUK_XluBBIIAw1mF3A2.htm)[4](https://community.checkpoint.com/t5/Security-Gateways/Network-Defined-by-Routes-Anti-Spoofing/td-p/154653&lt;/A&gt;)&lt;BR /&gt;- External is typically the interface used to reach the Internet (default route). [3](&lt;A href="https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349" target="_blank"&gt;https://community.checkpoint.com/t5/General-Topics/Gateway-Topolgy-Internal-External-or-DMZ/td-p/178349&lt;/A&gt;)&lt;BR /&gt;[Expert@CP-GW:0]#&lt;/P&gt;</description>
      <pubDate>Sun, 18 Jan 2026 20:02:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Simple-fw-topology-script/m-p/267721#M45048</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2026-01-18T20:02:42Z</dc:date>
    </item>
  </channel>
</rss>

