2 Apr
2013
2 Apr
'13
3:44 p.m.
On 04/02/13 09:15, aft wrote:
So i was asking how to install mediaproxy-ng itself?
If you're on a Debian system, you can simply issue dpkg-buildpackage and
then install the packages it produces. Otherwise you can compile the
sources yourself. A simple "make" in each one of the 3 subdirectories
(daemon, iptables-extension and kernel-module) should do the trick,
provided all the dependencies are installed. You need to have at least
the "daemon" compiled, the other 2 components are optional and required
only if you wish to utilize kernel-based packet forwarding.
The daemon is a single binary and will print usage information if
executed. The minimum required parameters are listening socket/port
("udp" for rtpproxy module, "ng" for rtpproxy-ng module;
"tcp" is a
legacy protocol not in use any more), local IP address(es) and a kernel
table ID. The kernel table ID is required even if you don't use kernel
forwarding and is usually set as zero. If the kernel module isn't
loaded, the daemon will print a warning but will continue to function
normally.
To enable kernel-based forwarding, you need to load the kernel module
and add an iptables rule to use it, for example:
iptables -I INPUT -p udp -j MEDIAPROXY --id $ID
with $ID being the same ID as you used when starting the daemon
(normally zero). With this in place, incoming packets are delivered to
the kernel module, which then can forward them if instructed to do so by
the daemon.
And that's all there is to it really.
cheers