All things related to multicast

[Greg Shepherd <>]

I think this was just realized as a high SA count source while hunting
down the real source of the trouble: a port-scan into the class D range.

Greg

On Tue, 16 Jan 2001, zaid wrote:

> Is there a clue that traffic on this group is what created the
> instability ?
> 
> Zaid
> -----Original Message-----
> From: Matthew Davy 
> <>
> To: Philip Pishioneri 
> <>
> Cc: 
> 
>  
> <>
> Date: Tuesday, January 16, 2001 2:15 PM
> Subject: Re: Norton Ghost Re: MSDP instability today
> 
> 
> 
> I just finished adding this to the Abilene MSDP filters.
> 
> - Matt
> 
> --------------------
> Matthew Davy
> 
> 812-855-7728
> Network Engineer
> Indiana University
> Abilene NOC
> --------------------
> 
> 
> On Mon, Jan 15, 2001 at 07:01:08PM -0500, Philip Pishioneri wrote:
> > Matthew Davy wrote:
> > >
> > > Pls ignore that;   I should have looked through the list archives
> before
> > > opening my mouth (Actually I looked at my folder, but this message
> hadn't
> > > made it out of my inbox yet :-) ...
> > >
> > > From: Simon Leinen 
> > > <>
> > > Date: Wed, 10 Jan 2001 00:18:24 +0100
> > > To: 
> > > ,
> > >  
> > > 
> > >
> > > While I was browsing our MSDP tables at random, I noticed a lot of
> > > source announcements for group 229.55.150.208.  This address is
> used
> > > by a product called "Norton Ghost" for server discovery, as
> documented
> > > under:
> >
> > I think we'll be adding that to our filter list as previously
> suggested.
> >
> > Anyone want to thwap Norton on the back of the head for using such
> an
> > address? :-)
> >
> > -Phil
> 
> 
>