After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 770969 - Reserve local port in the pool in multicast
Reserve local port in the pool in multicast
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-rtsp-server
unspecified
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-09-06 19:54 UTC by Xavier Claessens
Modified: 2018-11-03 15:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Xavier Claessens 2016-09-06 19:54:51 UTC 
In the multicast case, we bind the socket on ANY address, so I guess the port should be taken from the unicast pool as well as from the multicast pool.

I think alloc_ports_one_family() should reserve a multicast address from the pool, then try to reserve the same port in the unicast pool, then loop until it finds a port that is available in both pools.

I added FIXME comments in gst_rtsp_stream_get_multicast_address() and gst_rtsp_stream_reserve_address() about this.
Comment 1 Sebastian Dröge (slomo) 2016-09-07 07:42:22 UTC 
Indeed a problem, but also not a new one if I'm not mistaken. The whole address pool story in the server seems rather broken.
Comment 2 Xavier Claessens 2016-09-07 13:16:50 UTC 
Not a regression indeed.
Comment 3 GStreamer system administrator 2018-11-03 15:40:28 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/issues/28.