All things related to multicast

[Matthew Davy <>]

On Tue, Mar 07, 2000 at 01:17:15PM -0800, Lucy E. Lynch wrote:
> That part I understand, although why they're not peering is a ?

I sorta figured that, but since I couldn't answer the other questions, I 
thought
I'd respond to that one.  Unfortunately without access to any of the routers
involved it's difficult to say what's happening.  Have you contacted UUNet 
about
this ??

- Matt



> Meanwhile, the announcement has twinkled off and now I get:
> 
> # mtrace -s 128.46.200.203 224.2.164.161
> Mtrace from 128.46.200.203 to 128.223.214.23 via group 224.2.164.161
> Querying full reverse path... 
>   0  pythia.uoregon.edu (128.223.214.23)
>  -1  cisco3-gw.uoregon.edu (128.223.214.1)  PIM  thresh^ 0  Prune sent 
> upstream [default]
>  -2  cisco7-gw.uoregon.edu (128.223.2.7)  PIM  thresh^ 0  Unknown error 
> code 8 [128.46/16]
> Round trip time 78 ms
> 
> # mtrace -s 128.223.214.23 128.46.200.203 224.2.164.161
> Mtrace from 128.223.214.23 to 128.46.200.203 via group 224.2.164.161
> Querying full reverse path... 
>   0  viper2.ecn.purdue.edu (128.46.200.203)
>  -1  ascend-gw.customer.ALTER.NET (157.130.5.206)  DVMRP  thresh^ 1  Prune 
> sent upstream [default]
>  -2  ascend-gw.mbone.ALTER.NET (208.205.11.55)  PIM  thresh^ 32 [128.223/16]
>  -3  Loopback0.MB1.KCY1.ALTER.NET (137.39.3.94)  Unknown protocol code 8 
> thresh^ 0  Unknown error code 8 [128.223/16]
>  -4  Loopback0.MB1.EWR1.ALTER.NET (137.39.3.92)  Unknown protocol code 8 
> thresh^ 0  Unknown error code 8 [128.223/16]
>  -5  MBGP-UO.Mbone.ALTER.NET (137.39.26.98)  PIM  thresh^ 32  Unknown error 
> code 8 [128.223.214/23]
>  -6  cisco3-gw.uoregon.edu (128.223.2.3)  PIM  thresh^ 0 [128.223.214/23]
>  -7  pythia.uoregon.edu (128.223.214.23)
> Round trip time 290 ms
> 
> and an explict join brings up a session with just me, as you'd expect.
> 
> - LEL
> 
> On Tue, 7 Mar 2000, Matthew Davy wrote:
> 
> > On Tue, Mar 07, 2000 at 11:29:05AM -0800, Lucy E. Lynch wrote:
> > > A traceroute to the source address goes via Abilene, but mtrace goes via
> > > ALTERNET. I assume this is the commodity route for Purdue. Why is 
> > > multicast traffic between Abilene connected sites going out this
> > > route? 
> > 
> > Purdue does NOT have multicast peering with Abilene.  This is why your 
> > unicast
> > and multicast paths to 128.46.200.203 are different. 
> > 
> > - Matt
> > 
>