<?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: Static Route is not applied in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Static-Route-is-not-applied/m-p/81616#M6327</link>
    <description>&lt;P&gt;Is the next hop for &lt;STRONG&gt;192.168.Y.X/24&lt;/STRONG&gt; a valid responding IP address located on a directly-reachable subnet/interface?&amp;nbsp; If not you can configure the route but it will never be added to the live routing table unless the next hop can be directly and successfully reached; you cannot add a route with a next hop address that is reached through some other router and have it work, the next hop must be local.&lt;/P&gt;</description>
    <pubDate>Sat, 11 Apr 2020 17:04:26 GMT</pubDate>
    <dc:creator>Timothy_Hall</dc:creator>
    <dc:date>2020-04-11T17:04:26Z</dc:date>
    <item>
      <title>Static Route is not applied</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Static-Route-is-not-applied/m-p/81536#M6325</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are experiencing an issue with a static routing in our GW &lt;STRONG&gt;R77.30&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;We have already a routing for the subnet &lt;STRONG&gt;192.168.X.X/16&lt;/STRONG&gt; to go through destination &lt;STRONG&gt;A&lt;/STRONG&gt; and we have added a new routing for the subnet &lt;STRONG&gt;192.168.Y.X/24&lt;/STRONG&gt; to go through destination &lt;STRONG&gt;B&lt;/STRONG&gt; but the new routing is never applied. All traffic is going through destination A.&lt;/P&gt;&lt;P&gt;We believe that the issue is related with the routed service.&lt;/P&gt;&lt;P&gt;Can anyone assist?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2020 09:05:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Static-Route-is-not-applied/m-p/81536#M6325</guid>
      <dc:creator>mallayiotis</dc:creator>
      <dc:date>2020-04-10T09:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Static Route is not applied</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Static-Route-is-not-applied/m-p/81583#M6326</link>
      <description>This should probably be a TAC case.&lt;BR /&gt;However, R77.30 is End of Support, so if it is a bug and it's not fixed in the last jumbo hotfix, your only recourse will be to upgrade to a supported version.</description>
      <pubDate>Sat, 11 Apr 2020 04:28:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Static-Route-is-not-applied/m-p/81583#M6326</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-04-11T04:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: Static Route is not applied</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Static-Route-is-not-applied/m-p/81616#M6327</link>
      <description>&lt;P&gt;Is the next hop for &lt;STRONG&gt;192.168.Y.X/24&lt;/STRONG&gt; a valid responding IP address located on a directly-reachable subnet/interface?&amp;nbsp; If not you can configure the route but it will never be added to the live routing table unless the next hop can be directly and successfully reached; you cannot add a route with a next hop address that is reached through some other router and have it work, the next hop must be local.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Apr 2020 17:04:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Static-Route-is-not-applied/m-p/81616#M6327</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2020-04-11T17:04:26Z</dc:date>
    </item>
  </channel>
</rss>

