<?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: Shun Interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/shun-interface/m-p/1075354#M913802</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.  I found a static entry that should have been a class C but instead referenced a class B.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Aug 2008 11:32:39 GMT</pubDate>
    <dc:creator>rmeans</dc:creator>
    <dc:date>2008-08-29T11:32:39Z</dc:date>
    <item>
      <title>Shun Interface</title>
      <link>https://community.cisco.com/t5/network-security/shun-interface/m-p/1075352#M913800</link>
      <description>&lt;P&gt;When shunning, how is the interface decided?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show shun&lt;/P&gt;&lt;P&gt;shun (outside) 1.1.1.1 0.0.0.0 0 0 0&lt;/P&gt;&lt;P&gt;shun (inside) 2.2.2.2 0.0.0.0 0 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe both IP addresses should be shunned on the outside interface.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:37:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shun-interface/m-p/1075352#M913800</guid>
      <dc:creator>rmeans</dc:creator>
      <dc:date>2019-03-11T13:37:22Z</dc:date>
    </item>
    <item>
      <title>Re: Shun Interface</title>
      <link>https://community.cisco.com/t5/network-security/shun-interface/m-p/1075353#M913801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As per my understanding&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The decision order is as follows&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Static NAT entry&lt;/P&gt;&lt;P&gt;    All static entries are checked to see if there is an entry with the global IP as the shunned IP. If there is then the actual shunned IP would be the local IP and the interface would be the local interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. check the global addresses in the xlate and same process as above&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. If there is still no match, then a route lookup to figure out the source interface for this address and apply the shun to the interface returned by the route lookup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syed Iftekhar Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Aug 2008 20:51:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shun-interface/m-p/1075353#M913801</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2008-08-28T20:51:36Z</dc:date>
    </item>
    <item>
      <title>Re: Shun Interface</title>
      <link>https://community.cisco.com/t5/network-security/shun-interface/m-p/1075354#M913802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.  I found a static entry that should have been a class C but instead referenced a class B.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Aug 2008 11:32:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shun-interface/m-p/1075354#M913802</guid>
      <dc:creator>rmeans</dc:creator>
      <dc:date>2008-08-29T11:32:39Z</dc:date>
    </item>
  </channel>
</rss>

