"GStreamer" (bugzilla.gnome.org)
2013-05-28 12:45:27 UTC
https://bugzilla.gnome.org/show_bug.cgi?id=701129
GStreamer | gst-rtsp-server | 1.x
Summary: ipv6 support in rtsp-stream
Classification: Platform
Product: GStreamer
Version: 1.x
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-rtsp-server
AssignedTo: gstreamer-***@lists.freedesktop.org
ReportedBy: ***@axis.com
QAContact: gstreamer-***@lists.freedesktop.org
GNOME version: ---
When binding to an ipv6 socket we create rtsp-streams that have multiudp-sinks
that are not compatible with ipv6. There is a private flag in rtsp-stream:
is_ipv6. This flag works, if I set it to true the system is capable of serving
over ipv6. But noone sets this flag and it is non-trivial to do it correctly.
The reason is that when creating the stream it's hard to get the information
(since media and thus stream is created in the construct media factory call
which we have little control over, and we do not necassarily have the clients
yet (thus being able to look at the client address to figure it out).
My ideas are ranging from something simple just trying to communicate the
is_ipv6 through the construct call to refactorying the media and extracting the
stream construction to a seperate factory system enabling this case and other
future cases.
What do upstream guys think?
GStreamer | gst-rtsp-server | 1.x
Summary: ipv6 support in rtsp-stream
Classification: Platform
Product: GStreamer
Version: 1.x
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-rtsp-server
AssignedTo: gstreamer-***@lists.freedesktop.org
ReportedBy: ***@axis.com
QAContact: gstreamer-***@lists.freedesktop.org
GNOME version: ---
When binding to an ipv6 socket we create rtsp-streams that have multiudp-sinks
that are not compatible with ipv6. There is a private flag in rtsp-stream:
is_ipv6. This flag works, if I set it to true the system is capable of serving
over ipv6. But noone sets this flag and it is non-trivial to do it correctly.
The reason is that when creating the stream it's hard to get the information
(since media and thus stream is created in the construct media factory call
which we have little control over, and we do not necassarily have the clients
yet (thus being able to look at the client address to figure it out).
My ideas are ranging from something simple just trying to communicate the
is_ipv6 through the construct call to refactorying the media and extracting the
stream construction to a seperate factory system enabling this case and other
future cases.
What do upstream guys think?
--
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.
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.