cjdns — selected stack

IPv4 / UDP / cjdns / IPv6 / application UDP; ordinary application path without custom route-label overrides; outer point-to-point CryptoAuth enabled; numeric peers, known keys/local credentials, numeric application destinations; independent deployment uses private IPv4; independent logical-node keys and non-identifying peer credentials per context; transit traffic-history logging/export disabled; C02 includes documented DHT lookup role; no selected cover-traffic policy; private peering credentials, no public beacon advertisement; replicated route-server design with TCP/HTTP/WebSocket announcement exchange, independent servers and numeric contacts; C08 covers transit forwarding, not route-server query caches; F21: applications on native cryptographic node addresses, no imported IP tunnels; trusted local receive interface F37/F38: optional local AQM and DiffServ classification/conditioning explicitly selected on existing private-IP peering egress interfaces, including host-side network queues. Independent owners control their own link resources; no new Internet transit, global underlay, application reservation or inner-packet inspection is added.

Official project website · Logo credits · Methodology and limits