poc-fec(1) [debian man page]
POC-FEC(1) User Command POC-FEC(1) NAME
poc-fec - send FEC MP3 streams SYNOPSIS
poc-fec [ -s address ] [ -p port ] [ -t ttl ] [ -q ] [ -k fec_k ] [ -n fec_n ] files... DESCRIPTION
poc-fec is a streaming server sending mp3 data using a custom FEC protocol. The streamed MP3 frames are first decomposed in autonomous data units (ADUs). These ADUs are grouped into ADU groups, which are encoded redundantly using a FEC method by Luigi Rizzo. A group of k ADUs is encoded as n data packets. Any k of these n data packets is sufficient to recover the original k ADUs. It sends the files in the order given on the command-line. Use the filename - to stream from standard input. Normally, the FEC protocol is used to stream to multicast groups. OPTIONS
-s address Specify the address to send to (default 224.0.1.23). -p port Specify the port to send to (default 1500). -t ttl Specify the TTL parameter to be set on outgoing parameters (default 1). -q Don't output any information on standard error. -k fec_k Specify the number of ADUs that will be encoded as an ADU group (default 20). -n fec_n Specify the number of packets that the ADU groups will be encoded to (default 25). This number must be greater than the fec_k param- eter. EXAMPLES
poc-fec -s 224.0.1.24 -p 8989 -t 2 -k 16 -n 32 bla.mp3 Send the file bla.mp3 using the RTP RFC fec protocol to the address 224.0.1.24 on port 8989, and set the TTL to 2. MP3 frames of bla.mp3 are converted to ADUs and grouped in ADU groups of 16 ADUs. These 16 ADUs are encoded into 32 packets and streamed. A client will have to receive at least 16 packets to recover the original ADUs. AUTHORS
Manuel Odendahl <manuel@bl0rg.net>, Florian Wesch <dividuum@bl0rg.net> February 2005 POC-FEC(1)
Check Out this Related Man Page
NG_FEC(4) BSD Kernel Interfaces Manual NG_FEC(4) NAME
ng_fec -- netgraph Fast EtherChannel node SYNOPSIS
#include <netgraph/ng_fec.h> DESCRIPTION
The fec node implements Ethernet port trunking using the ``Cisco Fast EtherChannel'' protocol. Upon creation, a fec node creates a network interface associated with it. Interfaces are named ``fec0'', ``fec1'', etc. New nodes take the first available unit. HOOKS
The fec node accepts any hooks. However it does not use them. Under normal operation, a fec node should not have any hooks. CONTROL MESSAGES
Interface membership in the FEC group is configured with the following control messages: NGM_FEC_ADD_IFACE (``add_iface'') Attach interface to the FEC group. The target interface name is passed as a string argument. NGM_FEC_DEL_IFACE (``del_iface'') Remove interface from the trunk. The target interface name is passed as a string argument. The following control messages define the forwarding method for a node: NGM_FEC_SET_MODE_MAC (``set_mode_mac'') Forwarding decisions will be based on the link-layer MAC address of the destination. NGM_FEC_SET_MODE_INET (``set_mode_inet'') Forwarding decisions will be based on the IP address of the destination. SHUTDOWN
This node shuts down upon receipt of a NGM_SHUTDOWN control message. EXAMPLES
The following example script creates an fec node, attaches four Ethernet interfaces to it and sets the forwarding method to be IP-address based: /usr/sbin/ngctl -f- << SEQ mkpeer fec dummy fec msg fec0: add_iface "dc0" msg fec0: add_iface "dc1" msg fec0: add_iface "dc2" msg fec0: add_iface "dc3" msg fec0: set_mode_inet SEQ SEE ALSO
netgraph(4) HISTORY
The fec node type was implemented in FreeBSD 5.0. AUTHORS
The fec node was written by Bill Paul <wpaul@FreeBSD.org>. This manual page was written by Gleb Smirnoff <glebius@FreeBSD.org>. BSD
July 22, 2004 BSD