HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cjdelisle
cjdns
C2011–2025
cjdelisle / cjdns

cjdns

An encrypted IPv6 network using public-key cryptography for address allocation and a distributed hash table for routing.

74Distinct people
85Mentions
3Explicit recommenders
5.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An encrypted IPv6 network using public-key cryptography for address allocation and a distributed hash table for routing.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I highly recommend reading the excellent draft document from Usenet at the URL I posted, particularly the example of the "Western Wisconsin Computer Company". It is much…

feelin_googley used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year85 dated mentions

Observed mentions: 2011-04-10 19:41:09 UTC to 2025-06-23 14:40:46 UTC.

0510152011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 15 mentions; 1 submissions, 14 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC110
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC633
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC11110
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC12210
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC817
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC15114
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC404
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC927
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC211

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
cjdns Русская версия Hrvatski Svenska Ελληνικά Deutsch 繁體中文 简体中文 Español Français Português brasileiro Networking Reinvented Cjdns implements an encrypted IPv6 network using public-key cryptography for address allocation and a distributed hash table for routing. This provides near-zero-configuration networking, and prevents many of the security and scalability issues that plague existing networks. Testimonials 23:26 <@jercos> well, cjdns is now officially more reliable than the open internet for getting to my cheaper VPSes :| 12:52 < mariner> so i don't know if it's been done before, and i assume it's obvious, but I think it's neat. Currently on hype from an airplane 00:36 < tester> man sites take so long to load on i2p 00:36 < tester> i value speed over anonymity any day <DuoNoxSol> it's notably more reliable than the normal internet 09:46 < Kubuxu> I so love cjdns code base <whyrusleeping> my internet is way better now. <whyrusleeping> thanks <whyrusleeping> i'm really upset and sad that its better <whyrusleeping> but also quite happy 21:01 <@grewalsat> this is amazing. with my workpalce speedtest.net results I get around 6+mb speed, and with my cjdns-gate as vpn network I'm getting like 11-15mb download speed in speedtest.net 21:01 <@grewalsat> :P 21:01 <@grewalsat> plus, access anything! :D <davidar> Yeah, I have to admit I sort of avoided hypeirc because of stuff like that Community irc://irc.efnet.org/#cjdns Documentation Project Goals Cjdns Whitepaper Advanced configuration: Setup a cjdns NAT gateway for your LAN Thank you for your time and interest, The cjdns developers. How to install cjdns These instructions are for Linux distributions and macOS. They should be informative enough for use on other distributions - just don't expect them to work verbatim. If you want to know what operating system's base is go here. Option 1: Using cjdns.sh If you're on Linux with an amd64 processor (if you don't know your processor, it's amd64), you can install cjdns pre-built binaries using cjdns.sh. See: https://github.com/cjdelisle/cjdns.sh for more information. Option 2: Build from source In order to compile cjdns, you must have: Rust NodeJS (used for building the C code) GCC or Clang C compiler Make (used for compiling one of the Rust dependencies) Git (to checkout this repository) 0. Install dependencies Debian-based distro: sudo apt-get install nodejs git build-essential curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh Redhat-based distro: sudo dnf install nodejs git sudo dnf install @development-tools curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh MacOS: Check that you have clang activated: xcode-select --install Install with Homebrew: brew install node git make curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh 1. Retrieve cjdns from GitHub Clone the repository from GitHub and change to the source directory: git clone https://github.com/cjdelisle/cjdns.git cjdns cd cjdns 2. Build ./do Look for Build completed successfully, type ./cjdroute to begin setup., then proceed below: Setup Run cjdroute without options for HELP: ./cjdroute 0. Make sure you've got the stuff. If you're on macOS, skip this step. LANG=C cat /dev/net/tun If it says: cat: /dev/net/tun: File descriptor in bad state Good! If it says: cat: /dev/net/tun: No such file or directory, create it using: sudo mkdir -p /dev/net && sudo mknod /dev/net/tun c 10 200 && sudo chmod 0666 /dev/net/tun Then cat /dev/net/tun again. If it says: cat: /dev/net/tun: Permission denied You're probably using a VPS based on the OpenVZ virtualization platform. Ask your provider to enable the TUN/TAP device - this is standard protocol so they should know exactly what you need. 1. Generate a new configuration file ./cjdroute --genconf | sudo tee -a /etc/cjdroute.conf Protect your conf file! A lost conf file means you lost your password and connections and anyone who connected to you will no longer be able to connect. A compromised conf file means that other people can impersonate you on the network. 2. Secure your system - check for listening services Once your node is running, you're now a newly minted IPv6 host. Your operating system may automatically reconfigure network services to use this new address. If this is not what you intend, you should check to see that you are not offering more services than you intended to. ;) See doc/network-services.md for instructions. 3. Start it up! sudo ./cjdroute < /etc/cjdroute.conf If you want to have your logs written to a file: sudo ./cjdroute < /etc/cjdroute.conf > cjdroute.log To stop cjdns: sudo killall cjdroute If you are having problems use killall cjdroute to return to sanity. Use pgrep cjdroute or top to see if it running. NOTE! This starts cjdns as the root user so it can configure your system without concern for permissions. To start cjdns as a non-root user, see doc/non-root-user.md. Custom peering By default, cjdns will reach out to a DNS seeder to find peers and will automatically connect to them. This of course exposes the fact that you're running cjdns to the operators of these nodes. If you're planning on running a "clandestine" cjdns node, find the dnsSeeds section of the configuration and comment it out. Then take the peering credentials of a node you would like to connect to and add them to the UDPInterface / connectTo section of the cjdroute.conf. See doc/peering.md Admin interface When cjdroute is up and running, the admin interface will be available at udp://localhost:11234 (this can be changed in the cjdroute.conf configuration file). See doc/admin-api.md for more information about the admin interface. There are several tools in contrib/ that can interact with it. You can access the admin API with: ./cjdnstool The Python library; see here. The Perl library, maintained by Mikey; see here. Reporting issues Don't report in this repo, please instead report it at ht
Read the full README on GitHub

What Hacker News says

9 sources
I kind of hope the next 'net is based on cjdns, because it's a much better protocol and it's fundamentally less centralised. If the new ISPs evolved from Hyperboria, it'd be a dream come true. There are still some bugs, though (like the horizon issue limiting the usability of convoluted or large networks: https://github.com/cjdelisle/cjdns/blob/master/doc/bugs/hori...) but it's enough that people using the network don't really need to fix them, since everything still works. If you want to help out with the code, it's probably best to look at the bugs repo (https://github.com/hyperboria/bugs/issues); the issues in the "bugs" directory of cjd's repo are mostly large, architectural issues and non-trivial flaws that are probably due to the implementation.
In AT&T drops out of FCC speed-test program so it can hide bad results
Reminder: initiatives like Hyperboria (formerly Project Meshnet) exist. Using the cjdns protocol and some communications medium (e.g. wires, line-of-sight microwave, WLAN, IPoCP), you can become the ISP for your own local area, assigning IPv6 addresses and providing a bridge (or many) to the 'net at large. The various pages on the topic aren't well linked (due to server migrations, name changes, low attention to marketing… you know how devs are), but the main homepage is https://hyperboria.net/, some installation guides can be found at https://projectmeshnet.org/docs/ (which mostly links to https://github.com/cjdelisle/cjdns#how-to-install-cjdns) and generic, somewhat complete documentation is https://docs.meshwith.me/. cjdns has some other neat features, which are outlined in its whitepaper: https://docs.meshwith.me/Whitepaper.html
In AT&T drops out of FCC speed-test program so it can hide bad results
Is there a specific bug or missing feature that has you frustrated in that project? And also, note that yeah they last pushed to master in August, but they've been doing work since then on at least one other branch. https://github.com/cjdelisle/cjdns/tree/crashey Software should mature and when it does, development should slow down. I don't use cjdns myself, but from what I've heard it seems to be a solid piece of software. If you had personally submitted a PR to the project and it was sitting there unacknowledged, or you were seeing lots of PRs by others sitting unresponded to then I could see a reason for being frustrated. But there are only two open PRs at the moment, and only one of them is without any comments.
In Lack of cdnjs activity
I ran cjdns for 5 years but recently switched off it. For one, it seemed to have too much traffic over my limited outbound link when things should have been more idle. Also, the commit logs were a little unnerving to me for code I'm trusting with my network security: All kinds of "oops" edits: https://github.com/cjdelisle/cjdns/commit/3abe50b8e744f72696... https://github.com/cjdelisle/cjdns/commit/feabb1970fbaecf65c... https://github.com/cjdelisle/cjdns/commit/c51d89431f1fa42955... https://github.com/cjdelisle/cjdns/commit/1b0c999bd2e5988c3f... https://github.com/cjdelisle/cjdns/commit/355d7d77cc82c52bf1... (function args passed in the wrong order) Some are about extra traffic: https://github.com/cjdelisle/cjdns/commit/8bcfbf227a87020931... https://github.com/cjdelisle/cjdns/commit/0ee9cb7f45b466232b... Also it's ipv6 only, which took som
Read the rest
e fussing. Performance was fine, even on rpi. Reestablishing links was slow and sometimes required restarting of the daemon. Daemons would occasionally get wedged. Log output is unconventional and uses a special reader tool (a la adb for android). Occasionally routes wouldn't be chosen right (two home computers would route via an external cloud box), which I'd fix by restarting the right daemons. I laboriously switched to openvpn (two networks) and haven't worked out all the routing and hotswitching for my roaming phone+laptop yet. Now I'm considering vita, tinc, zerotier, or wireguard. Probably I'll try out zerotier to see if it works out of the box, then try wireguard if I'm going to have to configure it a lot, since it seems like WG is the most unix-toolbox-do-one-thing out of all of them.
In Vita: simple and fast VPN gateway
you've clearly not used any of the modern roaming-enabled encrypted overlay networks that people have been working on. one example is hyperboria. i connect to a handful of public relays (and one that i host myself) and no matter where i am my device is reachable at the same ip address. the address is an ipv6-encoded hash of the public key that is used for routing. its actually really neat, and you don't need to wait more than a few seconds for the routing tables to update if you change locations. https://hyperboria.net/ https://github.com/cjdelisle/cjdns/
In Re-decentralizing the Web, for good this time

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.