Skip to Content.
Sympa Menu

wg-multicast - Re: SAP storm from 145.19.1.183

Subject: All things related to multicast

List archive

Re: SAP storm from 145.19.1.183


Chronological Thread 
  • From: Zenon Mousmoulas <>
  • To: Michael Fortier <>
  • Cc:
  • Subject: Re: SAP storm from 145.19.1.183
  • Date: Thu, 26 Jun 2008 10:19:17 +0300


On 23 Ιουν 2008, at 3:43 ΜΜ, Michael Fortier wrote:

[...]

Hi,
Here is the message I posted Friday... but everybody didn't receive it.

I tested the miniSapserver 0.3.4 found here :
http://download.videolan.org/pub/videolan/miniSAPserver/
This version has some bugs.
DO NOT USE IT
Problem was in the announcement interval.

I corrected and now the intervalley of dispatch is 30 seconds (fixed).
You can find sources here :
http://exp-videos.univ-paris13.fr/src/minisapserver-0.3.4b.tar.gz

I'm under Linux. Commands to install :
#./configure (--prefix=...)
# make && make install
# ./minisapserver -d -c sap.cfg

sap.cfg exemple with 2 announces :
[global]
sap_delay=55
sap_ttl=255
[program]
name=Video SD 352x264 - 35 ans P13 - IPv4
user=videolan
machine=exp-videos.univ-paris13.fr
site=http://exp-videos.univ-paris13.fr
address=224.5.43.1
port=1234
playlist_group=University Paris 13
program_ttl=255
[program]
name=Video SD 352x264 - 35 ans P13 - IPv6
user=videolan
machine=exp-videos.univ-paris13.fr
site=http://exp-videos.univ-paris13.fr
address=ff0e::2:beeb
port=1234
playlist_group=University Paris 13
program_ttl=255

I created a blog which lists all information
I shall give you the url as soon as it will be made
Regards

Michael Fortier


Bonjour Michél,

I looked at what you did (hardcoding sap_delay to 30 seconds).

I tested the unmodified 0.3.4 with the configuration you provide and I confirmed with VLC and a packet trace that it works flawlessly: it adheres to the configured interval (30s) and sends valid SAP messages.
The only problems I could spot are that it doesn't set the originating source field correctly in the SAP header (not so uncommon) and that it doesn't announce IPv6 sessions to the appropriate IPv6 SAP group (it can't because it doesn't differentiate them from IPv4).

But, guess what, no SAP storm!

Is this the configuration you were using when the sap storm took place? I think some piece of the puzzle is missing here.

Z.




Archive powered by MHonArc 2.6.16.

Top of Page