<?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 Using Policy to Filter IPv6 Traffic on a SecureStack in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/using-policy-to-filter-ipv6-traffic-on-a-securestack/m-p/44985#M283</link>
    <description>Article ID: 12627 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, firmware 1.01.01.0039 and higher&lt;BR /&gt;
SecureStack C2, firmware 5.01.01.0039 and higher&lt;BR /&gt;
SecureStack B3, firmware 1.01.01.0039 and higher&lt;BR /&gt;
SecureStack B2, firmware 4.01.01.0039 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
How to detect and drop incoming IP Version 6 traffic, using Policy. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Here is a sample policy configuration which will accomplish this task, by targeting traffic of ethertype 0x86DD: &lt;BR /&gt;
set policy profile 1 name "Drop IPv6"&lt;BR /&gt;
set policy rule 1 ether 0x86DD drop&lt;BR /&gt;
set policy port *.*.* 1Note that the last command will spawn one policy assignment command &lt;I&gt;per port&lt;/I&gt;. This is by design. &lt;BR /&gt;
&lt;BR /&gt;
Minimal firmware versions to support ethertype classification rules are outlined in &lt;A href="http://bit.ly/1h3G4WY" target="_blank" rel="nofollow noreferrer noopener"&gt;5821&lt;/A&gt;.&lt;BR /&gt;
The B3 and B2 support Policy only after application of policy licensing, as explained in &lt;A href="http://bit.ly/Ig6wNS" target="_blank" rel="nofollow noreferrer noopener"&gt;5781&lt;/A&gt;.</description>
    <pubDate>Tue, 10 Dec 2013 04:28:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-10T04:28:00Z</dc:date>
    <item>
      <title>Using Policy to Filter IPv6 Traffic on a SecureStack</title>
      <link>https://community.extremenetworks.com/t5/faqs/using-policy-to-filter-ipv6-traffic-on-a-securestack/m-p/44985#M283</link>
      <description>Article ID: 12627 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, firmware 1.01.01.0039 and higher&lt;BR /&gt;
SecureStack C2, firmware 5.01.01.0039 and higher&lt;BR /&gt;
SecureStack B3, firmware 1.01.01.0039 and higher&lt;BR /&gt;
SecureStack B2, firmware 4.01.01.0039 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
How to detect and drop incoming IP Version 6 traffic, using Policy. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Here is a sample policy configuration which will accomplish this task, by targeting traffic of ethertype 0x86DD: &lt;BR /&gt;
set policy profile 1 name "Drop IPv6"&lt;BR /&gt;
set policy rule 1 ether 0x86DD drop&lt;BR /&gt;
set policy port *.*.* 1Note that the last command will spawn one policy assignment command &lt;I&gt;per port&lt;/I&gt;. This is by design. &lt;BR /&gt;
&lt;BR /&gt;
Minimal firmware versions to support ethertype classification rules are outlined in &lt;A href="http://bit.ly/1h3G4WY" target="_blank" rel="nofollow noreferrer noopener"&gt;5821&lt;/A&gt;.&lt;BR /&gt;
The B3 and B2 support Policy only after application of policy licensing, as explained in &lt;A href="http://bit.ly/Ig6wNS" target="_blank" rel="nofollow noreferrer noopener"&gt;5781&lt;/A&gt;.</description>
      <pubDate>Tue, 10 Dec 2013 04:28:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/using-policy-to-filter-ipv6-traffic-on-a-securestack/m-p/44985#M283</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-10T04:28:00Z</dc:date>
    </item>
  </channel>
</rss>

