No, this is how multicast routing works. Multicast is routed/joined by IP not 
IP/Port, so to not get all other traffic, each stream will have to use a 
separate multicast IP address.

This is infact how commercial multicast cable companies have to do it (I work 
in that industry) - each stream is on a separate multicast address.

________________________________
From: live-devel <live-devel-boun...@us.live555.com> on behalf of g.jaegy 
<g.ja...@imagine3d.fr>
Sent: Wednesday, January 18, 2023 7:02 AM
To: live-devel@lists.live555.com <live-de...@us.live555.com>
Subject: [Live-devel] membership report group

This email originated from outside Innovative Systems. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.


Hi Ross,



That subject is a bit beyond my knowledge, so I would like to apologize for any 
stupid thing I might be saying.



We have a system streaming 54 channels, using a different RTSP server for each 
channel, using 18 PCs in total (so about 3 streams per PC). Transport is using 
multicast.



Currently, we use the same common multicast IP for all the streams (with 
different ports of course).



However, this means that a given “video stream generator” PC receives all the 
packets from all the other channels, causing the network traffic to be 
significant on each of this “video stream generator”.



We have been told that this was due to each stream to generate and send IGMPv2 
packets (membership report group).



Since we don’t really need each “video stream generator” PC to receive the 
multicast packets generated by the other PC, it seems that we would like to 
avoid these IGMPv2 packets to be sent.



I’m not sure whether this is possible or not. Do you have any idea ? Is it 
possible to configure live555 to not send those IGMPv2 packets ?



Again, sorry if that sounds stupid, but to be honest I’m not completely sure I 
understand exactly what this packets are being used for (and whether we need 
them in order to send multicast packet on a given IP address).



Thanks,

Greg
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to