[Bug 764679] New: IPv6 UDP stream to site-local multicast address

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Wed Apr 6 13:05:27 UTC 2016


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

            Bug ID: 764679
           Summary: IPv6 UDP stream to site-local multicast address
    Classification: Platform
           Product: GStreamer
           Version: 1.x
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: gnome at desire.ch
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

While trying to switch from gstreamer 0.10 to an 1.x version I noticed that the
UDP stream that I'm trying to receive no longer works. The stream is sent to
the IPv6 all-nodes local multicast address (ff02::1) which seems to be a
problem for gstreamer 1.x.

The old pipeline starts with "gst-launch-0.10 udpsrc port=4001
multicast-group=ff02::1%eth0 caps="${CAPS}" ! [..]". Trying a similar thing
with 1.x fails with an error message:


$ gst-launch-1.0 udpsrc port=4001 multicast-group=ff02::1%eth0 caps="${CAPS}" !
fakesink
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstUDPSrc:udpsrc0: Could not get/set
settings from/on resource.
Additional debug info:
/tmp/portage/media-libs/gst-plugins-good-1.6.3/work/gst-plugins-good-1.6.3/gst/udp/gstudpsrc.c(1119):
gst_udpsrc_open ():
+/GstPipeline:pipeline0/GstUDPSrc:udpsrc0:
bind failed: Error binding to address: Invalid argument
Setting pipeline to NULL ...
Freeing pipeline ...


After asking for advice on the mailing list I was pointed to an #ifdef which
modifies the multicast group behaviour:
https://lists.freedesktop.org/archives/gstreamer-devel/2016-April/057644.html

Removing the "#ifdef G_OS_WIN32" on gstudpsrc.c:953 fixes the issue for me but
will, I assume, break things for others.

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


More information about the gstreamer-bugs mailing list