Prologue

Introduction Core concepts Block data & operations Secure & Private by default How it works

Quick Start

Overview Windows Linux MacOS Android Router

Run App on ĐNET

Run Tinc-VPN on ĐNET Tinc-VPN Introduction Tinc App Driver Tinc OVC Driver Executables Download Data Files Folder DNetDB Structure Node Roles DNet Owner Node OVC Owner Node OVC Cloud Instance App User Node

Port App to ĐNET

Port Tinc-VPN to ĐNET Build From Source DNetDB CRUD OVC Implementation App Implementation App command line

Working with data

DNet Record OVC Record

Help

Prerequisites How to upgrade Troubleshooting FAQ

OVF Cloud Instance

The ovf cloud instance is registrated in DNetDB with its Public IP address and Public Key.

The Overlay Foundation (OVF) is the cloud backend for the dnet. The Tinc VPN node is configured as server with 50069 port open listening for incoming protocol messages from the Tinc VPN App. The Tinc enduser node retrieves the ovf info from block chain and has a configuration item ConnectTo pointing to this OVF Public Address or domain name.

A public IP address is needed for ovf node, and it can be:

  • a static public IP address or domain name or
  • a Dynamic DNS domain name or
  • port forward on router.

The DNet Driver automatically pulls the authroized dnet list from blockchain every 100 seconds and add the nodes' PubKey to ovf instance's hosts folder.

Edit this page on GitHub