Quote:
Originally Posted by Stream Recorder
What kind of traffic needs to be redirected to rtmpsuck? TCP/IP coming to port 1935? Should this traffic be redirected to localhost:1935?
|
Almost. You need to redirect traffic *going out to* port 1935, not "coming to". And of course, port 1935 is only a default; any particular server could be configured to use any other port arbitrarily. Moreover, you need the redirect to be done at the kernel level, so that the original destination address is preserved inside the kernel, and can be retrieved by the rtmpsuck program. When you edit the hosts.txt file, you can redirect a hostname to localhost, but the original destination address is lost. And of course, editing hosts.txt doesn't help you if the original RTMP destination was specified as a numeric IP address.
Quote:
|
And what about RTMPE protocol? Do you think a TCP/IP filter that handles connection redirects for RTMPE streams can be DMCA compliant?
|
The TCP/IP filter doesn't know (or care) what the data streams carry. It simply takes traffic bound for one destination and swaps in an alternate destination instead. DMCA is irrelevant.
Quote:
|
What about rtmpsuck.exe on Windows? Can it be just launched or any tweaks are needed?
|
Once the TCP/IP redirector is running, rtmpsuck needs no special tweaks.
Quote:
|
symas driver works in Windows XP only?
|
WinNT, Win2K, WinXP. I haven't tried it on Vista or Win7 but from what I've read in the developer's documentation, it probably will not work.