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 g
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 ro
on a separate multicast address.
From: live-devel on behalf of g.jaegy
Sent: Wednesday, January 18, 2023 7:02 AM
To: live-devel@lists.live555.com
Subject: [Live-devel] membership report group
This email originated from outside Innovative Systems. Do not click
y
Sent: Wednesday, January 18, 2023 2:03 PM
To: live-devel@lists.live555.com
Subject: [Live-devel] membership report group
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 dif
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
They are the IGMP messages sent to join the multicast group the server will
be sending to, which in this case seems to be 228.67.43.91.
On most decent (and properly configured) pieces of network hardware you have
to join the group in order to receive packets sent to the multicast address.
These me
Hi.
While tracing a stream using wireshark I noticed the following packets
sent from the client between a describe and setup:
Destination 224.0.0.22 IGMP V3 Membership Report
Destination 228.67.43.91 UDP Source port: 15947 Destination port: 15947
Destination 224.0.0.22 IGMP V3 Membership Repor
