<?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: How to deny or drop multicast on switch B5G124-48P2 in ExtremeSwitching (EOS)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56719#M868</link>
    <description>I would dig deeper into this request.  This is almost like asking a switch to block all broadcast traffic.  You can make sure IGMP snooping is enabled and all mcast traffic that does not have a valid connection will not be forwarded.  I am not sure how you could do an policy that would block all mcast traffic on ingress ports because there may be built in forwarders at the hardware level ???   Still seems to be a rather strange request and if it asked of me I would talk more with the client and get a deeper understanding of what he was trying to do along with equipment and networks configurations.  &lt;BR /&gt;</description>
    <pubDate>Sat, 11 Nov 2017 06:06:00 GMT</pubDate>
    <dc:creator>EtherMAN</dc:creator>
    <dc:date>2017-11-11T06:06:00Z</dc:date>
    <item>
      <title>How to deny or drop multicast on switch B5G124-48P2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56717#M866</link>
      <description>the costumer need block de multicast and only pass unicast, on switch B5G124-48P2 for the CCTV solution with GENETEC&lt;BR /&gt;</description>
      <pubDate>Sat, 11 Nov 2017 03:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56717#M866</guid>
      <dc:creator>Salvador_Gallo</dc:creator>
      <dc:date>2017-11-11T03:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to deny or drop multicast on switch B5G124-48P2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56718#M867</link>
      <description>I have never heard of blocking all multicast on a switch but I am guessing that would be done by applying a  policy that blocks the multicast addresses at the edge ports.</description>
      <pubDate>Sat, 11 Nov 2017 05:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56718#M867</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2017-11-11T05:30:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to deny or drop multicast on switch B5G124-48P2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56719#M868</link>
      <description>I would dig deeper into this request.  This is almost like asking a switch to block all broadcast traffic.  You can make sure IGMP snooping is enabled and all mcast traffic that does not have a valid connection will not be forwarded.  I am not sure how you could do an policy that would block all mcast traffic on ingress ports because there may be built in forwarders at the hardware level ???   Still seems to be a rather strange request and if it asked of me I would talk more with the client and get a deeper understanding of what he was trying to do along with equipment and networks configurations.  &lt;BR /&gt;</description>
      <pubDate>Sat, 11 Nov 2017 06:06:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56719#M868</guid>
      <dc:creator>EtherMAN</dc:creator>
      <dc:date>2017-11-11T06:06:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to deny or drop multicast on switch B5G124-48P2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56720#M869</link>
      <description>The policy would filter on the multicast IP address range.</description>
      <pubDate>Sat, 11 Nov 2017 06:06:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56720#M869</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2017-11-11T06:06:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to deny or drop multicast on switch B5G124-48P2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56721#M870</link>
      <description>Hi Salvador,&lt;BR /&gt;
&lt;BR /&gt;
to block IP multicast, you could write an ACL that drops the destination IP range 224.0.0.0/4 and allows anything else, and bind that to the switch ports.&lt;BR /&gt;
&lt;BR /&gt;
Alternatively you could write a policy that either drops the above destination IP range, or drops the destination MAC address range 01-00-5E-00-00-00/25 and apply the policy to the respective ports.&lt;BR /&gt;
&lt;BR /&gt;
Erik</description>
      <pubDate>Mon, 13 Nov 2017 21:21:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/how-to-deny-or-drop-multicast-on-switch-b5g124-48p2/m-p/56721#M870</guid>
      <dc:creator>Erik_Auerswald</dc:creator>
      <dc:date>2017-11-13T21:21:00Z</dc:date>
    </item>
  </channel>
</rss>

