From owner-freebsd-multimedia  Wed Feb 28 17:54:10 1996
Return-Path: owner-multimedia
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA06789
          for multimedia-outgoing; Wed, 28 Feb 1996 17:54:10 -0800 (PST)
Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA06784
          for <multimedia@freebsd.org>; Wed, 28 Feb 1996 17:54:08 -0800 (PST)
Received: (from tinguely@localhost) by plains.nodak.edu (8.7.1/8.7.1) id TAA21647; Wed, 28 Feb 1996 19:53:57 -0600 (CST)
Date: Wed, 28 Feb 1996 19:53:57 -0600 (CST)
From: Mark Tinguely <tinguely@plains.nodak.edu>
Message-Id: <199602290153.TAA21647@plains.nodak.edu>
To: jkh@time.cdrom.com
Subject: Re: Seeking advice on mrouted configuration..
Cc: multimedia@freebsd.org
Sender: owner-multimedia@freebsd.org
Precedence: bulk

>  > if mrouted thinks the ed0 and sl0 are on the same network because
>  > of overlaping netmasks, it will not forward to sl0.
>  
>  Any chance of perhaps adding an option to *force* it to do so anyway? :-)

the offending code is in the kernel. If I remember correctly, it is possible
to bypass this netmask enforcement. I would have to think through the
possibility of multicast routing problems. For example, mrouted may not forward
something orginating on sl0, because it thinks ed0 attached devices already
see the packet.

--mark.