<?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: ACL, how to invert match condition in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-how-to-invert-match-condition/m-p/51279#M13934</link>
    <description>Create Date: Jun 19 2012  5:13AM&lt;BR /&gt;
&lt;BR /&gt;
I wouldn't claim to be an expert but wouldn't you just reverse the logic and permit traffic from the addresses?&lt;BR /&gt;
&lt;BR /&gt;
As far as I am aware, while the default action for an *entry* is to permit, the default action for an ACL is to deny that which hasn't been matched.  (from David_Rickard)</description>
    <pubDate>Wed, 08 Jan 2014 05:53:00 GMT</pubDate>
    <dc:creator>EtherNation_Use</dc:creator>
    <dc:date>2014-01-08T05:53:00Z</dc:date>
    <item>
      <title>ACL, how to invert match condition</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-how-to-invert-match-condition/m-p/51278#M13933</link>
      <description>Create Date: Jun 19 2012  4:48AM&lt;BR /&gt;
&lt;BR /&gt;
Is it possible to invert a match condition with an ACL?&lt;BR /&gt;
 E.g. I want to deny packets which are &lt;B&gt;not&lt;/B&gt; coming from a specific IP address:&lt;BR /&gt;
 &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;  entry denyExample {&lt;BR /&gt;     if {&lt;BR /&gt;       source-address NOT 1.2.3.4/32 ;&lt;BR /&gt;       more match conditions ;&lt;BR /&gt;     } then {&lt;BR /&gt;       deny ;&lt;BR /&gt;     }&lt;BR /&gt;   }&lt;BR /&gt; &lt;/PRE&gt;&lt;/DIV&gt;Is this missing in the XOS software, or is this a deficit with the hardware?&lt;BR /&gt;
&lt;BR /&gt;
  (from Hans-Werner_Paulsen )</description>
      <pubDate>Wed, 08 Jan 2014 05:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-how-to-invert-match-condition/m-p/51278#M13933</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T05:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: ACL, how to invert match condition</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-how-to-invert-match-condition/m-p/51279#M13934</link>
      <description>Create Date: Jun 19 2012  5:13AM&lt;BR /&gt;
&lt;BR /&gt;
I wouldn't claim to be an expert but wouldn't you just reverse the logic and permit traffic from the addresses?&lt;BR /&gt;
&lt;BR /&gt;
As far as I am aware, while the default action for an *entry* is to permit, the default action for an ACL is to deny that which hasn't been matched.  (from David_Rickard)</description>
      <pubDate>Wed, 08 Jan 2014 05:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-how-to-invert-match-condition/m-p/51279#M13934</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T05:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: ACL, how to invert match condition</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-how-to-invert-match-condition/m-p/51280#M13935</link>
      <description>Create Date: Jun 19 2012  5:46AM&lt;BR /&gt;
&lt;BR /&gt;
If there is only ONE match condition, and ONE rule in the policy file, then one can simply reverse the logic. If you have more conditions this will not work.&lt;BR /&gt;
&lt;BR /&gt;
  (from Hans-Werner_Paulsen)</description>
      <pubDate>Wed, 08 Jan 2014 05:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/acl-how-to-invert-match-condition/m-p/51280#M13935</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T05:53:00Z</dc:date>
    </item>
  </channel>
</rss>

