<?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: exclude a network from static route in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462543#M102272</link>
    <description>&lt;P&gt;Yes, the management interface is not part of the dataplane, by design. So you can not route data in/out the management port, just use it for PA controller management. If, for some reason, you need a particular PA service to use a data port instead of the management port (or need to setup special port routing for that), you can do that from Setup -&amp;gt; Services -&amp;gt; Service Route Configuration. But it doesn't work the other direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you absolutely do not want to pass management-port-bound data from your dataplane segement thru a third device, you could dedicate a dataplane port as the gateway for the management port and cross-connect it there, instead of an external switch/router.&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Eth1/1 - External WAN zone&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Eth1/2 - Internal LAN zone&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Eth1/3 - Management Net zone [192.168.0.1]&amp;nbsp; &amp;lt;-cable-&amp;gt;&amp;nbsp; Mgmt - [192.168.0.2]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 01 Feb 2022 17:31:46 GMT</pubDate>
    <dc:creator>Adrian_Jensen</dc:creator>
    <dc:date>2022-02-01T17:31:46Z</dc:date>
    <item>
      <title>exclude a network from static route</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462096#M102223</link>
      <description>&lt;P&gt;Is it possible to exclude a network from static route.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For eg&amp;nbsp; I have static route 10.20.0.0/16 to the core-switch.&lt;/P&gt;&lt;P&gt;unfortunately my management network (including PA) is 10.20.200.0/24&lt;/P&gt;&lt;P&gt;I dont want traffic to 10.20.200.0/24 going to core switch.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;just exclude that network from the route. As it's directly connected to PA, it should take that path by default.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2022 13:50:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462096#M102223</guid>
      <dc:creator>ceapen01</dc:creator>
      <dc:date>2022-01-31T13:50:12Z</dc:date>
    </item>
    <item>
      <title>Re: exclude a network from static route</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462142#M102229</link>
      <description>&lt;P&gt;In network routing, the most specific route takes precedence. So in the most aggregated form, if you have a large network block to one destination and a small subset to a different destination you have an overlapping netblock route. For instance:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.0.0/16&amp;nbsp; &amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.200.0/24&amp;nbsp; &amp;nbsp;eth1/3&amp;nbsp; &amp;nbsp;gw 192.168.3.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The 10.20.200.0/24 traffic will always take the more specific route unless the interface is down or the gateway is unreachable. Note that you actually have 3 (or more) routes that encompass the 10.20.200.0/24 above - you also need to consider the default route 0.0.0.0/0 eth1/1 gw 192.168.1.1 which will take the 10.20.200.0/24 traffic if the first 2 more specific routes are down.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The alternative is that you have to de-aggregate the routing into many netblocks to particular destinations. But again, if eth1/3 is down the 10.20.200.0/24 traffic will still take the default route.&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.0.0/17&amp;nbsp; &amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.129.0/18&amp;nbsp; &amp;nbsp;&amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.192.0/21&amp;nbsp; &amp;nbsp;&amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.200.0/24&amp;nbsp; &amp;nbsp;eth1/3&amp;nbsp; &amp;nbsp;gw 192.168.3.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.201.0/24&amp;nbsp; &amp;nbsp;&amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.202.0/23&amp;nbsp; &amp;nbsp;&amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.204.0/22&amp;nbsp; &amp;nbsp;&amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.208.0/20&amp;nbsp; &amp;nbsp;&amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.224.0/19&amp;nbsp; &amp;nbsp;&amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want to explicitly deny 10.20.200.0/24 traffic to any other destination then you need to create a blackhole route:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.0.0/16&amp;nbsp; &amp;nbsp;eth1/2&amp;nbsp; &amp;nbsp;gw 192.168.2.1&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.200.0/24&amp;nbsp; &amp;nbsp;eth1/3&amp;nbsp; &amp;nbsp;gw 192.168.3.1&amp;nbsp; &amp;nbsp;metric 10&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;10.20.200.0/24&amp;nbsp; &amp;nbsp;tunnel.999&amp;nbsp; &amp;nbsp;gw none&amp;nbsp; &amp;nbsp;metric 20&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2022 16:07:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462142#M102229</guid>
      <dc:creator>Adrian_Jensen</dc:creator>
      <dc:date>2022-01-31T16:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: exclude a network from static route</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462432#M102263</link>
      <description>&lt;P&gt;thank you&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/184804"&gt;@Adrian_Jensen&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was looking for an option to route traffic via management interface. There is no option in PA to route via MGMT interface. As a workaround I have written separate routes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I connect via globalprotect, am not able to access the Management interface IP in GUI.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Feb 2022 12:14:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462432#M102263</guid>
      <dc:creator>ceapen01</dc:creator>
      <dc:date>2022-02-01T12:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: exclude a network from static route</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462543#M102272</link>
      <description>&lt;P&gt;Yes, the management interface is not part of the dataplane, by design. So you can not route data in/out the management port, just use it for PA controller management. If, for some reason, you need a particular PA service to use a data port instead of the management port (or need to setup special port routing for that), you can do that from Setup -&amp;gt; Services -&amp;gt; Service Route Configuration. But it doesn't work the other direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you absolutely do not want to pass management-port-bound data from your dataplane segement thru a third device, you could dedicate a dataplane port as the gateway for the management port and cross-connect it there, instead of an external switch/router.&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Eth1/1 - External WAN zone&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Eth1/2 - Internal LAN zone&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Eth1/3 - Management Net zone [192.168.0.1]&amp;nbsp; &amp;lt;-cable-&amp;gt;&amp;nbsp; Mgmt - [192.168.0.2]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Feb 2022 17:31:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/exclude-a-network-from-static-route/m-p/462543#M102272</guid>
      <dc:creator>Adrian_Jensen</dc:creator>
      <dc:date>2022-02-01T17:31:46Z</dc:date>
    </item>
  </channel>
</rss>

