Downside, none. Unless you're doing something with multicast over an SM link, like maybe OSPF.

A few years ago, we had a bunch of customer routers (might have been Linksys or Netgear) that were spewing out multicast. And a large L2 segment of the network (which is now broken up) slowed to a crawl. I think it was IGMP. And SM isolation wouldn't have solved the problem for the entire network. Multicast filter on all of the Canopy SMs reduced the violence. But I think this was around the same time we had some Trango 5580's go stupid. They appeared to be looping traffic, but not all types, just broadcast and multicast. It was really weird. But now all that Trango stuff is gone, every last one.

On 11/19/2014 10:09 AM, Ty Featherling via Af wrote:
Is there any downside to dropping all multicast from the customers? My brain says no but my other end says don't try it without confirming.

-Ty

On Tue, Nov 18, 2014 at 5:36 PM, George Skorup (Cyber Broadcasting) via Af <[email protected] <mailto:[email protected]>> wrote:

    We do only bridge mode and DHCP to the customer's equipment. But I
    do check the PPPoE filter because it lets me easily see when a
    customer's router is configured for PPPoE (Stats > Filter). I also
    use the filters for BootP server, SNMP, SMB and multicast. This is
    some of the best stuff about Canopy. So I would prefer the ePMP to
    work like Canopy, for the most part anyway.


    On 11/18/2014 3:13 PM, Matt via Af wrote:

            I am Dan Sullivan and I am the software manager for ePMP
            at Cambium.

            Why do you want to filter PPPoE?  Can you explain the use
            case more for me.

            When our SM is set up as a PPPoE client and is talking to
            a PPPoE server, it will only accept traffic from the PPPoE
            server over the wireless interface.  With this in mind,
            why do you need a PPPoE filter for the wireless interface?

            One other item, when NAT mode is enabled we can set up a
            L2 filter for a source MAC and EtherType as indicated
            below, but only the source MAC filter will work.  There is
            a warning message that indicates this when in NAT mode.

        I think the desired affect is the same as:

        On Canopy 450 SM
        "Config / Protocol Filtering"
        "Packet Filter Configuration"

        Packet Direction: Filter Direction Upstream Checked
        Packet Filter Types: Check Everything BUT "PPPoE"

        This way the customer router/PC they plug into the ethernet
        port on
        the SM can only successfully send PPPoE traffic onto our network.




Reply via email to