stcpclo(1) [debian man page]
STCPCLO(1) BP executables STCPCLO(1) NAME
stcpclo - DTN simple TCP convergence layer adapter output task SYNOPSIS
stcpclo remote_hostname[:remote_port_nbr] DESCRIPTION
stcpclo is a background "daemon" task that connects to a remote node's TCP socket at remote_hostname and remote_port_nbr. It then begins extracting bundles from the queues of bundles ready for transmission via TCP to this remote bundle protocol agent and transmitting those bundles over the connected socket to that node. Each transmitted bundle is preceded by a 32-bit integer in network byte order indicating the length of the bundle. If not specified, remote_port_nbr defaults to 4556. Note that stcpclo 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 stcpclo is started. stcpclo 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. stcpclo can also be spawned and terminated in response to START and STOP commands that pertain specifically to the STCP convergence layer protocol. EXIT STATUS
0 stcpclo 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 the STCP protocol. 1 stcpclo 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 the STCP protocol. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: stcpclo can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No such stcp duct. No STCP outduct with duct name matching remote_hostname and remote_port_nbr has been added to the BP database. Use bpadmin to stop the STCP convergence-layer protocol, add the outduct, and then restart the STCP protocol. CLO task is already started for this duct. Redundant initiation of stcpclo. Can't get IP address for host Operating system error. Check errtext, correct problem, and restart STCP. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5), stcpcli(1) perl v5.14.2 2012-05-25 STCPCLO(1)
Check Out this Related Man Page
LTPCLO(1) BP executables LTPCLO(1) NAME
ltpclo - LTP-based BP convergence layer adapter output task SYNOPSIS
ltpclo [-]remote_node_nbr DESCRIPTION
ltpclo is a background "daemon" task that extracts bundles from the queues of segments ready for transmission via LTP to the remote bundle protocol agent identified by remote_node_nbr and passes them to the local LTP engine for aggregation, segmentation, and transmission to the remote node. If remote_node_nbr is preceded by a '-' character, then all LTP transmission performed by ltpclo will be "green" (unreliable) transmission, without acknowledgment and retransmission. Note that ltpclo is not a "promiscuous" convergence layer daemon: it can transmit bundles only to the node for which it is configured, so scheme configuration directives that cite this outduct need only provide the protocol name and the outduct name (the remote node number) as specified on the command line when ltpclo is started. ltpclo 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. ltpclo can also be spawned and terminated in response to START and STOP commands that pertain specifically to the LTP convergence layer protocol. EXIT STATUS
0 ltpclo 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 the BRSC protocol. 1 ltpclo 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 the BRSC protocol. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: ltpclo can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No such ltp duct. No LTP outduct with duct name matching remote_node_nbr has been added to the BP database. Use bpadmin to stop the LTP convergence- layer protocol, add the outduct, and then restart the LTP protocol. CLO task is already started for this duct. Redundant initiation of ltpclo. ltpclo can't initialize LTP. ltpadmin has not yet initialized LTP operations. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5), ltpadmin(1), ltprc(5), ltpcli(1) perl v5.14.2 2012-05-25 LTPCLO(1)