Re: Multicast routing with VLANs

From: Bruce M Simpson (bms_at_spc.org)
Date: 04/25/05

  • Next message: Michael G. Jung: "EM driver and Intel Pro 1000 MT (A78408-008)" 
    Date: Mon, 25 Apr 2005 20:28:41 +0100
To: Eivind Hestnes <eivind@stabbursmoen.no>

    Hi,

    On Mon, Apr 25, 2005 at 07:21:22PM +0200, Eivind Hestnes wrote:
    > I'm trying to get mrouted to route multicast traffic between multiple
    > VLANs on a FreeBSD 5.4-RC3 machine. Mrouted starts as expected, and
    > according to /var/log/messages it's running - but the multicast routing
    > itself don't work. While Googling, I noticed in kern/78821
    > (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78821) that FreeBSD
    > fails to set the ALLMULTI flag on the parent device when using the
    > if_em(4). I have tried to set the ALLMULTI flag manually, but with no
    > further success - The flag won't set.
    >
    > I need the multicast routing to get Norton Ghost work properly, and
    > currently I'm a bit stuck..

    It is very very possible that ALLMULTI doesn't work right on cards which
    have hardware VLAN tagging support, though I haven't investigated it.

    For situations where the underlying hardware or card firmware cannot support
    the notion of ALLMULTI (receive all multicast datagrams promiscuously), it
    would be necessary to spoof it up by putting the hardware into promiscuous
    mode.

    NetBSD has a flag called M_PROMISC. Why is this relevant? Well, one thing
    I've noticed is that if you're running regular unicast forwarding on a box,
    and then put one of the interfaces into PROMISC mode, the danger is that
    the box will then begin trying to forward the datagrams it's just forwarded.

    We'd need a way to differentiate between traffic addressed to us and not
    addressed to us by MAC address when forwarding.

    Sadly ENOTIME at the moment for writing patches. :-(

    Regards,
    BMS
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Michael G. Jung: "EM driver and Intel Pro 1000 MT (A78408-008)"

    Relevant Pages

    • Re: resend: multiple routing table roadmap (format fix)
      ... However it makes sense to merge the multicast and unicast forwarding code as currently MROUTING is limited to a fan-out of 32 next-hops only. ... As regards getting ARP out of forwarding tables, this should have happened a long time ago... ... Surely, routing table should contain a cached pointer to an entry in L2 table, to not do double lookups. ...
      (freebsd-arch)
    • Re: resend: multiple routing table roadmap (format fix)
      ... However it makes sense to merge the multicast and unicast forwarding code as currently MROUTING is limited to a fan-out of 32 next-hops only. ... As regards getting ARP out of forwarding tables, this should have happened a long time ago... ... Surely, routing table should contain a cached pointer to an entry in L2 table, to not do double lookups. ...
      (freebsd-net)
    • Re: multicast IP addresses
      ... RRAS is the only MS product with IGMP ... communicates with other Multicast enabled routers) ... >> network that has some sort of Multicast Forwarding capabilities. ...
      (microsoft.public.windowsxp.network_web)
    • Multicast routing with VLANs
      ... I'm trying to get mrouted to route multicast traffic between multiple ... VLANs on a FreeBSD 5.4-RC3 machine. ... I have tried to set the ALLMULTI flag manually, ... I need the multicast routing to get Norton Ghost work properly, ...
      (freebsd-net)
    • Multicast Question - urgent
      ... I need a way of forwarding the SAME multicast IP address in both ... The VCON multicasting server is connected to say FE0/0 and is ... I have confgured pim dense mode on both FE interfaces with te ip igmp ...
      (comp.dcom.sys.cisco)