bssfw(1) [debian man page]

BSSFW(1)							  BP executables							  BSSFW(1)

NAME

       bssfw - bundle route computation task for the IPN scheme, adapted for Bundle Streaming Service

SYNOPSIS

       bssfw

DESCRIPTION

       bssfw is a background "daemon" task that pops bundles from the queue of bundle destined for IPN-scheme endpoints, computes proximate
       destinations for those bundles, and appends those bundles to the appropriate queues of bundles pending transmission to those computed
       proximate destinations.

       For each possible proximate destination (that is, neighboring node) there is a separate queue for each possible level of bundle priority:
       0, 1, 2.  Each outbound bundle is appended to the queue matching the bundle's designated priority.

       Proximate destination computation is affected by static and default routes as configured by bssadmin(1) and by contact graphs as managed by
       ionadmin(1) and rfxclock(1).  bssfw differs from ipnfw in this way: a bundle that is destined for an endpoint associated with a BSS
       application (as registered in an "entry" passed to bssadmin(1) in a bssrc(5) command) is forwarded via a duct identified in a separately
       defined real-time or playback duct expression, rather than the standard duct that is used for non-BSS traffic.

       bssfw is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of Bundle Protocol on the local ION
       node, and it is terminated by bpadmin in response to an 'x' (STOP) command.  bssfw can also be spawned and terminated in response to START
       and STOP commands that pertain specifically to the IPN scheme.

EXIT STATUS

       0   bssfw terminated, for reasons noted in the ion.log log file.  If this termination was not commanded, investigate and solve the problem
	   identified in the log file and use bpadmin to restart bssfw.

       1   bssfw could not commence operations, for reasons noted in the ion.log log file.  Investigate and solve the problem identified in the
	   log file, then use bpadmin to restart bssfw.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       The following diagnostics may be issued to the ion.log log file:

       bssfw can't attach to BP.
	   bpadmin has not yet initialized BP operations.

       bssfw can't load routing database.
	   bssadmin has not yet initialized the IPN scheme.

       Can't create lists for route computation.
	   An unrecoverable database error was encountered.  bssfw terminates.

       'bss' scheme is unknown.
	   The IPN scheme was not added when bpadmin initialized BP operations.  Use bpadmin to add and start the scheme.

       Can't take forwarder semaphore.
	   ION system error.  bssfw terminates.

       Can't exclude sender from routes.
	   An unrecoverable database error was encountered.  bssfw terminates.

       Can't enqueue bundle.
	   An unrecoverable database error was encountered.  bssfw terminates.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       bpadmin(1), bssadmin(1), bprc(5), bssrc(5).

perl v5.14.2							    2012-05-25								  BSSFW(1)

Check Out this Related 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)

Linux and UNIX Man Pages

bssfw(1) [debian man page]

Check Out this Related Man Page