tcpclo(1) [debian man page]
TCPCLO(1) BP executables TCPCLO(1) NAME
tcpclo - DTN TCPCL-compliant convergence layer adapter output task SYNOPSIS
tcpclo remote_hostname[:remote_port_nbr] DESCRIPTION
tcpclo is a background "daemon" task that connects to a remote node's TCP socket at remote_hostname and remote_port_nbr. It sends a contact header, and it records the acknowledgement flag, reactive fragmentation flag and negative acknowledgements flag in the contact header it receives from its peer tcpcli task. 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 message type, segmentation flags, and an SDNV indicating the size of the bundle (in bytes). If not specified, remote_port_nbr defaults to 4556. Note that tcpclo 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 tcpclo is started. tcpclo 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. tcpclo can also be spawned and terminated in response to START and STOP commands that pertain specifically to the TCP convergence layer protocol. EXIT STATUS
0 tcpclo 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 TCPCL protocol. 1 tcpclo 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 TCPCL 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: tcpclo can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No such tcp duct. No TCP outduct with duct name matching remote_hostname and remote_port_nbr has been added to the BP database. Use bpadmin to stop the TCP convergence-layer protocol, add the outduct, and then restart the TCP protocol. CLO task is already started for this duct. Redundant initiation of tcpclo. Can't get IP address for host Operating system error. Check errtext, correct problem, and restart TCP. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5), tcpcli(1) perl v5.14.2 2012-05-25 TCPCLO(1)
Check Out this Related Man Page
UDPCLO(1) BP executables UDPCLO(1) NAME
udpclo - UDP-based BP convergence layer output task SYNOPSIS
udpclo DESCRIPTION
udpclo is a background "daemon" task that extracts bundles from the queues of bundles ready for transmission via UDP to remote bundle protocol agents, encapsulates them in UDP datagrams, and sends those datagrams to the appropriate remote UDP sockets as indicated by the host names and UDP port numbers (destination induct names) associated with the bundles by the routing daemons that enqueued them. Note that udpclo is a "promiscuous" CLO daemon, able to transmit bundles to any UDP destination induct. Its duct name is '*' rather than the induct name of any single UDP destination induct to which it might be dedicated, so scheme configuration directives that cite this outduct must provide destination induct IDs. For the UDP convergence-layer protocol, destination induct IDs are identical to induct names, i.e., they are of the form local_hostname[:local_port_nbr]. udpclo 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. udpclo can also be spawned and terminated in response to START and STOP commands that pertain specifically to the UDP convergence layer protocol. EXIT STATUS
0 udpclo 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 udpclo. 1 udpclo 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 udpclo. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: udpclo can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No memory for UDP buffer in udpclo. ION system error. Check errtext, correct problem, and restart UDP. No such udp duct. No UDP outduct with duct name '*' has been added to the BP database. Use bpadmin to stop the UDP convergence-layer protocol, add the outduct, and then restart the UDP protocol. CLO task is already started for this engine. Redundant initiation of udpclo. CLO can't open UDP socket Operating system error. Check errtext, correct problem, and restart udpclo. CLO write() error on socket Operating system error. Check errtext, correct problem, and restart udpclo. Bundle is too big for UDP CLA. Configuration error: bundles that are too large for UDP transmission (i.e., larger than 65535 bytes) are being enqueued for udpclo. Change routing. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5), udpcli(1) perl v5.14.2 2012-05-25 UDPCLO(1)