Basic Services

These services comprise a backbone of core services for peer-to-peer applications to use.

• STATISTICS — Runtime statistics publication
  • Statistics retrieval
  • Setting statistics and updating them
  • Watches
    • The STATISTICS Client-Service Protocol
  • Statistics retrieval
  • Setting and updating statistics
  • Watching for updates
• ATS — Automatic transport selection
• TRANSPORT — Overlay transport management
  • Address validation protocol
  • NAT library
  • Distance-Vector plugin
  • SMTP plugin
  • Why use SMTP for a peer-to-peer transport?
  • How does it work?
  • How do I configure my peer?
  • How do I test if it works?
  • How fast is it?
  • Bluetooth plugin
  • What do I need to use the Bluetooth plugin transport?
  • How does it work2?
  • What possible errors should I be aware of?
  • How do I configure my peer2?
  • How can I test it?
  • The implementation of the Bluetooth transport plugin
    • Linux functionality
    • THE INITIALIZATION
    • THE LOOP
    • Details about the broadcast implementation
    • Pending features
  • WLAN plugin
• TRANSPORT-NG — Next-generation transport management
  • Design goals of TNG
  • HELLO-NG
  • Priorities and preferences
  • Communicators
• HOSTLIST — HELLO bootstrapping and gossip
  • HELLOs
  • Overview for the HOSTLIST subsystem
    • Features
    • HOSTLIST - Limitations
  • Interacting with the HOSTLIST daemon
  • Hostlist security address validation
    • The HTTP Server
    • Advertising the URL
  • The HOSTLIST client
    • Bootstrapping
  • Usage
• PEERINFO — Persistent HELLO storage
  • PEERINFO - Features
  • PEERINFO - Limitations
  • DeveloperPeer Information
  • Startup
  • Managing Information
  • Obtaining Information
  • The PEERINFO Client-Service Protocol
    • Connecting to the PEERINFO Service
    • Adding Information to the PEERINFO Service
    • Obtaining Information from the PEERINFO Service
• PEERSTORE — Extensible local persistent data storage
  • Functionality
  • Architecture
• CORE — GNUnet link layer
  • When is a peer "connected"?
  • The CORE Client-Service Protocol
    • Setup2
    • Notifications
    • Sending
  • The CORE Peer-to-Peer Protocol
    • Creating the EphemeralKeyMessage
    • Establishing a connection
    • Encryption and Decryption
    • Type maps
• NSE — Network size estimation
  • Motivation
    • Example
    • Algorithm
    • Target value
    • Timing
    • Controlled Flooding
    • Calculating the estimate
    • Results
    • Examples
  • The NSE Client-Service Protocol
  • The NSE Peer-to-Peer Protocol
• DHT — Distributed Hash Table
  • Block library and plugins
    • What is a Block?
    • The API of libgnunetblock
    • Queries
    • Sample Code
    • Conclusion2
    • GET
    • PUT
    • MONITOR
    • DHT Routing Options
  • The DHT Client-Service Protocol
    • PUTting data into the DHT
    • GETting data from the DHT
    • Monitoring the DHT
  • The DHT Peer-to-Peer Protocol
    • Routing GETs or PUTs
    • PUTting data into the DHT
    • GETting data from the DHT
• REGEX — Service discovery using regular expressions
  • How to run the regex profiler
• CADET — Confidential Ad-hoc Decentralized End-to-end Transport
• RPS — Random peer sampling
  • Brahms