[gstreamer-bugs] [Bug 534243] New: udpsink no longer supports IPv4 on Windows, only IPv6

[GStreamer (bugzilla.gnome.org) <bug...@bu...>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=534243

  GStreamer | gst-plugins-good | Ver: HEAD CVS
           Summary: udpsink no longer supports IPv4 on Windows, only IPv6
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Windows
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gst...@li...
        ReportedBy: ole...@ta...
         QAContact: gst...@li...
     GNOME version: Unspecified
   GNOME milestone: Unspecified


After some recent IPv6 improvements it looks like udpsink is now broken for
IPv4 on Windows. Turns out that sockets of address family AF_INET6 cannot send
data to AF_INET addresses, or at least so it seems. sendto() returns
WSAEAFNOSUPPORT, which translates to "An address incompatible with the
requested protocol was used.".

If I comment out the following line in in gstmultiudpsink.c, in
gst_multiudpsink_init_send, it works for IPv4 again:
if ((sink->sock = socket (AF_INET6, SOCK_DGRAM, 0)) == -1)

It sounds like we might have to rethink how to handle this if my initial
findings are correct. If so, maybe we could make it so that the first client on
IPv4 results in an IPv4 socket being created, and vice versa for IPv6.

Thoughts?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=534243.