netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Ben Greear <greearb@candelatech.com>
Cc: David Ahern <dsahern@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: vrf and multicast is broken in some cases
Date: Wed, 15 Jan 2020 21:19:20 +0200	[thread overview]
Message-ID: <20200115191920.GA1490933@splinter> (raw)
In-Reply-To: <dbefe9b1-c846-6cc6-3819-520fd084a447@candelatech.com>

On Wed, Jan 15, 2020 at 11:02:26AM -0800, Ben Greear wrote:
> 
> 
> On 01/15/2020 10:45 AM, David Ahern wrote:
> > On 1/15/20 10:57 AM, Ben Greear wrote:
> > > Hello,
> > > 
> > > We put two different ports into their own VRF, and then tried to run a
> > > multicast
> > > sender on one and receiver on the other.  The receiver does not receive
> > > anything.
> > > 
> > > Is this a known problem?
> > > 
> > > If we do a similar setup with policy based routing rules instead of VRF,
> > > then the multicast
> > > test works.
> > > 
> > 
> > It works for OSPF for example. I have lost track of FRR features that
> > use it, so you will need to specify more details.
> > 
> > Are the sender / receiver on the same host?
> 
> Yes, like eth2 sending to eth3, eth2 is associated with _vrf2, eth3 with _vrf3.

Two questions:

1. Did you re-order the FIB rules so that l3mdev rule is before the main
table?
2. Did you configure a default unreachable route in the VRF?

IIRC, locally generated multicast packets are forwarded according to the
unicast FIB rules, so if you don't have the unreachable route, it is
possible the packet is forwarded according to the default route in the
main table.

> 
> I'll go poking at the code.
> 
> Thanks,
> Ben
> 
> -- 
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2020-01-15 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 17:57 vrf and multicast is broken in some cases Ben Greear
2020-01-15 18:45 ` David Ahern
2020-01-15 19:02   ` Ben Greear
2020-01-15 19:19     ` Ido Schimmel [this message]
2020-01-15 20:00       ` Ben Greear
2020-01-15 20:23         ` Ido Schimmel
2020-01-15 20:33           ` David Ahern
2020-01-15 21:09             ` Ben Greear
2020-01-15 22:53               ` David Ahern
2020-01-15 20:24         ` David Ahern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200115191920.GA1490933@splinter \
    --to=idosch@idosch.org \
    --cc=dsahern@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).