Understood. Thanks to both of you for your prompt (and extremely useful) answer
!
-Original Message-
From: live-devel On Behalf Of Ross Finlayson
Sent: Wednesday, January 18, 2023 4:20 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] membership report group
As Rune Torgesen explained, multicast packets are routed on the network based
on the IP multicast address; the port number is used only once an IP (actually
UDP/IP) multicast packet reaches each recipient. So, each stream (or at least
each PC) should use a separate multicast address.
Also:
>
OK that was my backup plan. So since plan A is a stupid thing, I'll use that
plan B.
From: live-devel On Behalf Of Rune Torgersen
Sent: Wednesday, January 18, 2023 3:14 PM
To: live-devel@lists.live555.com
Subject: Re: [Live-devel] membership report group
No, this is how multicast routing works
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
Could my issue comes from the fact that the code of that method below is
commented out ?
void Groupsock::multicastSendOnly() {
// We disable this code for now, because - on some systems - leaving the
multicast group seems to cause sent packets
// to not be received by other applications (at
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.
Cur
