gst-rtsp-server, rtspsrc &Firewall/NAT?

[Carl Kovamees]

Right. Unfortunately I don’t have access to the Firewall/NAT. I have full control on the server side, but can’t change anything on the client side. ☹


From: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] On Behalf Of Chuck Crisler
Sent: Monday, July 28, 2014 11:57 AM
To: Discussion of the development of and with GStreamer
Subject: Re: gst-rtsp-server, rtspsrc &Firewall/NAT?

This is not a GStreamer specific problem, it happens with all RTSP (and other) servers. What you need to do is to choose a client port and configure the client to always request that port, then enter a firewall rule to open that port. Be forewarned, there are some buggy NATs that will lie about opening ports.

On Mon, Jul 28, 2014 at 10:34 AM, Carl Kovamees <ckovamees at digitalresultsgroup.com<mailto:ckovamees at digitalresultsgroup.com>> wrote:
Thanks. It actually fallsback to TCP automatically. But, I really want UDP. ☺

/Carl

From: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org<mailto:gstreamer-devel-bounces at lists.freedesktop.org>] On Behalf Of Mailing List SVR
Sent: Monday, July 28, 2014 10:27 AM
To: gstreamer-devel at lists.freedesktop.org<mailto:gstreamer-devel at lists.freedesktop.org>
Subject: Re: gst-rtsp-server, rtspsrc &Firewall/NAT?

Il 28/07/2014 16:02, Carl Kovamees ha scritto:
Hi all.

This is about getting through a client side firewall/NAT that assigns new source ports every connection.

I’m using 1.4; gst-rtsp-server and the gst-launch-1.0 with playbin as client.

My client is behind a firewall/NAT that gives random outbound ports. The rtsp-server side is pretty much wide open.

After the RTSP PLAY message, but before the server starts to send RTP packets, the client sends UDP packets to the correct server port (I assume these are the rtspsrc element’s dummy packets). However, the client source port is not what was specified in the RTSP SETUP message (client_port) – the firewall seems to assign new ones every time.

Is there any way to override the client_port based on the (dummy packets) source port?

If not, any ideas of how to leverage the rtspsrc element’s dummy packets in lieu of implementing libnice or other firewall/NAT traversal technics?


Any ideas are much appreciated – thanks,

try to use rtsp over tcp, if you use gstreamer as client simply change the url from rtsp:// to rtspt://

Nicola



/Carl



_______________________________________________

gstreamer-devel mailing list

gstreamer-devel at lists.freedesktop.org<mailto:gstreamer-devel at lists.freedesktop.org>

http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel


_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org<mailto:gstreamer-devel at lists.freedesktop.org>
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140728/715a530f/attachment.html>