[gstreamer-bugs] [Bug 588245] New: TTL is never applied with udpsink/udpmultisink

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

  GStreamer | gst-plugins-good | Ver: 0.10.23
           Summary: TTL is never applied with udpsink/udpmultisink
           Product: GStreamer
           Version: 0.10.23
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: nicolas.richasse at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.25/2.26
   GNOME milestone: Unspecified


the "ttl" parameter of the udpsink and udpmultisink elements is never applied
on the socket, and always have the same value:
- 64 when the host parameter is an unicast address
- 1 when the host parameter is a multicast address


-----Examples--

--> The GST pipeline sending an unicast udp stream with TTL=100
# gst-launch videotestsrc ! x264enc bitrate=200 ! rtph264pay ! udpsink
host=192.168.1.1 port=10101 ttl=100

--> The TCPDUMP capture showing packets with TTL=64
08:18:43.059112 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 947) 192.168.1.2.53651 > 192.168.1.1.10101: UDP, length 919

-----

--> The GST pipeline sending a multicast udp stream with TTL=100
# gst-launch videotestsrc ! x264enc bitrate=200 ! rtph264pay ! udpsink
host=225.0.0.1 port=10101 auto-multicast=true ttl=100

--> The TCPDUMP capture showing multicast packets with TTL=1
08:20:37.919368 IP (tos 0x0, ttl 1, id 0, offset 0, flags [DF], proto UDP (17),
length 935) 192.168.1.2.53644 > 225.0.0.1.10101: UDP, length 907


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