Skip to Content.
Sympa Menu

wg-multicast - Re: yet another (brief) SAP storm

Subject: All things related to multicast

List archive

Re: yet another (brief) SAP storm


Chronological Thread 
  • From: Brian Fitzgerald <>
  • To: Dave Diller <>, wg-multicast List <>
  • Subject: Re: yet another (brief) SAP storm
  • Date: Wed, 25 Jun 2008 16:01:01 -0700
  • Accept-language: en-US
  • Acceptlanguage: en-US

Title: Re: yet another (brief) SAP storm
Hello All

I believe I caused that one.

I was experimenting internally with miniSAP (ACLed off from the world) and got caught by an ACL change.  As soon as I knew I shut it down.

This is getting to be ridiculous.   Any time the niniSAP application is started up anywhere, it causes havoc.  I was setting up to stream our university radio station internally on a couple of different formats.  We are doing multiple transcoded multicast streams from their live unicast stream, and each of the transcode streams could be SAP announced, but it is clunky to do each individually – thus the SAP server.

I offer my 2 bits worth – do not, under any circumstances, use the miniSAP server for anything.  It is too horrendously buggy!  The audio stream I was generating was only about 64k – the SAP stream was much larger!

Anyway – live and learn – sorry all.

Brian Fitzgerald
Network Services
University of Victoria
Victoria, BC, Canada


On 25/06/08 3:51 PM, "Dave Diller" <> wrote:

Just saw this for 20-30 minutes, it was about 275M/sec inbound here as
seen on my lab switch:
   5 minute input rate 275939000 bits/sec, 116536 packets/sec

Came from:

Group: 224.2.127.254
     Source: 142.104.22.43/32
     Statistics: 33465 kBps, 122134 pps, 161904168 packets

but it quickly subsided and is gone now.  Either they (University of
Victoria, Canada) caught it directly or I2 is getting quicker about
proactive filtering. ;-)

-dd




Archive powered by MHonArc 2.6.16.

Top of Page