[gstreamer-bugs] [Bug 573115] New: [udpsink] set TTL and LOOP properties for multicast groups

[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=573115

  GStreamer | gst-plugins-good | Ver: git
           Summary: [udpsink] set TTL and LOOP properties for multicast
                    groups
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: jan.smout at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


In commit e206f74bcea198673e6e64f04218d7c72a56efcd from 2008-05-21 19:35:50
(gst/udp/: Joining a multicast group and setting the loop/ttl properties are
totally unrelated tasks are must be separ...), the functionality of
gst_udp_join_group() was split in two functions. However, the body of the
second (new) function - gst_udp_set_loop_ttl() - was set in an '#if 0 ....
#endif' block. The result is that multicast streams have a default (multicast)
TTL of 1 and only have significance in your own subnet. Result: your streams
will not pass a single router.

I have two patches which I will attach shortly:

1- Make sure the TTL and loop properties are set when multicasting
2- Match the default multicast TTL to the (more sane?) default value of 1


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