[Bug 639420] RTSP setup, add client_ports

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Fri Nov 16 03:24:51 PST 2012


https://bugzilla.gnome.org/show_bug.cgi?id=639420
  GStreamer | gst-plugins-good | 0.10.26

Wim Taymans <wim.taymans> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #12 from Wim Taymans <wim.taymans at gmail.com> 2012-11-16 11:24:41 UTC ---
We should not try to allocate any ports client side when requesting multicast.
It is only when the server replies that we can create any port and add
ourselves to the multicast address.

What we should do is suggest a port pair in multicast when the user selected
one (without actually allocating and binding to the port).

Setting reuse is IMO not such a good idea as it allows multiple clients on the
same machine to bind to the same port in unicast, which is only going to fail
(it looks like only the last bound socket gets the data).

If I understand the problem correctly, this should fix the issue:

commit cc9cb26be16e51fe748a01b2a75be91c35bcfc1e
Author: Wim Taymans <wim.taymans at collabora.co.uk>
Date:   Fri Nov 16 12:00:14 2012 +0100

    rtspsrc: propose ports in multicast

    When the user configured a port-range, propose ports from this range
    as the multicast ports. The server is free to ignore this request but if it
    honors it, increment our ports so that we suggest the next port pair for
    the next stream.

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

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- 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