[quagga-dev 11701] Re: [PATCH] zebra: Connected route addition shoudn't happen in MRIB

Everton Marques everton.marques at gmail.com
Thu Oct 30 12:04:58 GMT 2014


On Thu, Oct 30, 2014 at 5:17 AM, Balaji G <balajig81 at gmail.com> wrote:

> Hi David
>
> On Thu, Oct 30, 2014 at 12:25 PM, David Lamparter <
> david at opensourcerouting.org> wrote:
>
>> On Thu, Oct 30, 2014 at 11:55:28AM +0530, Balaji G wrote:
>> > On Thu, Oct 30, 2014 at 10:40 AM, David Lamparter <
>> > david at opensourcerouting.org> wrote:
>> > > This patch was discussed on IRC between Balaji, Everton and me;  the
>> > > outcome was that Balaji would resend it with a switch to control the
>> > > behaviour.
>> > >
>> >
>> > I would send a V2 with that switch. do you want something "rib-lookup
>> > mrib". On executing this the connected routes and the RPF check is made
>> in
>> > the MRIB and executing "no rib-lookup mrib" would bring it back to URIB
>> > lookup and remove the connected routes. Would that be fine ?
>>
>> Hm, we have 3 cases:
>> 1. MRIB only
>> 2. MRIB first, then URIB
>> 3. URIB only
>>
>> Options 1. and 3. can be "emulated":
>> 1. = use 2. but install add "default unreachable" route to MRIB
>>      => URIB lookup never happens
>> 3. = use 2. but leave MRIB empty
>>      => empty MRIB doesn't get used
>>
>
> Thanks for the suggestion but i guess we can have two in terms of CLI.
> MRIB-URIB and URIB .
>
> MRIB-URIB Case:This would be with MBGP and Mroute enabled where the
> look-up happens at the MRIB first and then URIB. The connected routes would
> be installed in MRIB and URIB
> URIB Only- No MRIB and No routes get installed in MRIB including Connected
> Routes
> MRIB Only - Not sure if this is needed in CLI
>

I would like to know if there is a case for MRIB only as well.

BTW, I found this interesting reference on RPF lookup:

http://blog.ine.com/2011/07/31/understanding-static-multicast-routes/

Everton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20141030/d5f2f6eb/attachment-0001.html>


More information about the Quagga-dev mailing list