[Bug 757488] gst-rtsp-server: multicast functionality is broken if using the same port ranges for multicast and unicast

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=757488

--- Comment #77 from Patricia Muscalu <patricia at axis.com> ---
(In reply to Sebastian Dröge (slomo) from comment #75)
> (In reply to Patricia Muscalu from comment #74)
> > (In reply to Sebastian Dröge (slomo) from comment #70)
> > > commit 206d2ded099e49d8d6e03fdc6158eb6ed96d6276
> > > Author: Sebastian Dröge <sebastian at centricular.com>
> > > Date:   Sat Mar 5 10:52:11 2016 +0200
> > > 
> > >     rtsp-stream: Disable multicast loopback for all our sockets
> > >     
> > >     On Windows this is a receiver-side setting, on Linux a sender-side
> > > setting. As
> > >     we provide a socket ourselves to udpsrc, udpsrc is never setting the
> > > multicast
> > >     loopback setting on the socket... while udpsink does which unfortunately
> > > has
> > >     no effect here on Windows but on Linux.
> > >     
> > >     https://bugzilla.gnome.org/show_bug.cgi?id=757488
> > 
> > This is supposed to be done in create_and_configure_udpsources_one_family():
> > g_object_set (G_OBJECT (udpsrc_out[0]), "loop", FALSE, NULL);
> > g_object_set (G_OBJECT (udpsrc_out[1]), "loop", FALSE, NULL);

> Just that udpsrc does not do anything with that flag if we provide it our
> own socket :) That's why I went with the hammer solution now and just
> disabled it directly on the socket from the very start.

Yes, I understand, but in that case we should remove these two lines above from
the code. Maybe setting multicast loopback should be also done in the same
function just to make sure that all configuration that is really needed is done
in one place. What do you think?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.