[gstreamer-bugs] [Bug 578378] New: multiudpsink on Vista is bound on IPv6 and fails when sending to IPv4 address

[GStreamer (bugzilla.gnome.org)]

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=578378

  GStreamer | gst-plugins-good | Ver: 0.10.22
           Summary: multiudpsink on Vista is bound on IPv6 and fails when
                    sending to IPv4 address
           Product: GStreamer
           Version: 0.10.22
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: filippo.dellabetta at telecomitalia.it
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
When using udpsink (gst-plugins-good-0.10.14) on Vista, by default (and if you
don't provide external fd) it creates socket with AF_INET6 family (line 611 of
gstmultiudpsink.c) even if is not requested. When trying to specify host with
IPv4 it fails sending ( sendto on line 397 of same file returns SOCKET_ERROR )
since it is already bound on IPv6.

Steps to reproduce:
simply execute
gst-launch audiotestsrc ! udpsink host=1.2.3.4 port=5678




Actual results:
no packet are sent to the host

Expected results:
UDP packet sent on host 1.2.3.4

Does this happen every time?
Yes

Other information:
Probably adding a parameter to force socket binding on IPv4 would be an idea.


-- 
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=578378.