--- Begin Message ---
Hi,
I am using live555 to provide an RTSP stream on an IP camera. This works great.
Now I was tasked to also provide tunneling over HTTP, so I was very happy when
I learnt that live555 already has this covered by simply calling
RTSPServer::setUpTunnelingOverHTTP. This also works, but one question arose for
me:
The camera is running an HTTP server and due to "requirements" the
RTSP-over-HTTP server must be accessible on the same port as the HTTP server.
So I used a different port than the normal HTTP port in
RTSPServer::setUpTunnelingOverHTTP and configured the HTTP server as a proxy
that forwards to that port in my RTSP server.
The result of this is that my RTSP-over-HTTP stream is now accessible through 2
different ports. While not a big problem, this seems inelegant and some users
tend to be wary of open ports, so I would like to ask: Is there a way to make
the live555 RTSP server only listen on localhost for the RTSP-over-HTTP port?
(the normal RTSP port should still be open to any address) It seems like the
fHTTPServerSocketIPv4 and fHTTPServerSocketIPv6 members of RTSPServer are
private, so I cannot just mess with them. (also creating these sockets myself
would boil down to doing almost everything that the setupStreamSocket function
already does)
If this simply can't be done, then so be it, but if there actually is a way,
I'd be very happy to hear about it.
Ideally setupStreamSocket could be adjusted so that an address to bind to can
be supplied, but I would understand if you don't want to support this somewhat
niche use case.
In the worst case, I could use iptables or something similar to block the
additional port.
In any case, thanks and have a nice day
--- End Message ---
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
