About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: Top 50 unstable DVMRP routes

  • To:
  • From: Dino Farinacci < >
  • Date: Tue, 2 Dec 1997 12:37:39 -0800 (PST)
  • Cc:

>>   Configuring the DVMRP distance high is sufficient to prevent the
>> route instability problem, you're right.  However, if you don't use the
>> A<B<C solution as described on the web page, you will create black
>> holes.  I don't want to trade one problem for another, which is why the
>> web page suggests the A<B<C configuration which solves both.  The set
>> of routes requiring the C distance could be empty, of course, and in
>> that case it reduces to the solution you were suggesting.

    The distance C introduces a problem. What if there is a DVMRP route that
    covers one of the unicast routes your not advertising into DVMRP. Then
    a multicast packet from a local source will RPF to the DVMRP route and
    not get forwarded to local members.

    You should only use 2 distances in my opinion.

Dino




  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community