This page has three main sections. (Note that the listings could be empty.) moreā€¦ Tip: Remember the back-button! And don't click the number on the left.

  1. The first item displays a term, URL, text or picture.
  2. Followed by a (still unordered) listing of statements about this subject. (for details follow ">"-link)
  3. Separated by a horizontal rule a "reverse" listing of statements referring to this item in object position.

System Monitor


The system monitor and control panel is a simple browser based interface for common administrative operations on the local peer. The monitor is by default either as user named "system" or within the "system" user under the name of "system".

System Monitor & Control: Tabs


A simple, native thread listing of the implementation.

Depending on the underlying language and implementation this listing looks very different.



This allows to supply a URL for the initial connect to a network. (Normally a one-time operation.)

host map

The current map from known host identifiers to network addresses.


A listing of network addresses.

The connections listing is concerned exclusively with values gathered from the currently running peer (process).


  • host: the other peer
  • left:difference of used vs. allowed number of connections active number of active (reusable) connections
  • speed: two sub-columns: total avg and recent avg of the time difference between echo messages sent to host and ready messages received. min, max upper and lower limits of speed.
  • s: connection state

    char description
    - unreachable
    # trying to connect
    > fully reachable (can connect at any time; aka. not firewalled)
    < one-way connected; persistent incoming connection exists, outgoing connections will fail (aka. firewalled)
  • age: seconds since last refresh of this entry


An example how the local map of connected hosts would look as a DNS zome file.

That's so far not actually used.


Management interface for local users.


Displays of the local X509 certificate and the certification authority in use.

For authorized users: includes forms to manage these certificates.


Certificate Management: forms to aid the handling of certificate requests.

user debug

A protocol of the last debug messages generated from the user debug facility.


Very system dependent means to view some currently collected profile information of the peer.

do we need this link?
documentation comment