dccplsi(1) [debian man page]
DCCPLSI(1) LTP executables DCCPLSI(1) NAME
dccplsi - DCCP-based LTP link service input task SYNOPSIS
dccplsi {local_hostname | @}[:local_port_nbr] DESCRIPTION
dccplsi is a background "daemon" task that receives DCCP datagrams via a DCCP socket bound to local_hostname and local_port_nbr, extracts LTP segments from those datagrams, and passes them to the local LTP engine. Host name "@" signifies that the host name returned by hostname(1) is to be used as the socket's host name. If not specified, port number defaults to 1113. The link service input task is spawned automatically by ltpadmin in response to the 's' command that starts operation of the LTP protocol; the text of the command that is used to spawn the task must be provided as a parameter to the 's' command. The link service input task is terminated by ltpadmin in response to an 'x' (STOP) command. EXIT STATUS
0 dccplsi terminated normally, for reasons noted in the ion.log file. If this termination was not commanded, investigate and solve the problem identified in the log file and use ltpadmin to restart dccplsi. 1 dccplsi terminated abnormally, for reasons noted in the ion.log file. Investigate and solve the problem identified in the log file, then use ltpadmin to restart dccplsi. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: dccplsi can't initialize LTP. ltpadmin has not yet initialized LTP protocol operations. LSI task is already started. Redundant initiation of dccplsi. LSI can't open DCCP socket. This probably means DCCP is not supported on your system. Operating system error. This probably means that you are not using an operating system that supports DCCP. Make sure that you are using a current Linux kernel and that the DCCP modules are being compiled. Check errtext, correct problem, and restart dccplsi. LSI can't initialize socket. Operating system error. Check errtext, correct problem, and restart dccplsi. LSI can't create listener thread. Operating system error. Check errtext, correct problem, and restart dccplsi. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
ltpadmin(1), dccplso(1), owltsim(1) perl v5.14.2 2012-05-25 DCCPLSI(1)
Check Out this Related Man Page
DCCPCLO(1) BP executables DCCPCLO(1) NAME
dccpclo - DCCP-based BP convergence layer output task SYNOPSIS
dccpclo remote_hostname[:remote_port_nbr] DESCRIPTION
dccpclo is a background "daemon" task that connects to a remote node's DCCP socket at remote_hostname and remote_port_nbr. It then begins extracting bundles from the queues of bundles ready for transmission via DCCP to this remote bundle protocol agent and transmitting those bundles as DCCP datagrams to the remote host. If not specified, remote_port_nbr defaults to 4556. Note that dccpclo is not a "promiscuous" convergence layer daemon: it can transmit bundles only to the node to which it is connected, so scheme configuration directives that cite this outduct need only provide the protocol name and the outduct name as specified on the command line when dccpclo is started. Note also that dccpclo has no fragmentation support at all. Therefore, the largest bundle that can be sent via this convergence layer is limited to just under the link's MTU (typically 1500 bytes). dccpclo is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the Bundle Protocol, and it is terminated by bpadmin in response to an 'x' (STOP) command. dccpclo can also be spawned and terminated in response to START and STOP commands that pertain specifically to the DCCP convergence layer protocol. EXIT STATUS
0 dccpclo terminated normally, for reasons noted in the ion.log file. If this termination was not commanded, investigate and solve the problem identified in the log file and use bpadmin to restart dccpclo. 1 dccpclo terminated abnormally, for reasons noted in the ion.log file. Investigate and solve the problem identified in the log file, then use bpadmin to restart dccpclo. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: dccpclo can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No memory for DCCP buffer in dccpclo. ION system error. Check errtext, correct problem, and restart dccpclo. No such dccp duct. No DCCP outduct matching local_hostname and local_port_nbr has been added to the BP database. Use bpadmin to stop the DCCP convergence-layer protocol, add the outduct, and then restart dccpclo. CLO task is already started for this duct. Redundant initiation of dccpclo. dccpclo can't get IP address for host. Operating system error. Check errtext, correct problem, and restart dccpclo. dccpclo can't create thread. Operating system error. Check errtext, correct problem, and restart dccpclo. CLO can't open DCCP socket. This probably means DCCP is not supported on your system. Operating system error. This probably means that you are not using an operating system that supports DCCP. Make sure that you are using a current Linux kernel and that the DCCP modules are being compiled. Check errtext, correct problem, and restart dccpclo. CLO can't initialize socket. Operating system error. Check errtext, correct problem, and restart dccpclo. CLO send() error on socket. Operating system error. Check errtext, correct problem, and restart dccpclo. Bundle is too big for DCCP CLO. Configuration error: bundles that are too large for DCCP transmission (i.e., larger than the MTU of the link or 65535 bytes--whichever is smaller) are being enqueued for dccpclo. Change routing or use smaller bundles. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5), dccpcli(1) perl v5.14.2 2012-05-25 DCCPCLO(1)