<?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 S/K-Series Policy to identify IPv6 Router Advertisements in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/using-s-k-series-policy-to-identify-ipv6-router-advertisements/m-p/46918#M426</link>
    <description>Article ID: 14443 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series&lt;BR /&gt;
K-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
Identify IPv6 Router Advertisements on user ports, for the purpose of dropping what amounts to "rogue" IPv6 traffic that can either directly misroute IPv6 traffic or cause IPv6/IPv4 users to try to communicate using IPv6 when no actual IPv6 connectivity exists. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Here is a sample configuration which uses Policy to identify and drop IPv6 RA traffic ingressing the configured user port(s):set policy profile 1 name IPv6-RA-drop&lt;BR /&gt;
    [profile to drop incoming IPv6 Router Advertisements]&lt;BR /&gt;
set policy rule admin-profile port ge.1.1 mask 16 port-string ge.1.1 admin-pid 1&lt;BR /&gt;
    [assign the profile to this port]&lt;BR /&gt;
set policy rule 1 icmp6type 134.0 mask 16 drop syslog enable&lt;BR /&gt;
    [cause the profile to drop ingress RAs]&lt;BR /&gt;
set policy autoclear interval 1 ports ge.1.1&lt;BR /&gt;
    [force a max of one syslog message per second for this port]&lt;BR /&gt;
set policy syslog extended-format enable every-time enable&lt;BR /&gt;
    [allow detailed syslogging for every rule hit]The intent of the continued syslogging is to allow the network manager to identify any false router nodes and resolve them (via manual intervention), on an ongoing basis.&lt;BR /&gt;
&lt;BR /&gt;
The Policy supported on other Enterasys products can use ethertype 0x86dd (native IPv6; &lt;A href="http://bit.ly/18PLq6b" target="_blank" rel="nofollow noreferrer noopener"&gt;12627&lt;/A&gt;) or ipproto 41 (IPv6 encapsulated into IPv4) to identify IPv6 in general, but do not have the granularity to determine the &lt;I&gt;type&lt;/I&gt; of IPv6 packet.&lt;BR /&gt;
Also see this &lt;A href="https://www.youtube.com/watch?v=U1Br1seJ1s8&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n&amp;amp;#38;index=24" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which explains how to drop all IPv6 packets on the S/N/K-Series.</description>
    <pubDate>Tue, 10 Dec 2013 04:37:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-10T04:37:00Z</dc:date>
    <item>
      <title>Using S/K-Series Policy to identify IPv6 Router Advertisements</title>
      <link>https://community.extremenetworks.com/t5/faqs/using-s-k-series-policy-to-identify-ipv6-router-advertisements/m-p/46918#M426</link>
      <description>Article ID: 14443 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series&lt;BR /&gt;
K-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
Identify IPv6 Router Advertisements on user ports, for the purpose of dropping what amounts to "rogue" IPv6 traffic that can either directly misroute IPv6 traffic or cause IPv6/IPv4 users to try to communicate using IPv6 when no actual IPv6 connectivity exists. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Here is a sample configuration which uses Policy to identify and drop IPv6 RA traffic ingressing the configured user port(s):set policy profile 1 name IPv6-RA-drop&lt;BR /&gt;
    [profile to drop incoming IPv6 Router Advertisements]&lt;BR /&gt;
set policy rule admin-profile port ge.1.1 mask 16 port-string ge.1.1 admin-pid 1&lt;BR /&gt;
    [assign the profile to this port]&lt;BR /&gt;
set policy rule 1 icmp6type 134.0 mask 16 drop syslog enable&lt;BR /&gt;
    [cause the profile to drop ingress RAs]&lt;BR /&gt;
set policy autoclear interval 1 ports ge.1.1&lt;BR /&gt;
    [force a max of one syslog message per second for this port]&lt;BR /&gt;
set policy syslog extended-format enable every-time enable&lt;BR /&gt;
    [allow detailed syslogging for every rule hit]The intent of the continued syslogging is to allow the network manager to identify any false router nodes and resolve them (via manual intervention), on an ongoing basis.&lt;BR /&gt;
&lt;BR /&gt;
The Policy supported on other Enterasys products can use ethertype 0x86dd (native IPv6; &lt;A href="http://bit.ly/18PLq6b" target="_blank" rel="nofollow noreferrer noopener"&gt;12627&lt;/A&gt;) or ipproto 41 (IPv6 encapsulated into IPv4) to identify IPv6 in general, but do not have the granularity to determine the &lt;I&gt;type&lt;/I&gt; of IPv6 packet.&lt;BR /&gt;
Also see this &lt;A href="https://www.youtube.com/watch?v=U1Br1seJ1s8&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n&amp;amp;#38;index=24" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which explains how to drop all IPv6 packets on the S/N/K-Series.</description>
      <pubDate>Tue, 10 Dec 2013 04:37:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/using-s-k-series-policy-to-identify-ipv6-router-advertisements/m-p/46918#M426</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-10T04:37:00Z</dc:date>
    </item>
  </channel>
</rss>

