No description, website, or topics provided.
Assembly C Python JavaScript C++ Shell Other
Failed to load latest commit information.
admin Removed usage of NumberCompress, poisoned dht code in SUBNODE and add… Sep 26, 2016
benc First wave of changes to make possible super/sub nodes May 16, 2016
client Merge branch 'master' of git:// into crashey Sep 22, 2016
contrib Merge branch 'patch-1' of git:// into crashey Sep 26, 2016
crypto Remove duplicate function declaration Sep 19, 2016
debian Bump debian package version to 0.17.1 Dec 1, 2015
dht Manually merged faster findBestParent Oct 9, 2016
doc Merge branch 'tunnel-ipv4' of git:// into cra… Oct 11, 2016
exception Change Linker_require() to allow a trailing semicolon Jan 6, 2016
interface TUNInterface_openbsd.c failed codestyle check due to missing whitespace Jun 22, 2016
io Change Linker_require() to allow a trailing semicolon Jan 6, 2016
memory Change Linker_require() to allow a trailing semicolon Jan 6, 2016
net Removed usage of NumberCompress, poisoned dht code in SUBNODE and add… Sep 26, 2016
node_build Add authorizedPasswords generator Sep 24, 2016
node_modules/nthen Remove semver dependency Aug 7, 2014
subnode Removed usage of NumberCompress, poisoned dht code in SUBNODE and add… Sep 26, 2016
switch Removed usage of NumberCompress, poisoned dht code in SUBNODE and add… Sep 26, 2016
test Removed usage of NumberCompress, poisoned dht code in SUBNODE and add… Sep 26, 2016
tools correct error messages on failure Oct 4, 2016
tunnel Merge branch 'tunnel_typo' of git:// into cra… Sep 22, 2016
util Document that the subnode is only optional Oct 11, 2016
wire Switch to 32 byte peer announcement entity, correct path and send a v… Sep 26, 2016
.dockerignore docker: add dockerfile and entrypoint script Nov 15, 2015
.gitignore Ignore mkpasswd from git Sep 25, 2016
.jshintignore Fix Travis CI builds failing because of JSHint May 16, 2014
.travis.yml Test android build too Jul 6, 2016
Dockerfile docker: add dockerfile and entrypoint script Nov 15, 2015 Add note about Valgrind and CII badge Sep 22, 2016
LICENSE Rename gpl-3.0.txt to LICENSE Aug 26, 2013 Merge branch 'patch-3' of git:// into crashey Sep 22, 2016 readme: rename to upper Sep 24, 2016 Merge branch 'debian-install' of git:// into … Sep 22, 2016 Install 'python2.7' instead of 'python' on Debian. Aug 21, 2016 Install 'python2.7' instead of 'python' on Debian. Aug 21, 2016 Install 'python2.7' instead of 'python' on Debian. Aug 21, 2016
android_do Test android build too Jul 6, 2016
clean clean should fail gracefully if the version if git is old Dec 14, 2013
cross-do Fixed cross-do for Bash 3 Jan 13, 2015
do merged new ./do and copied old ./do to ./old_do which will be removed… Mar 3, 2015
package.json Grab this namespace before Jeremy does Jan 20, 2016


Русская версия Hrvatski Svenska Ελληνικά

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.

Build Status CII Best Practices tip for next commit irc


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

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 results I get around 6+mb speed, and with my cjdns-gate as vpn network I'm getting like 11-15mb download speed in
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



Advanced configuration:

Thank you for your time and interest,

The cjdns developers.

How to install cjdns

These instructions are for Debian-based Linux distributions and OS X. They should be informative enough for use on other distributions - just don't expect them to work verbatim.

0. Install dependencies

On both platforms, installing Node.js, although preferable, is not strictly necessary. If Node.js is unavailable or an unacceptable version, it will be downloaded and installed in the source tree.

Debian-based distro:

sudo apt-get install nodejs git build-essential python2.7

Fedora 22+ based distro:

sudo dnf install install nodejs git
sudo dnf install @development-tools

RHEL based distro (adds the EPEL repo):

sudo yum localinstall
sudo yum install install nodejs git
sudo yum install @development-tools


Install with homebrew:

brew install cjdns


Sadly, OpenBSD is a bit experimental right now.

pkg_add git node gcc gmake bash

Select version gcc-4.8.1p2 or more recent.


Everything you need is available prebuild in FreeBSD' ports.

pkg install gmake node


You can install cjdns by running

pacman -S cjdns

If you need to build from source, everything you need can be installed like this

pacman -S nodejs git base-devel

Alternatively, you may like to install via AUR from the package, cjdns-git. After Installation, The configuration file is located at /etc/cjdroute.conf. To start the service cjdns.service, do:

    systemctl start cjdns

To stop it:

   systemctl stop cjdns

1. Retrieve cjdns from GitHub

Clone the repository from GitHub and change to the source directory:

git clone cjdns
cd cjdns

2. Build


Look for Build completed successfully, type ./cjdroute to begin setup., then proceed below:


Run cjdroute without options for HELP:


0. Make sure you've got the stuff.

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. If you're on OS X, don't worry about this step.

1. Generate a new configuration file

./cjdroute --genconf >> 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.

To generate a conf file with permissions set so that only your user can read it and write to it:

(umask 077 && ./cjdroute --genconf > cjdroute.conf)

2. Find a friend

To get into an existing network (e.g. Hyperboria), you need to connect to someone who is already in the network. This is required for a number of reasons:

  1. It helps prevent abuse because bad people will be less likely to abuse a system after they were, in an act of human kindness, given access to that system.
  2. This is not intended to overlay The Old Internet, it is intended to replace it. Each connection will in due time be replaced by a wire, a fiber optic cable, or a wireless network connection.
  3. In any case of a disagreement, there will be a "chain of friends" linking the people involved so there will already be a basis for coming to a resolution.

To find a friend, get out there and join our community. Also, have a look at the Hyperboria Map to find peers near you.

3. Connect your node to your friend's node

To initiate the connection OUTbound

In your conf file, you will see:

// Nodes to connect to.
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.

A conf file with multiple friend-nodes, setup OUTbound, should look like:

// Nodes to connect to.
    //friend_1 (IPv4:; IPv6 fcaa:5bac:66e4:713:cb00:e446:c317:fc39)
        "login": "k.alexander"
        "password": "thisIsNotARealConnection_1",
        "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"

    //friend_2 (IPv4:; IPv6 fcbb:5bac:66e4:713:cb00:e446:c317:fc39)
        "login": "k.alexander"
        "password": "thisIsNotARealConnection_2",
        "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_2.k"

You can add as many connections as you want to the connectTo attribute, following JSON syntax.

To allow your friend to initiate the connection INbound

In your conf file, you will see:

    // A unique string which is known to the client and server.
    {"password": "thisisauniquestring_001"}

    // More passwords should look like this.
    // {"password": "thisisauniquestring_002"}
    // {"password": "thisisauniquestring_003"}
    // {"password": "thisisauniquestring_004"}

    // "":{"password": "thisisauniquestring_001","publicKey":thisisauniqueKEY_001.k"}


A conf file with multiple friend-nodes, setup INbound, should look like:

    // A unique string which is known to the client and server.
    {"password": "thisisauniquestring_001", "user": "k.alexander"}

    // More passwords should look like this.
    //William Jevons (IPv4:; IPv6 fcaa:5bac:66e4:713:cb00:e446:c317:fc39)
    {"password": "thisisauniquestring_002", "user": "William Jevons"}
    //Marilyn Patel (IPv4:; IPv6 fcbb:5bac:66e4:713:cb00:e446:c317:fc39)
    {"password": "thisisauniquestring_003", "user": "Marilyn Patel"}
    // {"password": "thisisauniquestring_004"}

    // "":{"password": "thisisauniquestring_001","publicKey":thisisauniqueKEY_001.k"}

You need to give William Jevons (who is making the INbound connection) the following 4 items:

  1. Your external IPv4
  2. The port found in your conf file here:

    // Bind to this port. "bind": "",

  3. Their unique password that you uncommented or created: "password": "thisisauniquestring_002"

  4. Your public key: "publicKey": "thisisauniqueKEY_001.k"
  5. His username: "William Jevons"

His login credentials will look something like this (with your IPv4 and port):

"": {
    "login": "William Jevons",
    "password": "thisisauniquestring_002",
    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"

Please note that you and your friend can initiate a connection either outbound (from YOU --> FRIEND) or inbound (from FRIEND --> YOU) but traffic flows both ways once the connection is established.

See doc/ for more details on configuration, including how to peer with other cjdns nodes over ethernet and wifi.

4. 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 then you intended to. ;)

See doc/ for instructions.

5. Start it up!

sudo ./cjdroute < cjdroute.conf

If you want to have your logs written to a file:

sudo ./cjdroute < 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.


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/

6. Get in IRC

Welcome to the network! You're now a network administrator. There are responsibilities which come with being a network administrator which include being available in case there is something wrong with your equipment. You should stay on IRC so that people can reach you.

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/ 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:

  • the Python library; see here.
  • the Perl library, maintained by Mikey; see here.

Reporting issues

  1. Don't
  2. Get on IRC and talk to somebody
  3. What will happen is either
    • Someone feels like fixing it
    • You feel like fixing it
    • Nobody cares about it and it will be forgotten for a while and maybe someone will hit it later and fix it or else it will get wiped away in a refactoring
    • Nobody can fix it at the moment but it is considered worth remembering because it has great significance to the way the code is developed, in this case it needs to be explained in technical terms by someone with strong familiarity with the code. They will make a pull request to the docs/bugs directory.
    • Alternatively you can report the issue on the repo.


Security issues should be reported on IRC the same as other bugs. We don't have a closed group of people with special knowledge so that means the default security reporting method is full disclosure. see: to see if a possible security issue is really a security issue.