Workflow
NNCP consists of several utilities. As a rule you will have the
following workflow:
- Run nncp-cfgnew on each node to create an initial
configuration file.
- Tune it up and set at least spool and log paths.
- Share your public keys and reachability addressees with your
neighbours. Add their keys to your configuration file and do any other
required configuration about their reachability, permissions of file or
freq transmission.
- Use nncp-file, nncp-freq, nncp-exec
(look how Postfix and how Exim SMTP servers
could be configured) commands to queue file, freq and exec
transmissions. Repeat as many times any time as you wish.
- Depending on connection methods, either:
- run nncp-daemon to accept remotely initiated connections
to your node
- run either nncp-call or nncp-caller to initiate
connection to required nodes from time to time
- use nncp-xfer with removable storage devices for copying
packets to/from other nodes
- use nncp-bundle with either sequential storage devices
or broadcasting transmissions for copying packets
- After successful packet exchanging (or just simply from time to
time), run nncp-toss for tossing (decrypting and processing) all
inbound queues to receive exec messages, files, file requests and relay
transition packets to other nodes.
- If you wish to encrypt your configuration file containing your
private keys, then use nncp-cfgenc utility. You can always use an
encrypted config without decrypting it in temporary memory file.
- If you wish to strip off any private keys from your config, then
use nncp-cfgmin utility. It will be useful for transferring
messages with offline methods, but tossing them later on the machine
with private keys.