udpclo
UDP-based BP convergence layer output task
- Provided by: ion (Version: 3.2.1+dfsg-1.1)
- Report a bug
UDP-based BP convergence layer output task
udpclo
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.
No configuration files are needed.
No environment variables apply.
The following diagnostics may be issued to the ion.log log file:
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>