Русская версия Hrvatski Svenska Ελληνικά Deutsch 繁體中文 Español Français
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.
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
<DuoNoxSol> even though it really really shouldn't be
<DuoNoxSol> seeing as the connections are largely over 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
Hyperboria is the largest cjdns network, with hundreds of active nodes around the world.
Cjdns has been tested on x86, amd64, ARMv5, ARMv7, MIPS, and PowerPC. It's continually tested on Linux, FreeBSD, OS X, Windows and Illumos systems.
The protocols and algorithms are experimental and subject to change. To minimize the harm to the network, please update your cjdns nodes often.
We are in need of some buildbots on more obscure systems and architectures.
If you would like to donate one, you could mail it, or you could administer
it and provide remote shell access. Please email [email protected]
if you'd like to run a buildbot. Note that it is not a general support inbox,
other questions should be directed toward IRC.
In a cjdns network, a packet goes to a router and the router labels the packet with directions to the router best able to handle it. That is, a router which is physically nearby and has an address numerically close to the destination address of the packet. The directions are added to the packet to allow it to go through a number of routers with minimal handling, a verifiable form of source routing. They just read the label and bounce the packet wherever the next bits in the label tell them to. Routers have a responsibility to "keep in touch" with other routers that are physically close by and numerically near to their address.
The router engine is a modified implementation of the Kademlia distributed hash table. 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
- irc://irc.efnet.org/#cjdns
- Hyperboria the largest cjdns network, as of October 2015 there are 2100 nodes.
- irc://irc.efnet.org/#cjdns (web client)
- Hyperboria
- [Project Meshnet][]
- /r/darknetplan
- #cjdns on Twitter
Advanced configuration:
Thank you for your time and interest,
The cjdns developers.
These instructions are for Debian-based 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.
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.
sudo apt-get install nodejs git build-essential python2.7
sudo dnf install nodejs git
sudo dnf install @development-tools
sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum install nodejs git
sudo yum install @development-tools
Building from package:
sudo yum localinstall https://kojipkgs.fedoraproject.org//packages/cjdns/17.4/4.el6/src/cjdns-17.4-4.el6.src.rpm
If you are on a laptop and suspend or hibernate it, cjdroute will take a few minutes to make coffee and figure out what just happened when it wakes up. You can speed this up dramatically with:
systemctl enable cjdns-resume
The resume service restarts cjdns when the system wakes up from sleep.
emerge --ask nodejs sys-devel/gcc dev-lang/python:3.4 dev-vcs/git
Install with Homebrew:
brew install cjdns
Install with MacPorts:
sudo port install cjdns
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
cjdns is not yet in the main Gentoo repository, so you will have to use an overlay. The easiest way is to use Layman but you can do it by hand, too.
First, you need to install layman.
emerge layman
If layman is installed correctly, you can add the overlay
layman -f
layman -a weuxel
For future update of the overlay use
layman -S
Now you can install cjdns
emerge cjdns
You will have to clone the overlay repository
cd /opt
git clone https://github.com/Weuxel/portage-weuxel.git
Now tell portage to use this repo
cd /etc/portage/repos.conf/
Create a file portage-weuxel.conf containing
[weuxel]
location = /opt/portage-weuxel
masters = gentoo
auto-sync = yes
Now sync
emerge --sync
And install cjdns
emerge cjdns
Copy the the openrc init script from contrib/openrc to /etc/init.d/ and modify the CONFFILE and command parameter to your needs.
Then start cjdns by issuing
/etc/init.d/cjdns start
Configure the init system to autostart cjdns
rc-update add cjdns default
Copy the service_restart script contrib/gentoo/service_restart.sh to any convenient directory on
your system and modify the eMail address. If you do not wish to be notified, comment out the whole line.
Now add a crontab entry like this
-
-
-
-
-
root /path/to/script/service_restart.sh
-
-
-
-
Dependencies:
sudo eopkg install nodejs git build-essential system.devel python gcc binutils kernal-headers xorg-server-devel
Then Follow the steps below:
Sorry for so many steps. A package is being worked on currently
Clone the repository from GitHub and change to the source directory:
git clone https://github.com/cjdelisle/cjdns.git cjdns
cd cjdns
./do
Look for Build completed successfully, type ./cjdroute to begin setup., then
proceed below:
Run cjdroute without options for HELP:
./cjdroute
If you're on macOS, don't worry about 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.
./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)
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:
- 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.
- 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.
- 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.
To initiate the connection OUTbound
In your conf file, you will see:
// Nodes to connect to.
"connectTo":
{
// 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.
"connectTo":
{
//friend_1 (IPv4: 0.1.2.3; IPv6 fcaa:5bac:66e4:713:cb00:e446:c317:fc39)
"0.1.2.3:45678":
{
"login": "k.alexander"
"password": "thisIsNotARealConnection_1",
"publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"
},
//friend_2 (IPv4: 5.1.2.3; IPv6 fcbb:5bac:66e4:713:cb00:e446:c317:fc39)
"5.1.2.3:5678":
{
"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:
"authorizedPasswords":
[
// A unique string which is known to the client and server.
{"password": "password001", "login": "default-login"}
// More passwords should look like this.
// {"password": "password002", "login": "my-second-peer"}
// {"password": "password003", "login": "my-third-peer}
// {"password": "password004", "login": "my-fourth-peer"}
...
// "your.external.ip.goes.here:45678":{"login": "default-login", "password": "password001","publicKey":thisisauniqueKEY_001.k"}
],A conf file with multiple friend-nodes, setup INbound, should look like:
"authorizedPasswords":
[
// 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: 0.1.2.3; IPv6 fcaa:5bac:66e4:713:cb00:e446:c317:fc39)
{"password": "thisisauniquestring_002", "user": "William Jevons"}
//Marilyn Patel (IPv4: 5.1.2.3; IPv6 fcbb:5bac:66e4:713:cb00:e446:c317:fc39)
{"password": "thisisauniquestring_003", "user": "Marilyn Patel"}
// {"password": "thisisauniquestring_004"}
...
// "your.external.ip.goes.here:45678":{"password": "thisisauniquestring_001","publicKey":thisisauniqueKEY_001.k"}
],You need to give William Jevons (who is making the INbound connection) the following 4 items:
-
Your external IPv4
-
The port found in your conf file here:
// Bind to this port. "bind": "0.0.0.0:yourportnumberishere", -
Their unique password that you uncommented or created:
"password": "thisisauniquestring_002" -
Your public key:
"publicKey": "thisisauniqueKEY_001.k" -
His username: "William Jevons"
His login credentials will look something like this (with your IPv4 and port):
"1.2.3.4:56789": {
"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/configure.md for more details on configuration, including how to peer with other cjdns nodes over ethernet and wifi.
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.
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.
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.
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.
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:
- Don't report in this repo, please instead report it at https://github.com/hyperboria/bugs/issues
- Get on IRC and talk to somebody
- 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.
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: https://github.com/cjdelisle/cjdns/blob/master/doc/security_specification.md to see if a possible security issue is really a security issue.
That time of year again... Time for some open source Projects!
