# cjdns

[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)
[Português brasileiro](README_PT-BR.md)

#### *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](https://api.travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/387/badge)](https://bestpractices.coreinfrastructure.org/projects/387)
[![tip for next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![irc](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)
![License](https://img.shields.io/github/license/cjdelisle/cjdns.svg)

## 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.freenode.org/#cjdns][IRC Web]
* [Hyperboria][] the largest cjdns network, as of October 2015 there are 2100 nodes.
* [/r/darknetplan][]
* [#cjdns on Twitter][]
* [/r/CJDNS](https://www.reddit.com/r/cjdns/)


## Documentation

* [Project Goals](doc/projectGoals.md)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns on Wikipedia][]

Advanced configuration:

* [Setup a cjdns NAT gateway for your LAN](doc/nat-gateway.md)
* [Install cjdns on OpenIndiana](doc/open-indiana.md)

Thank you for your time and interest,

The cjdns developers.

--------------------------------------------------------------------------------

## How to install cjdns

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](https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg).

### 0. Install dependencies

On both platforms, installing [Node.js](https://nodejs.org/), 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 nodejs git
    sudo dnf install @development-tools

#### RHEL based distro (adds the EPEL repo):

    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.

#### Gentoo

    emerge --ask nodejs sys-devel/gcc dev-lang/python:3.4 dev-vcs/git

#### macOS:

Install with [Homebrew](https://brew.sh/):

    brew install cjdns

Install with [MacPorts](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

    pkg_add git node gcc gmake bash

Select version gcc-4.8.1p2 or more recent.

#### FreeBSD:

Everything you need is available prebuild in FreeBSD' ports.

    pkg install gmake node

#### Arch:

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

#### Gentoo:

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.

##### Layman:

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

##### By hand:

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

#### Automatic crash detection and restart

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

    # Restart crashed Services
    * * * * *       root	/path/to/script/service_restart.sh

#### Solus:

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*

##### 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, 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.


### 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](#community). Also, have
a look at the [Hyperboria Map](https://www.fc00.org/) to find peers near you.

You can also use the geographically assorted list of public peering credentials for joining Hyperboria at [hyperboria/peers](https://github.com/hyperboria/peers).

### 3. Connect your node to your friend's node

**To initiate the connection OUTbound**

In your conf file, you will see:

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

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

``` javascript
"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:
``` javascript
"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:

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

    `// Bind to this port.
    "bind": "0.0.0.0:yourportnumberishere",`

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

```javascript
"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](doc/configure.md) 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 than you intended to. ;)

See [doc/network-services.md](doc/network-services.md) 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.

**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](doc/non-root-user.md).


### 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](#community) 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/admin-api.md](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:

* the **Python library**; see [here](contrib/python/README.md).
* the **Perl library**, maintained by Mikey; see [here](contrib/perl/CJDNS/README).


## Reporting issues
1. Don't report in this repo, please instead report it at https://github.com/hyperboria/bugs/issues
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.

### Security
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: [security_specification.md](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!
[![Hacktoberfest](https://img.shields.io/badge/Open%20Source-Hacktoberfest-orange.svg)](https://hacktoberfest.digitalocean.com/)

[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns on Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: https://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns on Wikipedia]: https://fr.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[English](README.md)
[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)

#### *Netzwerk neu erfunden*

Cjdns implementiert ein verschlüsseltes IPv6 Netzwerk basierend auf Public-Key Kryptografie für die Adressen-Zuteilung und es benutzt eine verteilte Hash-Tabelle für das Routing.
Dies ermöglicht eine nahezu konfigurationslose Handhabung und verhindert viele Sicherheits- und Skalierungs-Probleme, welche andere existierende Netzwerke heimsuchen.

[![Build Status](https://api.travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/387/badge)](https://bestpractices.coreinfrastructure.org/projects/387)
[![tip for next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![irc](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)
![License](https://img.shields.io/github/license/cjdelisle/cjdns.svg)

## 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][IRC Web]
* [Hyperboria][] das grösste cjdns-Netzwerk mit bis zu 2100 Knotenpunkten (Oktober 2015).
* [/r/darknetplan][]
* [#cjdns auf Twitter][]


## Dokumentation

* [Projekt-Ziele](doc/projectGoals.md)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns auf Wikipedia][]

Erweiterte Konfiguration:

* [Installiere ein cjdns NAT gateway für dein LAN](doc/nat-gateway.md)
* [Installiere cjdns auf OpenIndiana](doc/open-indiana.md)

Danke für deine Zeit und dein Interesse,

Die cjdns-Entwickler.

--------------------------------------------------------------------------------

## Installation von cjdns

Diese Anleitungen sind für Debian-basierte Linux-Distributionen und macOS. Sie sollten erklärend genug sein, um sie auch auf anderen Distributionen zu verwenden - wenn auch nicht unbedingt eins-zu-ein.
Wenn du wissen möchtest, [was die Basis deines Betriebssystems ist, klicke hier.](https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg)

### 0. Installations-Abhängigkeiten

Für beide Platformen ist es nicht zwingend notwendig, doch aber vorzuziehen, [Node.js](https://nodejs.org/) zu installieren. Wenn Node.js nicht verfügbar oder eine nicht akzeptierte Version ist, wird es in den Quellpfad heruntergeladen und installiert.

#### Debian basierte Distribution:

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

#### Fedora 22+ basierte Distribution:

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

#### RHEL basierte Distribution (Fügt das EPEL Repository hinzu):

    sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    sudo yum install install nodejs git
    sudo yum install @development-tools

#### Aus dem Paket installieren:

    sudo yum localinstall https://kojipkgs.fedoraproject.org//packages/cjdns/17.4/4.el6/src/cjdns-17.4-4.el6.src.rpm

Wenn du Suspend oder Hibernate auf einem Laptop verwendest wird cjdroute ein paar Minuten brauchen um Kaffee zu machen udn herauszufinden, was eigentlich gerade passiert ist, wenn es aufwacht.
Du kannst das aber dramatisch beschleunigen:

    systemctl enable cjdns-resume

Der Resume Service startet cjdns neu, wenn das System aufwacht.

#### Gentoo

    emerge --ask nodejs sys-devel/gcc dev-lang/python:3.4 dev-vcs/git

#### macOS:

Installation mit [Homebrew](https://brew.sh/):

    brew install cjdns

Installation mit [MacPorts](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

OpenBSD ist momentan leider ein bisschen experimentell.

    pkg_add git node gcc gmake bash

Wähle die Version gcc-4.8.1p2 oder neuer.

#### FreeBSD:

Alles was du benötigst ist als Prebuild im FreeBSD' port bereits vorhanden.

    pkg install gmake node

#### Arch:

Du kannst cjdns mit folgendem Befehl installieren.

    pacman -S cjdns

Wenn du aus den Quellen installieren möchtest, kann alles, was du brauchst hiermit installiert werden.

    pacman -S nodejs git base-devel

Alternativ kannst du per AUR das Packet `cjdns-git` installieren.
Nach der Installation ist die Konfigurationsdatei unter  `/etc/cjdroute.conf` zu finden.
Um den Service `cjdns.service` zu starten, führe

    systemctl start cjdns

 aus.
 Um ihn zu stoppen:

    systemctl stop cjdns

#### Gentoo:

cjdns ist noch nicht im Gentoo Repository, daher muss ein Overlay verwendet werden.
Der einfachste Weg ist Layman zu verwenden, aber man kann das auch händisch machen.

##### Layman:

Als erstes muss Layman installiert werden.

    emerge layman

Wenn Layman korrekt installiert ist, kann man das Overlay hinzufügen.

    layman -f
    layman -a weuxel

In Zukunft kann man folgenden Befehl verwenden um das Overlay zu syncen.

    layman -S

Jetzt kann cjdns installiert werden.

    emerge cjdns

##### Händische Installation:

Zuerst muss das Overlay Repository geklont werden.

    cd /opt
    git clone https://github.com/Weuxel/portage-weuxel.git

Nun bringen wir Portage dazu das Repo zu verwenden.

    cd /etc/portage/repos.conf/

Erstelle eine Datei `portage-weuxel.conf` mit folgendem Inhalt:

    [weuxel]
    location = /opt/portage-weuxel
    masters = gentoo
    auto-sync = yes

Einmal syncen.

    emerge --sync

Und cjdns installieren.

    emerge cjdns

#### Automatische Crash Erkennung und neu starten

Kopiere das OpenRC Init Skript aus `contrib/openrc` nach `/etc/init.d/` und ändere die Variablen `CONFFILE` und `command` nach Bedarf.
Nun starte cjdns mit dem Kommando

    /etc/init.d/cjdns start

Konfigiere das Initsystem cjdns automatisch zu starten

    rc-update add cjdns default

Kopiere das service_restart Skript `contrib/gentoo/service_restart.sh` an eine beliebige, geeignete Stelle im Verzeichnisbaum deines Systems und ändere die eMailadresse. Wenn du keine eMail erhalten willst, wenn der Service neu gestartet wurde, dann kommentiere die komplette Zeile aus.
Nun füge folgenden crontab Eintrag hinzu

    # Restart crashed Services
    * * * * *       root	/path/to/script/service_restart.sh

#### Solus:

Abhängigkeiten:

    sudo eopkg install nodejs git build-essential system.devel python gcc binutils kernal-headers xorg-server-devel

Dann folge den Schritten weiter unten:

*Entschuldigung für so viele Schritte. Es wird gerade an einem Paket gearbeitet.*


### 1. Hole cjdns from GitHub

Klone das Repository von GitHub und wechsle zum Quellverzeichnis:

    git clone https://github.com/cjdelisle/cjdns.git cjdns
    cd cjdns

### 2. Build

    ./do

Es sollte folgendes stehen: `Build completed successfully, type ./cjdroute to begin setup.`. Danach gehe vor wie weiter unten beschrieben:

--------------------------------------------------------------------------------

## Setup

Lasse cjdroute ohne Optionen für HELP laufen:

    ./cjdroute

### 0. Stelle sicher, dass du alles bekommen hast.

Wenn du macOS verwendest, brauchst du Dir über diesen Schritt keine Sorgen machen.

    LANG=C cat /dev/net/tun

Wenn steht: `cat: /dev/net/tun: File descriptor in bad state` Gut!

Wenn steht: `cat: /dev/net/tun: No such file or directory`, erstelle es wie folgt:

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

Danach wieder `cat /dev/net/tun`.

Wenn es sagt: `cat: /dev/net/tun: Permission denied` Dann verwendest du vielleicht einen VPS basierend auf der OpenVZ virtualisations Platform. Frage deinen Provider, ob er das TUN/TAP device - das ist standard Protokoll, sie sollten also genau wissen was du benötigst. Wenn du auf macOS bist, musst du dich nicht um dieses Setup kümmern.


### 1. Erstelle ein neues Konfiguration-File

    ./cjdroute --genconf >> cjdroute.conf

**Schütze dein conf File!**

Ein verlorenes conf File bedeutet, du hast dein Passwort und deine Verbindungen verloren und jeder der sich mit dir verbunden hatte wird nicht länger in der lage sein, sich mit dir zu verbinden.
Ein kompromitiertes conf File bedeutet, dass andere Leute sich mit deiner Identität im Netzwerk ausgeben können.

Um ein conf File mit den richtigen Rechten zu generieren, so dass nur dein User darauf schreiben und lesen kann:

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


### 2. Finde einen Freund

Um in ein existierendes Netzwerk (z.B. Hyperboria) zu gelangen, musst du dich mit jemandem verbinden, der bereits mit diesem Netzwerk verbunden ist. Dies ist wegen verschiedensten Gründen notwendig:

1. Es hilft den Missbrauch zu verhindern, denn schlechte Leute werden tendenziell ein System weniger missbrauchen, wenn ihnen, in einem Akt von menschlicher Freundlichkeit, von anderen der Zugang gewährt wird.
2. Es ist nicht geplant das Alte Internet zu überlagern, sondern es zu ersetzen. Jede Verbindung wird zu gegebener Zeit durch ein Kabel, ein Glasfaser-Kabel oder eine Wireless-Netzwerk-Verbindung ersetzt.
3. Im Falle einer Streitigkeit wird es eine "Kette von Freunden" geben, welche die involvierten Leute verbindet, so dass es bereits eine Basis zu einer Lösungsfindung gibt.

Um einen Freund zu finden, gehe nach draussen und beteilige dich an unserer [Community](#community). Weiter kannst du auch einen Blick auf die [Hyperboria-Karte][] werfen, um Peers in deiner Nähe zu finden.


### 3. Verbinde deinen Knoten mit dem deines Freundes

**Um ein AUSgehende Verbindung herzustellen**

In deinem conf File wirst du folgendes sehen:

``` javascript
// Nodes to connect to.
"connectTo":
{
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.
}
```

Ein conf File mit mehreren konfigurierten Freundes-Knoten (Setup AUSgehende Verbindung) sollte wie folgt aussehen:

``` javascript
// 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"
    }
}
```

In der gegebenen JSON Syntax kannst du so viele Verbindungen wie du willst zum `connectTo` Attribut hinzufügen.


**Um deinem Freund zu erlauben eine EINgehende Verbindung mit dir aufzubauen**

In deinem config File wirst du eine Passage wie folgt finden:

``` javascript
"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"}

],
```

Ein config File mit mehreren Freundes-Knoten (Setup EINgehende Verbindung) sollte wie folgt aussehen:

``` javascript
"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"}
],
```


Du musst William Jevons (welcher die EINgehende Verbindung bei sich einträgt) die folgenden 4 Objekte geben:

1. Deine externe IPv4-Adresse
2. Den Port, welchen du in deinem conf File wie folgt findest:

    `// Bind to this port.
    "bind": "0.0.0.0:yourportnumberishere",`

3. Das speziefische Passwort, welches du unkommentiert oder neu erstellt hast:
`"password": "thisisauniquestring_002"`
4. Deinen Public-Key: `"publicKey": "thisisauniqueKEY_001.k"`
5. Seinen Benutzernamen: "William Jevons"

Seine Zugangsdaten werde dann ungefähr wie folgt aussehen (mit deiner IPv4-Adresse und Port):

```javascript
"1.2.3.4:56789": {
    "login": "William Jevons",
    "password": "thisisauniquestring_002",
    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"
}
```

Bitte beachte, dass du und dein Freund jeweils nur eine AUSgehende (von DIR -> Freund) oder EINgehende (von Freund -> DIR) Verbindung *eintragen* müsst. Der Datenverkehr kann dann aber doch in beide Richtungen fliessen, sobald die Verbindung steht.

Für mehr Details bezüglich Konfiguration, oder wie du mit anderen cjdns-Knoten über Ethernet und Wifi peerst, schaue dir das Dokument [doc/configure.md](doc/configure.md) an.


### 4. Sichere dein System ab - prüfe auf lauschende Services

Wenn dein Knoten einmal läuft, bist du ein neuwertiger IPv6 Host. Dein Betriebssystem wird wahrscheinlich automatisch deine Netzwerk-Services neu konfigurieren, um diese neue Adresse zu verwenden.
Wenn das nicht dein Ziel ist, solltest du überprüfen, dass du nicht mehr Services bereitstellst als du willst. ;)

Schaue dir [doc/network-services.md](doc/network-services.md) an für Anleitungen.


### 5. Starte!

    sudo ./cjdroute < cjdroute.conf

Wenn du deine Logs in ein File geschrieben haben willst:

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

Um cjdns zu stoppen:

    sudo killall cjdroute

Wenn du Probleme hast, benutze `killall cjdroute` um tabula rasa zu machen. Benutze
`pgrep cjdroute` oder `top` um zu überprüfen, ob cjdns läuft.

**Bemerkung!**

Die obigen Anleitungen starten cjdns als root-user. Es kann also dein System konfigurieren ohne dich um erlaubniss zu bitten. Um cjdns als non-root-user zu starten, konsultiere [doc/non-root-user.md](doc/non-root-user.md).


### 6. Komme ins IRC

Willkommen im Netzwerk! Du bist jetzt ein Netzwerk-Administrator. Damit verbunden ist eine gewisse Verantwortung, die unter anderem darin bestehen erreichbar zu sein im Falle eines Problems mit deinen Gerätschaften. Du solltest dich auf [IRC](#community) aufhalten, so dass leute dich erreichen können.


## Admin interface

Wenn cjdroute gestartet wurde und läuft, kannst du das admin-Interface unter `udp://localhost:11234` erreichen (kann im folgenden Konfigurations-File geändert werden: `cjdroute.conf`). Konsultiere [doc/admin-api.md](doc/admin-api.md) für mehr Informationen bezüglich dem admin-Interface. Es gibt mehrere Tools in `contrib/`,
welche damit interagieren können.

Du kannst das admin-API wie folgt erreichen:

* die **Python library**; konsultiere [here](contrib/python/README.md).
* die **Perl library**, unterhalten by Mikey; konsultiere [here](contrib/perl/CJDNS/README).

## Fehler melden
1. Melde Fehler bitte nicht in diesem Repo, stattdessen melde sie hier: https://github.com/hyperboria/bugs/issues
2. Geh ins IRC und sprich mit jemandem.
3. Was passieren wird ist entweder
 * Jemand hat Lust es zu fixen
 * Du hast Lust es zu fixen
 * Es interessiert niemanden und es wird für eine Weile vergessen und eventuell wird jemand später darauf stossen und es fixen oder es geht im Refactoring verloren.
 * Niemand kann es im Moment beheben, aber es wird als merkenswert angesehen, weil es eine große Bedeutung in der Entwicklung des Quelltextes hat. In diesem Fall muss es technisch erklärt werden von jemandem, der den Quelltext sehr gut kennt. Derjenige wird einen Pullrequest in das docs/bugs Verzeichnis machen.

### Sicherheit
Sicherheitsprobleme sollten im IRC berichtet werden, genau wie andere Fehler. Wir haben keine geschlossene Gruppe von Leuten mit Spezialwissen, das Bedeutet, das Standardvorgehen für Sicherheitsmeldungen ist volle Enthüllung.
Schaue unter  https://github.com/cjdelisle/cjdns/blob/master/doc/security_specification.md nach, ob ein Sicherheitsproblem wirklich ein Sicherheitsproblem ist.

Schon wieder diese Zeit des Jahres... Zeit für ein paar Open Source Projekte!
[![Hacktoberfest](https://img.shields.io/badge/Open%20Source-Hacktoberfest-orange.svg)](https://hacktoberfest.digitalocean.com/)

[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns auf Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria-Karte]: https://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns auf Wikipedia]: https://en.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)

#### *Reinventando las redes*

Cjdns implementa una red IPv6 cifrada usando criptografia de llave publica para
la asignación de direcciones y una tabla distribuida de hashes para el
ruteo. Esto provee redes de casi-nula-configuración, y previene mucho de los
problemas de seguridad y escalabilidad que plagan a las redes existentes.

[![Build Status](https://travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/387/badge)](https://bestpractices.coreinfrastructure.org/projects/387)
[![tip for next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![irc](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)
![License](https://img.shields.io/github/license/cjdelisle/cjdns.svg)

## Testimonios

    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

## Comunidad

* [irc://irc.efnet.org/#cjdns][IRC Web]
* [Hyperboria][] la mayor red cjdns, tomando a Octubre 2015 donde tenia 2100 nodos.
* [Project Meshnet][]
* [/r/darknetplan][]
* [#cjdns on Twitter][]


## Documentación

* [Metas del proyecto - en inglés -](doc/projectGoals.md)
* [Cjdns Whitepaper - en inglés -](doc/Whitepaper.md)
* [Cjdns on Wikipedia][]

## Configuración avanzada:

* [Configurando una puerta de enlace NAT en cjdns para tu LAN - en ingles](doc/nat-gateway.md)
* [Instalar cjdns en OpenIndiana - en ingles](doc/open-indiana.md)

Graciars por su tiempo e interes,

Los desarrolladores de CJDNS.

--------------------------------------------------------------------------------

## Como instalar CJDNS

Estas instrucciones son para las distribuciones basadas en Debian y macOS. Deben ser
suficientemente informativas como para usarse en otras distribuciones - solo no
espere que funcionen tal cual. Si desea saber que [base del sistema operativo tiene, revise aqui](https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg).

### 0. Instalar dependencias

En ambas plataformas, instalar [Node.js](http://nodejs.org/), aunque preferible,
no es estrictamente necesario. Si Node.js no esta disponible o en una version
inaceptable, sera descargado e instalado en el arbol de codigo fuente.

#### Distribuciones basadas en Debian:

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

#### Distribuciones basadas en Fedora 22+:

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

#### Distribuciones basada en RHEL (añade el repositorio EPEL):

    sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    sudo yum install install nodejs git
    sudo yum install @development-tools
Construyendo desde el paquete:
`sudo yum localinstall https://kojipkgs.fedoraproject.org//packages/cjdns/17.4/4.el6/src/cjdns-17.4-4.el6.src.rpm`

Si usted esta en una laptop y suspende o hiberna, a cjdroute le tomara unos
minutos figurar que ha pasado al despertar. Puede dramáticamente acelerar esto
con:

    systemctl enable cjdns-resume

El servicio de resume reinicia cjdns cuando el sistema regresa de dormir.

#### Gentoo

    emerge --ask nodejs sys-devel/gcc dev-lang/python:3.4 dev-vcs/git

#### macOS:

Instalar con [Homebrew](https://brew.sh/):

    brew install cjdns

Instalar con [MacPorts](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

Desafortunadamente, en OpenBSD es un poco experimental por el momento.

    pkg_add git node gcc gmake bash

Elija la version gcc-4.8.1p2 o mas reciente.

#### FreeBSD:

Todo lo que necesita esta prearmado en los ports de FreeBSD.

    pkg install gmake node

#### Arch:

Usted puede instalar cjdns ejecutando

    pacman -S cjdns

Si necesita armar desde el codigo fuente, todo lo requerido se puede obtener asi

    pacman -S nodejs git base-devel

Como alternativa, usted podria instalar desde AUR desde el paquete, `cjdns-git`.
Despues de instalar, La configuracion estara en `/etc/cjdroute.conf`.
Para iniciar el servicio `cjdns.service`, ejecute:

       systemctl start cjdns

Para detenerlo:

       systemctl stop cjdns

#### Solus:

Dependencias:

      sudo eopkg install nodejs git build-essential system.devel python gcc binutils kernel-headers xorg-server-devel

Despues siga estas instrucciones:

*Lo sentimos por tantos pasos. Actualmente un paquete se esta aun preparando*

### 1. Obtener cjdns desde GitHub

Clonar el repositorio desde GitHub y cambiar al directorio del codigo fuente:

    git clone https://github.com/cjdelisle/cjdns.git cjdns
    cd cjdns

### 2. Armar

    ./do

Espere por `Build completed successfully, type ./cjdroute to begin setup.`, y entonces
proceda con lo que sigue abajo:

--------------------------------------------------------------------------------

## Configuración

Ejecute cjdroute sin opciones para otener ayuda:

    ./cjdroute

### 0. Cerciórese que tiene las cosas necesarias.

    LANG=C cat /dev/net/tun

Si dice: `cat: /dev/net/tun: File descriptor in bad state` ¡Muy bien!

Si dice: `cat: /dev/net/tun: No such file or directory`, tiene que crearlo ejecutando:

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

Después ejecute `cat /dev/net/tun` otra ves.

Si dice: `cat: /dev/net/tun: Permission denied` Probablemente usted esta usando
un VPS basado en la plataforma de virtualización OpenVZ. Pídale a su proveedor
que habilite el dispositivo TUN/TAP - esto es un protocolo estándar y ellos
deberían de saber que es lo que usted necesita. Si esta usando macOS, no necesita
preocuparse por este paso.

### 1. Generando un archivo de configuración

    ./cjdroute --genconf >> cjdroute.conf

**¡Proteja su archivo conf!**

Un archivo conf extraviado significa perder sus contraseñas y conecciones
, y todo aquel que conectaba a usted ya no lo podrá hacer.
Un archivo conf que ha sido sustraido podría dar a que alguien se dedique
a impersonificarle.

Para generar un archivo conf con los permisos de tal manera que solo su
usuario pueda leer y escribir en el:

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


### 2. Encontrando un amigo

Para acceder a una red existente (por ejemplo, Hyperboria), necesita conectar con
alguien que ya tenga acceso a esa red. Esto es necesario por muchos motivos:

1. Ayuda a prevenir abusos porque la gente malintencionada muy probablemente evitara
   abusar un sistema después de que, en un acto de amabilidad, se le ha dado acceso
   al sistema.
2. Esto no intenta ser una capa sobre la Vieja Internet, su intención es remplazarla.
   Cada conexión eventualmente debera ser remplazada por un cable, un enlace de fibra
   optica, o una conexión inalámbrica.
3. En cualquier caso de desacuerdo, existirá una "cadena de amigos" enlazando a la
   gente involucrada de manera de que exitiría una base para llegar a una resolución.

Para encontrar un amigo, salga de aquí y accede a nuestra [comunidad](#comunidad). También,
de un vistazo a la [Hyperboria Map][] para encontrar nodos cercanos a usted.

### 3. Enlazar su nodo al nodo de su amigo

**Para iniciar una conexión OUTbound**

En su archivo conf, usted observará:

``` javascript
// Nodes to connect to.
"connectTo":
{
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.
}
```

Un archivo conf con múltiples nodos de amigos, con la configuracion OUTbound, deberia
de verse así:

``` javascript
// 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"
    }
}
```

Usted puede agregar tantas conexiones como quiera en el atributo `connectTo`,
siguiendo la sintaxis de JSON.


**Para permitir que su amigo realize una conexión INbound**

En su archivo conf, usted encontrará:

``` javascript
"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"}

],
```

Un archivo conf con múltiple nodos de amigos, con la configuración INbound, deberia de verse como:
``` javascript
"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"}
],
```


Usted necesitaría darle a William Jevons (quien esta haciendo una conexion INbound) las siguiente 4 cosas:

1. Su IPv4 externa
2. El puerto que aquí se lee en su archivo conf:

    `// Bind to this port.
    "bind": "0.0.0.0:yourportnumberishere",`

3. El password único que ha descomentado o creado: `"password": "thisisauniquestring_002"`
4. Su llave pública: `"publicKey": "thisisauniqueKEY_001.k"`
5. Su nombre de usuario: "William Jevons"

Sus credenciales para iniciar sesion se veran como aquí (con su IPv4 y el puerto):

```javascript
"1.2.3.4:56789": {
    "login": "William Jevons",
    "password": "thisisauniquestring_002",
    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"
}
```

De favor cerciorese que usted y su amigo pueden *iniciar* una
conexión tanto hacia fuera (de USTED --> AMIGO) hacia dentro (del AMIGO --> USTED)
pero el tráfico fluye ambos sentidos una vez una coneccion suceda.

Revise [doc/configure_ES.md](doc/configure_ES.md) para mas detalles de
configuración, incluido como acceder a otros nodos cjdns sobre ethernet y wifi.


### 4. Asegurando su sistema - revisar los servicios que escuchan.

Una vez que su nodo esté corriendo, está ahora en una recién creada dirección IPv6.
Su sistema operativo puede que configure automáticamente para que servicios sobre
red lo utilicen.
Si esta no es su intencion, deberá revisar que no se este ofreciendo mas servicios
que los deseados. ;)

Lea [doc/network-services.md](doc/network-services.md) - en inglés - para mas
instrucciones.


### 5. ¡Iniciarlo!

    sudo ./cjdroute < cjdroute.conf

Si desea que las bitácoras se escriban en un archivo:

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

Para detener cjdns:

    sudo killall cjdroute

Si usted tiene problemas, ejecute `killall cjdroute` para regresar a la tranquilidad.
Use `pgrep cjdroute` o `top` para ver si el proceso sigue corriendo.

**¡Nota!**

Esto inicia cjdns como el usuario root para que pueda configurar su sistema
sin impedimentos por los permisos. Para iniciar cjdns como un usuario que no
es root, favor de leer [doc/non-root-user.md](doc/non-root-user.md) - en inglés -.


### 6. Acceda a IRC

¡Bienvenido a la red! Ahora es un administrador de redes. Hay responsabilidades
que vienen con ser un administrador de redes, que incluye estar disponible en
caso de que algo este mal con su equipamiento. Debe de estar en [IRC](#community)
de tal manera de que la gente le encuentre.


## Interfaz de administración

Cuando cjdroute esta habilitado y corriendo, la interfaz de administración estara en
`udp://localhost:11234` (esto puede ser cambiado en el archivo de configuracion
`cjdroute.conf`). Consulte [doc/admin-api.md](doc/admin-api.md) - en inglés - para
mas información sobre la interfaz de administracion. Ha varias herramientas en
la carpeta `contrib/` que puede interactuar con ella.

Puede acceder a la API de administración con:

* La **Python library**; vea [aquí](contrib/python/README.md) - en inglés -.
* La **Perl library**, mantenida por Mikey; vea [aquí](contrib/perl/CJDNS/README) - en inglés -.


## Reportando problemas
1. No hacer reportes en este repositorio, mejor hagalo en https://github.com/hyperboria/bugs/issues
2. Accede a IRC y converse con alguien
3. Lo que pasara en ambos casos
 * Alguien estará de humor para acomodarlo
 * Usted estará de humor para acomodarlo
 * Nadien le importara y sera eventualmente olvidado y talves alguien se topara futuramente con ello,
 lo arregle, o termine superado en alguna reestructura completa del código.
 * Nadie por el momento podrá repararlo pero tendra el merito de ser recordado por su gran significado
 en como el código se desarrolla, y sera el caso de que tendrá que ser explicado por alguien fuertemente
 relacionado al codigo. Podrá realizar una peticion pull al directorio docs/bugs.

### Seguridad
Problemas de seguridad deberán de ser reportado en IRC como cualquier otro bug. No tenemos un grupo
cerrado de personas con conocimientos especiales, lo que significa que el método por defacto para
reportar cosas de seguridad, es con su descripción completa.
Consulte: https://github.com/cjdelisle/cjdns/blob/master/doc/security_specification.md - en ingles -
para comprobar si un aparente problema de seguridad realmente es un problema de seguridad.

Esa época del año nuevamente... ¡El tiempo para actuar en algunos proyectos de código abierto!
[![Hacktoberfest](https://img.shields.io/badge/Open%20Source-Hacktoberfest-orange.svg)](https://hacktoberfest.digitalocean.com/)

[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: http://hyperboria.net
[Project Meshnet]: https://projectmeshnet.org
[/r/darknetplan]: http://www.reddit.com/r/darknetplan
[#cjdns on Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: http://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns on Wikipedia]: https://en.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: http://www.i2p2.de
[Freenet]: https://freenetproject.org

Traduction à partir de la version
[`cjdns-v19.1`](https://github.com/woshilapin/cjdns/blob/cjdns-v19.1/README.md)
# cjdns

[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)

#### *Le réseau réinventé*

Cjdns est un réseau IPv6 chiffré utilisant des clefs publiques de cryptographie

pour l'allocation d'adresses et une table de hashage distribuée pour le
routage.  Il fournit un réseau quasiment sans configuration et évite la majorité
des problèmes de sécurité et de passage à l'échelle (_scalability_) des réseaux
actuels.

[![Statut de compilation](https://api.travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![Bonnes pratiques CII](https://bestpractices.coreinfrastructure.org/projects/387/badge)](https://bestpractices.coreinfrastructure.org/projects/387)
[![Pourboire pour le prochain commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![IRC](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)
![Licence](https://img.shields.io/github/license/cjdelisle/cjdns.svg)

## Témoignages

    23:26 <@jercos> well, cjdns is now officially more reliable than the open
                    internet for getting to my cheaper VPSes :|

    23:26 <@jercos> bon, cjdns est maintenant officiellement plus fiable que
                    l'internet pour me connecter à mes VPS bon marchés :|


    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

    12:52 < mariner> je ne sais pas si ça a déjà été fait avant, et je suppose
                     que c'est facile, mais je pense que c'est génial. En ce
                     moment sur Hype depuis un avion


    00:36 < tester> man sites take so long to load on i2p
    00:36 < tester> i value speed over anonymity any day

    00:36 < tester> les sites prennent tellement longtemps à charger sur I2P
    00:36 < tester> je préfèrerai toujours la vitesse face à l'anonymité


    <DuoNoxSol> it's notably more reliable than the normal internet

    <DuoNoxSol> c'est particulièrement plus fiable que l'internet normal


    09:46 < Kubuxu> I so love cjdns code base

    09:46 < Kubuxu> J'adore tellement le code source de cjdns


    <whyrusleeping> my internet is way better now.
    <whyrusleeping> thanks
    <whyrusleeping> i'm really upset and sad that its better
    <whyrusleeping> but also quite happy

    <whyrusleeping> mon internet est vachement mieux maintenant.
    <whyrusleeping> merci
    <whyrusleeping> je suis vraiment énervé et triste que ce soit mieux
    <whyrusleeping> mais aussi pas mal content


    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

    21:01 <@grewalsat> c'est fou. avec les scores speedtest.net depuis mon
                       boulot, j'ai un débit d'environ 6+mb, et avec une
                       passerelle cjdns comme réseau VPN, j'obtiens autour de
                       11-15mb en téléchargement sur speedtest.net
    21:01 <@grewalsat> :P
    21:01 <@grewalsat> en plus, accès à tout ! :D


    <davidar> Yeah, I have to admit I sort of avoided hypeirc because of stuff like that

    <davidar> Ouais, je dois admettre que j'ai en quelque sorte évité hypeirc à
              cause de ce genre de truc

## Community

* [irc://irc.efnet.org/#cjdns][IRC Web]
* [Hyperboria][] le plus grand réseau cjdns, avec 2100 noeuds en Octobre 2015
* [Projet Meshnet][]
* [/r/darknetplan][]
* [#cjdns sur Twitter][]


## Documentation

* [Objectifs du project](doc/projectGoals.md)
* [Livre blanc sur cjdns](doc/Whitepaper.md)
* [Cjdns sur Wikipedia][]

Configuration avancée:

* [Configurer une passerelle NAT cjdns pour votre LAN](doc/nat-gateway.md)
* [Installer cjdns sur OpenIndiana](doc/open-indiana.md)

Merci pour votre temps et votre intérêt,

Les développeurs de cjdns.

--------------------------------------------------------------------------------

## Comment insaller cjdns

Ces instructions sont pour les distributions Linux basées sur Debian et OS X.
Elles devraient être suffisantes pour d'autres distributions mais n'espérez pas
qu'elles fonctionnent mot pour mot.  Si vous souhaitez connaitre la base de
votre système d'exploitation, [regardez le graphique suivant](https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg).

### 0. Installer les dépendances

Installer [Node.js](https://nodejs.org/), bien que préférable,
n'est pas nécessaire. Si Node.js n'est pas disponible ou que la version n'est
pas la bonne, Node.js sera téléchargé et installé dans le répertoire du code
source.

#### Distributions basées sur Debian :

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

#### Distributions basées sur Fedora 22 ou + :

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

#### Distributions basées sur RHEL (ajoutez le dépôt EPEL) :

    sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    sudo yum install install nodejs git
    sudo yum install @development-tools

Compiler depuis le paquetage :
`sudo yum localinstall https://kojipkgs.fedoraproject.org//packages/cjdns/17.4/4.el6/src/cjdns-17.4-4.el6.src.rpm`

Si vous êtes sur un ordinateur portable et que vous le mettez en veille ou en
hibernation, cjdroute prendra du temps (faites vous un café !) pour comprendre
ce qui vient de se passer en tentant de se réveiller. Vous pouvez radicalement
améliorer la vitesse de ce réveil avec :

    systemctl enable cjdns-resume

Le service de réveil redémarre cjdns lorsque le système sort de veille ou
d'hibernation.

#### Gentoo

    emerge --ask nodejs sys-devel/gcc dev-lang/python:3.4 dev-vcs/git

#### OS X :

Installer avec homebrew :

    brew install cjdns

#### OpenBSD :

Malheureusement, le support sur OpenBSD est encore un peu expérimental.

    pkg_add git node gcc gmake bash

Utilisez gcc-4.8.1p2 ou plus récent.

#### FreeBSD :

Tout ce dont vous avez besoin est disponible pré-compilé dans les ports FreeBSD.

    pkg install gmake node

#### Arch :

Vous pouvez installer cjdns en lançant

    pacman -S cjdns

Si vous avez besoin de compiler à partir des sources, tout ce dont vous avez
besoin peut être installer avec la commande suivante

    pacman -S nodejs git base-devel

Sinon, vous préférez peut-être installer à travers AUR à partir du paquet
`cjdns-git`. Après l'installation, vous trouverez le fichier de configuration
dans `/etc/cjdroute.conf`. Pour démarrer le service `cjdns.service`, faites :

    systemctl start cjdns

Pour l'arrêter, faites :

    systemctl stop cjdns

#### Gentoo :

cjdns n'est pas encore dans le dépôt principal de Gentoo, donc vous allez devoir
utiliser un arbre alternatif (_overlay_). La manière la plus simple est
d'utiliser Layman mais vous pouvez également le faire à la main.

##### Layman :

Premièrement, vous devez installer layman.

    emerge layman

Si layman est installé correctement, vous pouvez ajouter un arbre alternatif

    layman -f
    layman -a weuxel

Pour des mises à jour futures de l'arbre alternatif, utilisez

    layman -S

Maintenant, vous pouvez installer cjdns

    emerge cjdns

##### À la main :

Vous allez devoir cloner l'arbre alternatif depuis le dépôt

    cd /opt
    git clone https://github.com/Weuxel/portage-weuxel.git

Maintenant, configurez portage pour utiliser ce dépôt

    cd /etc/portage/repos.conf/

Créez un fichier `portage-weuxel.conf` contenant

    [weuxel]
    location = /opt/portage-weuxel
    masters = gentoo
    auto-sync = yes

Maintenant, synchronisez

    emerge --sync

Puis installez cjdns

    emerge cjdns

#### Détection automatique de plantage et redémarrage

Copiez le script init openrc `contrib/openrc` vers `/etc/init.d/` et modifiez
les paramètres `CONFFILE` et `command` selon vos besoins. Puis démarrez cjdns

    /etc/init.d/cjdns start

Configurez le système init pour démarrer automatiquement cjdns

    rc-update add cjdns default

Copiez le script `contrib/gentoo/service_restart.sh` vers un répertoire
approprié sur votre système et modifiez l'adresse de courriel. Si vous ne
souhaitez pas recevoir de notifications, commentez la ligne. Maintenant,
ajoutez une ligne dans votre crontab de la manière suivante

    # Redémarrer le service planté
    * * * * *       root	/path/to/script/service_restart.sh

#### Solus :

Dépendances:

    sudo eopkg install nodejs git build-essential system.devel python gcc binutils kernal-headers xorg-server-devel

Puis suivez les étapes suivantes :

*Désolé pour le nombre important d'étapes. Un paquet est en cours de
préparation*

##### 1. Récupérez cjdns sur Github

Clonez le dépôt depuis Github et déplacez vous dans le nouveau répertoire :

    git clone https://github.com/cjdelisle/cjdns.git cjdns
    cd cjdns

##### 2. Compilez

    ./do

Cherchez pour la ligne `Build completed successfully, type ./cjdroute to begin
setup.`, puis continuez ci-dessous :

--------------------------------------------------------------------------------

## Configuration

Lancer cjdroute sans options pour obtenir de l'aide :

    ./cjdroute

### 0. Vérifiez que vous avez tout.

Si vous êtes sur OS X, ne vous inquiétez pas pour cette étape.

    LANG=C cat /dev/net/tun

Si le message est : `cat: /dev/net/tun: File descriptor in bad state` Parfait !

Si le message est : `cat: /dev/net/tun: No such file or directory`, créez le avec :

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

Puis `cat /dev/net/tun` à nouveau.

Si le message est : `cat: /dev/net/tun: Permission denied`, vous utilisez probablement un VPS tournant sur une platforme virtualisée avec OpenVZ.  Demandez à votre fournisseur d'activer le périphérique TUN/TAP - c'est un protocole standard, ils devraient savoir exactement ce dont vous avez besoin.

### 1. Générez un nouveau fichier de configuration

    ./cjdroute --genconf >> cjdroute.conf

**Protégez votre fichier de configuration !**

Un fichier de configuration perdu signifie que vous avez perdu votre mot de
passe et les connexions; toutes les personnes connectées à vous n'en seront plus
capables.  Un fichier de configuration compromis signifie que d'autres personnes
peuvent se faire passer pour vous sur le réseau.

Pour générer un fichier de configuration avec des droits tels que votre
utilisateur puisse lire et écrire dedans :

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


### 2. Trouvez des amis

Pour entrer dans un réseau existant (par exemple, Hyperboria), vous devez vous
connecter à quelqu'un qui est déjà dans le réseau. C'est nécessaire pour les
raisons suivantes :

1. Cela évite les abus car les personnes nuisibles seront moins prompts à abuser
   le système si l'accès leur a été offert dans un acte de bonté
2. L'intention n'est pas de faire une surcouche au Vieil Internet, l'objectif
   est de le remplacer. Chaque connexion sera à terme, remplacée par un cable,
   une fibre optique ou une connexion sans fil.
3. Dans le cas d'un désaccord, une « chaine d'amis » liant les personnes
   impliquées fournira une base afin d'aboutir à une solution.

Pour trouver un ami, sortez dehors and rejoignez notre [communité](#community).  Vous pouvez également jetez un oeil à la
[carte Hyperboria][] pour trouver des pairs près de chez vous.


### 3. Connectez votre noeud à celui de votre ami

**Pour démarrer une connexion OUTbound**

Dans votre fichier de configuration, vous trouverez :

``` javascript
// Nodes to connect to.
"connectTo":
{
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.
}
```

Un fichier de configuration avec plusieurs noeuds amis OUTbound devrait
ressembler à ceci :

``` javascript
// Nodes to connect to.
"connectTo":
{
    //ami_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"
    },

    //ami_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"
    }
}
```

Vous pouvez ajouter autant de connexions que vous le voulez dans la propriété
`connectTo`, en respectant la syntaxe JSON.


**Pour permettre à votre ami de démarrer une connexion INbound**

Dans votre fichier de configuration, vous trouverez :

``` javascript
"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"}

],
```

Un fichier de configuration avec plusieurs noeuds amis INbound, devrait
ressembler à ceci :
``` javascript
"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"}
],
```


Vous devez donner à William Jevons (qui se connectera en INbound) les 4 éléments suivants :

1. Votre adresse IPv4 externe
2. Le port que vous trouverez dans votre fichier de configuration à la ligne

    `// Bind to this port.
    "bind": "0.0.0.0:yourportnumberishere",`

3. Un mot de passe unique que vous décommentez ou que vous créez : `"password": "thisisauniquestring_002"`
4. Votre clef publique : `"publicKey": "thisisauniqueKEY_001.k"`
5. Son nom d'utilisateur : "William Jevons"

Ces paramètres de connexion devraient ressembler à quelque chose comme ceci
(avec votre adresse IPv4 et votre port) :

```javascript
"1.2.3.4:56789": {
    "login": "William Jevons",
    "password": "thisisauniquestring_002",
    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"
}
```

Veuillez noter que vous et votre ami peuvent *démarrer* une connexion soit
OUTbound (de VOUS --> AMI) soit INbound (de AMI --> vous) mais la circulation se
fait dans les deux sens une fois que la connection est établie.

Voir [doc/configure.md](doc/configure.md) pour plus de détails sur la
configuration, en particulier sur la manière de se connecter à d'autres noeuds
cjdns à travers ethernet et wifi.


### 4. Sécurisez votre système - vérifiez les services ouverts

Une fois que votre noeud tourne, vous êtes maintenant le nouveau propriétaire
d'une adresse IPv6. Votre système d'exploitation reconfigurera peut-être
automatiquement les services de réseau pour utiliser cette nouvelle adresse. Si
ce n'est pas ce que vous souhaitez, vous devriez vérifier que vous n'offrez pas
plus de services que vous ne souhaitez vraiment. ;)

Voir [doc/network-services.md](doc/network-services.md) pour les instructions.


### 5. Démarrez-le !

    sudo ./cjdroute < cjdroute.conf

Si vous voulez écrire les messages du programme dans un fichier :

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

Pour arrêter cjdns :

    sudo killall cjdroute

Si vous avez des problèmes, utilisez `kilall cjdroute` pour retrouver un état
propre. Utilisez `pgrep cjdroute` ou `top` pour vérifier s'il est lancé.

**NOTE !**

Cette commande lance cjdns en tant qu'utilisateur root afin de pouvoir
configurer votre système sans soucis de droits. Pour démarrer cjdns en tant
qu'utilisateur normal, voir [doc/non-root-user.md](doc/non-root-user.md).


### 6. Venir sur IRC

Bienvenue sur le réseau ! Vous êtes maintenant un administrateur réseau.
Certaines responsabilités viennent avec le fait d'être un administrateur réseau
incluant être disponible en cas de problème avec votre matériel. Vous devriez
rester sur [IRC](#community) afin que les gens puissent vous joindre.


## Interface administrateur

Lorsque cjdroute est lancé, l'interface administrateur est disponible sur
`udp://localhost:11234` (ceci peut être modifié dans le fichier de configuration
`cjdroute.conf`). Voir [doc/admin-api.md](doc/admin-api.md) pour plus
d'informations à propos de l'interface administrateur. Plusieurs outils pour
interagir avec cette interface sont disponibles dans `contrib/`.

Vous pouvez accéder à l'interface administrateur avec :

* la **bibliothèque Python**; voir [ici](contrib/python/README.md).
* la **bibliothèque Perl**, maintenue par Mikey; voir [ici](contrib/perl/CJDNS/README).


## Remonter un bogue
1. Ne remontez pas les bogues dans ce dépôt, veuillez les remonter au niveau de
   https://github.com/hyperboria/bugs/issues
2. Se connecter sur IRC et discuter avec quelqu'un
3. Qu'adviendra-t-il si
 * Quelqu'un se sent capable de le corriger
 * Vous vous sentez capable de le corriger
 * Personne ne se sent concerné et il sera oublié pendant une période jusqu'à ce
   que quelqu'un d'autre tombe dessus plus tard et le corrige ou il sera corrigé
   indirectement par une réorganisation du code
 * Personne ne peut le corriger pour le moment mais il semble nécessaire de s'en
   rappeler car il a un impact significatif sur la manière dont le projet est
   développé, dans ce cas, il est nécessaire qu'il soit expliqué en termes
   techniques par quelqu'un ayant une bonne connaissance du code du projet. Ils
   devraient faire une requête au code (_pull request_) aux répertoires
   docs/bugs.

### Sécurité
Les bogues de sécurité devraient être remontés sur IRC de la même manière que
les autres bogues. Nous n'avons pas de groupe de personne priviligiée avec une
connaissance spécifique, donc notre politique de remontée de bogues de sécurité
est une divulgation totale.
voir : https://github.com/cjdelisle/cjdns/blob/master/doc/security_specification.md pour voir si un bogue possible de sécurité en est vraiment un.

À ce moment de l'année, à nouveau... Il est temps pour quelques projets libres !
[![Hacktoberfest](https://img.shields.io/badge/Open%20Source-Hacktoberfest-orange.svg)](https://hacktoberfest.digitalocean.com/)

[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns on Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: https://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns on Wikipedia]: https://en.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[English](README.md)
[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)

#### *Η δικτύωση επανεφευρέθηκε*

Cjdns υλοποιεί ένα κρυπτογραφημένο δίκτυο IPV6 χρησιμοποιώντας κρυπτογραφία δημόσιου-κλειδιού για
κατανομή διευθύνσεων και ένα κατανεμημένο πίνακα hash για δρομολόγηση. Αυτό προσφέρει
σχεδόν-μηδενικής-ρύθμισης δικτύωση, και αποτρέπει πολλά ζητήματα ασφαλείας και
επεκτασιμότητας που μαστίζουν τα υπάρχοντα δίκτυα.

[![Build Status](https://api.travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![tip for next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![irc](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)

## Γνώμες πελατών

    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

## Κοινότητα

* [irc://irc.efnet.org/#cjdns][IRC Web]
* [Hyperboria][] the largest cjdns network, as of October 2015 there are 2100 nodes.
* [/r/darknetplan][]
* [#cjdns on Twitter][]


## Τεκμηρίωση

* [Project Goals](doc/projectGoals.md)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns στο Wikipedia]()

Προχωρημένες ρυθμίσεις:

* [Στήστε μια cjdns NAT πύλη για το LAN σας](doc/nat-gateway.md)
* [Εγκατάσταση του cjdns σε OpenIndiana](doc/open-indiana.md)

Ευχαριστούμε για το χρόνο και το ενδιαφέρον σας,

Οι προγραμματιστές του cjdns.

--------------------------------------------------------------------------------

## Πώς να εγκαταστήσετε το cjdns

Αυτές οι οδηγίες είναι για διανομές Debian-based Linux και macOS. Θα ήταν
αρκετά πληροφοριακές για χρήση σε άλλες διανομές - απλά μην περιμένετε να
δουλέψουν αυτολεξεί.

### 0. Εγκατάσταση εξαρτήσεων

Και στις δύο πλατφόρμες, η εγκατάσταση του [Node.js](https://nodejs.org/en), αν και προτιμούμενη,
δεν είναι αυστηρά απαραίτητη. Αν το Node.js δεν είναι διαθέσιμο ή δεν είναι αποδεκτής έκδοσης,
θα κατέβει και θα εγκατασταθεί στο πηγαίο δέντρο.

#### Debian-based διανομή:

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

#### Fedora 22+ based διανομή:

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

#### RHEL based διανομή (προσθέτει το EPEL αποθετήριο):

    sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    sudo yum install install nodejs git
    sudo yum install @development-tools

#### macOS:

Εγκατάσταση με το [Homebrew](https://brew.sh/):

    brew install cjdns

Εγκατάσταση με το [MacPorts](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

Δυστυχώς, το OpenBSD είναι λίγο πειραματικό αυτή τη στιγμή.

    pkg_add git node gcc gmake bash

Διαλέξτε έκδοση gcc-4.8.1p2 ή πιο πρόσφατη.

#### FreeBSD:

Ό,τι χρειάζεστε είναι διαθέσιμο προκατασκευασμένο σε FreeBSD' ports.

    pkg install gmake node bash

#### Arch:

Μπορείτε να εγκαταστήσετε το cjdns τρέχοντας

    pacman -S cjdns

Αν χρείαζεται να χτίσετε από τον πηγαίο κώδικα, όλα όσα χρείαζεστε μπορούν να εγκατασταθούν έτσι

    pacman -S nodejs git base-devel

### 1. Ανακτήστε το cjdns από το GitHub

Κλωνοποίηστε το αποθετήριο από το GitHub και περάστε στο πηγαίο φάκελο:

    git clone https://github.com/cjdelisle/cjdns.git
    cd cjdns

### 2. Χτίστε

    ./do

Κοιτάξτε για μήνυμα `Build completed successfully, type ./cjdroute to begin setup.`, μετά
προχωρήστε παρακάτω:

--------------------------------------------------------------------------------

## Στήσιμο

Τρέξτε το cjdroute χωρίς επιλογές για ΒΟΗΘΕΙΑ:

    ./cjdroute

### 0. Βεβαιωθείτε πως έχετε το πράμα.

    LANG=C cat /dev/net/tun

Αν λέει: `cat: /dev/net/tun: File descriptor in bad state` Καλώς!

Αν λέει: `cat: /dev/net/tun: No such file or directory`, φτιάξτε το κάνοντας:

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

Μετά εκτελέστε `cat /dev/net/tun` ξανά.

Αν λέει: `cat: /dev/net/tun: Permission denied` Πιθανώς χρησιμοποιείται κάποιο VPS
βασισμένο στην OpenVZ πλατφόρμα εικονικοποίησης. Ζητήστε από τον παροχό σας να ενεργοποιήσει τη
TUN/TAP συσκευή - αυτό είναι στάνταρ πρωτόκολλο ώστε να ξέρουν ακριβώς τι χρειάζεστε.
Αν εργάζεστε σε macOS, δε χρειάζεται να ανησυχείτε για αυτό το βήμα.


### 1. Δημιουργήστε ένα νέο αρχείο επιλογών

    ./cjdroute --genconf >> cjdroute.conf

**Προστατέψτε το αρχείο επιλογών σας!**

Ένα χαμένο αρχείο επιλογών σημαίνει πως χάσατε τον κωδικό και
τις συνδέσεις και οποιοσδήποτε ήταν συνδεδεμένος σε εσάς δεν μπορεί πλέον να συνδεθεί.
Ένα εκτεθειμένο αρχείο επιλογών σημαίνει πως άλλοι μπορούν να σας υποδηθούν στο
δίκτυο.

Για να δημιουργήσετε ένα αρχείο επιλογών με άδειες όπου να είστε ο μόνος χρήστης που μπορεί
να το διαβάσει και να γράψει σε αυτό:

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


### 2. Βρείτε ένα φίλο

Για να μπείτε σε ένα υπάρχον δίκτυο (π.χ. το Hyperboria), χρειάζεται να συνδεθείτε με
κάποιον που είναι ήδη στο δίκτυο. Αυτό απαιτείται για τους παρακάτω
λόγους:

1. Βοηθά στην αποτροπή της κατάχρησης γιατί οι κακοί άνθρωποι δε θα θέλουν και τόσο να καταχραστούν
   ένα σύστημα αφότου, ως κίνηση ανθρωπιάς, τους δόθηκε πρόσβαση σε αυτό το
   σύστημα.
2. Δεν σκοπεύει να καλύψει το "Παλιό Internet", σκοπεύει να το αντικαταστήσει.
   Κάθε σύνδεση με τον καιρό θα αντικατασταθεί από καλώδιο, οπτικές ίνες,
   σύνδεση ασύρματης δικτύωσης.
3. Σε οποιαδήποτε περίπτωση διαφωνίας, θα υπάρχει μια "αλυσίδα φίλων" που θα
   συνδέει τα άτομα που ασχολούνται οπότε θα υπάρχει ήδη μια βάση ώστε να βγει
   μια ανάλυση.

Για να βρείτε ένα φίλο, βγείτε εκεί έξω και μπείτε στην [κοινότητα](#community). Επίσης, ρίξτε
μια ματιά στο [Χάρτη του Hyperboria]() ώστε να βρείτε peers κοντά σας.


### 3. Συνδέστε τον κόμβο σας στον κόμβο του φίλου σας

**Ξεκινήστε μια εξερχόμενη σύνδεση**

Στο αρχείο επιλογών, θα δείτε:

``` javascript
// Nodes to connect to.
"connectTo":
{
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.
}
```

Ένα αρχείο επιλογών με πολλαπλούς φιλικούς κόμβους, στις εξερχόμενες συνδέσεις, θα έμοιαζε κάπως έτσι:

``` javascript
// 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"
    }
}
```

Μπορείτε να προσθέσετε όσες συνδέσεις θέλετε στην `connectTo` ιδιότητα,
ακολουθώντας σύνταξη JSON.


**Για να επιτρέψετε στο φίλο σας να εκκινήσει μια εισερχόμενη σύνδεση**

Στο αρχείο επιλογών, θα δείτε:

``` javascript
"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"}

],
```

Ένα αρχείο επιλογών με πολλαπλούς φιλικούς κόμβους, στις εισερχόμενες συνδέσεις, θα έμοιαζε κάπως έτσι:
``` javascript
"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"}
],
```


Χρειάζεται να δώσετε στον William Jevons (που θέλει να κάνει μια εισερχόμενη σύνδεση) τα 4 παρακάτω στοιχεία:

1. Την εξωτερική IPv4 σας
2. Την θύρα που θα βρείτε στο αρχείο επιλογών σας εδώ:

    `// Bind to this port.
    "bind": "0.0.0.0:οαριθμόςτηςθύραςείναιεδώ",`

3. Τον μοναδικό κωδικό πρόσβασης που αποσχολιάσατε ή δημιουργήσατε: `"password": "thisisauniquestring_002"`
4. Το δημόσιο κλειδί σας: `"publicKey": "thisisauniqueKEY_001.k"`
5. Το όνομα χρήστη του: "William Jevons"

Το πιστοποιητικό εισόδου του θα μοιάζει κάπως έτσι (με την IPv4 και θύρα σας):

```javascript
"1.2.3.4:56789": {
    "login": "William Jevons",
    "password": "thisisauniquestring_002",
    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"
}
```

Παρακαλούμε σημειώστε πως εσείς και ο φίλος σας μπορείτε να *εκκινήσετε* μία
σύνδεση είτε εξερχόμενη (ΕΣΕΙΣ --> ΦΙΛΟΣ) ή εισερχόμενη (ΦΙΛΟ --> ΕΣΕΙΣ)
αλλά η κίνηση είναι αμφίδρομη από τη στιγμή που γίνει η σύνδεση.

Δείτε το [doc/configure.md](doc/configure.md) για περισσότερες πληροφορίες πάνω στις ρυθμίσεις,
συμπεριλαμβανομένου του πως να συνδεθείτε με άλλους κόμβους cjdns μέσω ethernet και wifi.


### 4. Διασφαλίστε το σύστημά σας - ελέγξτε για υπηρεσίες

Με το που τρέξει ο κόμβος σας, είστε ένας φρεσκοκομμένος IPv6 host. Το λειτουργικό σας
σύστημα ίσως αυτόματα επανερυθμίσει τις υπηρεσίες δικτύου για να χρησιμοποιήσει τη νέα σας διεύθυνση.
Εαν αυτό δεν είναι επιθυμητό από εσάς, θα πρέπει να δείτε πως δεν προσφέρετε παραπάνω
υπηρεσίες από αυτές που σκοπεύατε. ;)

Δείτε το [doc/network-services.md](doc/network-services.md) για οδηγίες.


### 5. Ξεκινήστε το!

    sudo ./cjdroute < cjdroute.conf

Αν θέλετε τα καταγραφόμενα να περαστούν σε αρχείο:

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

Για να σταματήσετε το cjdns:

    sudo killall cjdroute

Αν έχετε προβλήματα χρησιμοποιήστε `killall cjdroute` για να επιστρέψετε στη λογική. Χρησιμοποιήστε
`pgrep cjdroute` ή `top` για να δείτε αν τρέχει.

**ΣΗΜΕΙΩΣΗ!**

Αυτό ξεκινά το cjdns ως χρήστης root ώστε να μπορεί να ρυθμίσει το σύστημά σας
χωρίς ανησυχίες για τα δικαιώματα. Για να ξεκινήσετε το cjdns ως μη-root χρήστης, δείτε
[doc/non-root-user.md](doc/non-root-user.md).


### 6. Μπείτε στο IRC

Καλωσήρθατε στο δίκτυο! Πλέον είστε διαχειριστής δικτύου. Υπάρχουν
ευθύνες που έρχονται με το να είσαι διαχειριστής δικτύου που συμπεριλαμβάνει
το να είσαι διαθέσιμος σε περίπτωση που υπάρχει κάποιο πρόβλημα με τον εξοπλισμό σας. Θα πρέπει
να μείνετε στο [IRC](#community) να μπορεί να σας βρει ο κόσμος.


## Διεπαφή διαχείρισης

Όταν το cjdroute τρέχει, η διεπαφή διαχείρισης είναι διαθέσιμη στη
`udp://localhost:11234` (αυτό μπορεί να αλλαχτεί στο `cjdroute.conf`
αρχείο επιλογών). Δείτε [doc/admin-api.md](doc/admin-api.md) για περισσότερες
πληροφορίες σχετικά με την διεπαφή διαχείρισης. Υπάρχουν διάφορα εργαλεία στο `contrib/`
που μπορούν να αλληλεπιδράσουν με αυτή.

Μπορείτε να έχετε πρόσβαση στο API διαχείρισης με:

* την **Python library**; δείτε [εδώ](contrib/python/README.md).
* την **Perl library**, συντηρείται από τον Mikey; δείτε [εδώ](contrib/perl/CJDNS/README).


[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns on Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: https://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns on Wikipedia]: https://en.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[English](README.md)
[Русская версия](README_RU.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)

#### *Umrežavanje iznova*

Cjdns je šifrirana IPv6 mreža koja koristi public-key kriptografiju za
dodjelu adresa i DHT za usmjeravanje. To omogućuje gotovo nikakvu
mrežnu konfiguraciju i sprječava mnoge sigurnosne i
skalabilne probleme koje muče trenutne mreže.

[![Build Status](https://api.travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![napojnica za sljedeću promjenu](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)

## Iskustva

    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


## Zajednica

* irc://irc.efnet.org/#cjdns ([web client][IRC Web])
* [Hyperboria][]
* [Projekt Meshnet][]
* [/r/darknetplan][]
* [#cjdns na Twitteru][]


## Dokumentacija

* [Ciljevi projekta](doc/projectGoals.md)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns na Wikipediji][]


Napredna konfiguracija:

* [Setup a cjdns NAT gateway for your LAN](doc/nat-gateway.md)
* [Instaliraj cjdns na OpenIndiani](doc/open-indiana.md)

Hvala Vam za vaše vrijeme i interes,

Cjdns programeri.

--------------------------------------------------------------------------------

## Kako instalirati cjdns

Ove instrukcije su namijenjene za distribucije bazirane na Debian Linux-u i macOS-u.
Trebale bi biti dovoljno informativne za korištenje na ostalim distribucijama,
ali ne očekujte da će raditi od prve.

### 0. Install dependencies

On both platforms, installing [Node.js](https://nodejs.org/), 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.

#### Distribucija bazirana na Debianu:

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

#### Distribucija bazirana na Fedori 22+:

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

#### Distribucija bazirana na RHELu (dodaje EPEL repozitorij):

    sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    sudo yum install install nodejs git
    sudo yum install @development-tools

#### macOS:

Instalacija putem [Homebrewa](https://brew.sh/):

    brew install cjdns

Instalacija putem [MacPortsa](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

    pkg_add git node gcc gmake bash

Odaberite verziju gcc-4.8.1p2 ili noviju.

#### FreeBSD:

    pkg install gmake node

#### Arch:

Možete instalirati cjdns sljedećom naredbom;

    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`.
Nakon instalacije konfiguracijska datoteka će se nalaziti u `/etc/cjdroute.conf`.
Za pokrenuti servis `cjdns.service`, pokrenite sljedeću naredbu:

        systemctl start cjdns

Za zaustavljanje:

       systemctl stop cjdns

#### Gentoo:

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.

##### Layman:

Prvo treba te instalirati 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

##### By hand:

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

#### Automatic crash detection and restart

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

   # Restart crashed Services
   * * * * *       root	/path/to/script/service_restart.sh

#### Solus:

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*

### 1. Preuzmite cjdns sa GitHuba

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

Potražite `Build completed successfully, type ./cjdroute to begin setup.`, zatim nastavite:

--------------------------------------------------------------------------------

## Setup

Run cjdroute without options for HELP:

    ./cjdroute

### 0. Provjerite imate li potrebne stvari

    LANG=C cat /dev/net/tun

Ako kaže: `cat: /dev/net/tun: File descriptor in bad state`, sve je u redu!

Ako kaže: `cat: /dev/net/tun: No such file or directory`, stvorite ga putem:

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

Zatim opet pokrenite `cat /dev/net/tun`.

Ako kaže: `cat: /dev/net/tun: Permission denied` vjerojatno koristite VPS
baziran na OpenVZ virtualizacijskoj platformi. Pitajte vašeg pružatelja usluga da vam omogući
TUN/TAP - ovo je standardni protokol tako da bi trebali znati što trebate.
Ako ste na macOSu, ne morate se brinuti u vezi ove greške.


### 1. Stvorite novu konfiguracijsku datoteku

    ./cjdroute --genconf >> cjdroute.conf

**Zaštitite Vašu konfiguraciju!** 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 set 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. Pronađite prijatelja

Kako biste ušli u postojeću mrežu (npr. Hyperboria), morate se spojiti s nekime
tko je već unutar te mreže. To je tako zbog nekoliko razloga:

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](#community). Also, have
a look at the [Hyperboria Map][] to find peers near you.


### 3. Spojite vaš node sa nodeom prijatelja

**Za pokretanje izlazne konekcije**

U Vašoj conf datoteci vidjeti ćete:

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

``` javascript
// 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":
    {
        "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":
    {
        "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**

U Vašoj conf datoteci vidjeti ćete:
``` javascript
"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:
``` javascript
"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"}
],
```


Morate dati friend_3 (who is making the INbound connection) sljedeće 4 stvari:

1. Vašu vanjsku IPv4 adresu
2. Port iz konfiguracijske datoteke:

                `// Bind to this port.
                "bind": "0.0.0.0:yourportnumberishere",`

3. Their unique password that you uncommented or created: `"password": "thisisauniquestring_002"`
4. Vaš javni ključ: `"publicKey": "thisisauniqueKEY_001.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](doc/configure.md) for more details on configuration,
including how to peer with other cjdns nodes over ethernet and wifi.


### 4. Zaštitite Vaš sustav - check for listening services

Nakon što se Vaš node pokrene, postajete IPv6 host. Vaš operativni
sustav će automatski konfigurirati mrežne servise kako bi koristili novu adresu.
Ako ovo nije Vaš cilj, trebali bi ste provjeriti da ne pružate više servisa
nego što mislite. ;)

Pogledajte [doc/network-services.md](doc/network-services.md) za instrukcije.


### 5. Pokrenite ga!

    sudo ./cjdroute < cjdroute.conf

Ako želite da se logovi zapisuju u datoteku:

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

Za zaustavljanje cjdns-a:

    sudo killall cjdroute

Ako imate problema koristite `killall cjdroute`.
Koristite `pgrep cjdroute` ili `top` kako bi ste provjerili radi li cjdns.

**Note:** ovo pokreće cjdns kao putem korisnika tako da može konfigurirati Vaš sustav
bez potrebnih dozvola. Za pokretanje cjdns-a putem običnog korisnika, pogledajte
[doc/non-root-user.md](doc/non-root-user.md).


### 6. Dođite na IRC

Dobrodošli u mrežu! Sada ste mrežni administrator. Kao mrežni
administrator odgovorni ste za stvari poput kvara opreme.
Budite na [IRC-u](#community) kako bi vas ljudi mogli kontaktirati.


## Administratorsko sučelje

Kada je cjdnroute pokrenut, administratorsko sučelje biti će dostupna na
`udp://localhost:11234` (ovo se može promijeniti u cjdroute.conf
konfiguracijskoj datoteci). Pogledajte [doc/admin-api.md](doc/admin-api.md) za više
informacija o administratorskom sučelju. U `contrib/` se nalazi nekoliko alata
s kojima može komunicirati.

Možete pristupiti administratorskom API-ju putem:

* the **Python library**; pogledajte
  [contrib/python/README.md](contrib/python/README.md).
* the **Perl library**, održava Mikey; pogledajte
  [contrib/perl/CJDNS/README](contrib/perl/CJDNS/README).


[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns na Twitteru]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: https://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns na Wikepediji]: https://en.wikipedia.org/wiki/Cjdns
[Distribuirana hash tablica]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)
[Português brasileiro](README_PT-BR.md)

#### *Rede Reinventada*

O Cjdns implementa uma rede IPv6 criptografada usando criptografia de chave pública para
alocação de endereços e uma tabela de hash distribuída para roteamento. Isso fornece
rede de configuração quase zero e evita muitos dos aspectos de segurança e
problemas de escalabilidade que afetam as redes existentes.

[![Build Status](https://api.travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/387/badge)](https://bestpractices.coreinfrastructure.org/projects/387)
[![tip for next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![irc](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)
![License](https://img.shields.io/github/license/cjdelisle/cjdns.svg)

## Depoimentos

    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

## Comunidade

* [irc://irc.efnet.org/#cjdns][IRC Web]
* [Hyperboria][] a maior rede de cjdns, em outubro de 2015, havia 2100 nós.
* [/r/darknetplan][]
* [#cjdns no Twitter][]
* [/r/CJDNS](https://www.reddit.com/r/cjdns/)


## Documentação

* [Objetivos do projeto](doc/projectGoals.md)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns na Wikipedia][]

Configuração avançada:

* [Configure um gateway NAT cjdns para sua LAN](doc/nat-gateway.md)
* [Instale cjdns no OpenIndiana](doc/open-indiana.md)

Obrigado por seu tempo e interesse,

Os desenvolvedores do cjdns.

--------------------------------------------------------------------------------

## Como instalar o cjdns

Estas instruções são para distribuições Linux baseadas no Debian e macOS. Eles deveriam ser
informativo o suficiente para uso em outras distribuições - apenas não espere que
trabalhar literalmente. Se você quer saber qual é a [base do sistema operacional, clique aqui](https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg).

### 0. Instalar dependências

Nas duas plataformas, a instalação do [Node.js] (https://nodejs.org/), embora seja preferível,
não é estritamente necessário. Se o Node.js estiver indisponível ou uma versão inaceitável,
ele será baixado e instalado na árvore de origem.

#### Distribuição baseada no Debian:

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

#### Distro baseado no Fedora 22+:

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

#### Distribuição baseada em RHEL (adiciona o repositório EPEL):

    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

#### Construção a partir do pacote:

    sudo yum localinstall https://kojipkgs.fedoraproject.org//packages/cjdns/17.4/4.el6/src/cjdns-17.4-4.el6.src.rpm

Se você estiver em um laptop e o suspender ou hibernar, o cjdroute levará alguns
minutos para fazer café e descobrir o que aconteceu quando acorda. Vocês
pode acelerar drasticamente isso com:

    systemctl enable cjdns-resume

O serviço de reinicialização reinicia o cjdns quando o sistema acorda do modo de suspensão.

#### Gentoo

    emerge --ask nodejs sys-devel/gcc dev-lang/python:3.4 dev-vcs/git

#### macOS:

Instale com [Homebrew](https://brew.sh/):

    brew install cjdns

Instale com [MacPorts](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

    pkg_add git node gcc gmake bash

Selecione a versão gcc-4.8.1p2 ou mais recente.

#### FreeBSD:

Tudo o que você precisa está disponível pré-compilado nas portas do FreeBSD.

    pkg install gmake node

#### Arch:

Você pode instalar cjdns executando:

    pacman -S cjdns

Se você precisa construir a partir do código-fonte, tudo o que você precisa pode ser instalado assim:

    pacman -S nodejs git base-devel

Como alternativa, você pode instalar via AUR a partir do pacote, `cjdns-git`.
Após a instalação, o arquivo de configuração está localizado em `/etc/cjdroute.conf`.
Para iniciar o serviço `cjdns.service`, faça:

    systemctl start cjdns

Para parar:

    systemctl stop cjdns

#### Gentoo:

O cjdns ainda não está no repositório principal do Gentoo, então você terá que usar uma sobreposição.
A maneira mais fácil é usar o Layman, mas você também pode fazê-lo manualmente.

##### Layman:

Primeiro, você precisa instalar layman.

    emerge layman

Se o layman estiver instalado corretamente, você poderá adicionar a sobreposição

    layman -f
    layman -a weuxel

Para atualização futura da sobreposição, use

    layman -S

Agora você pode instalar o cjdns

    emerge cjdns

##### À mão:

Você precisará clonar o repositório de sobreposições

    cd /opt
    git clone https://github.com/Weuxel/portage-weuxel.git

Agora diga ao portage para usar este repositório

    cd /etc/portage/repos.conf/

Crie um arquivo `portage-weuxel.conf` contendo

    [weuxel]
    location = /opt/portage-weuxel
    masters = gentoo
    auto-sync = yes

Agora sincronize

    emerge --sync

E instale cjdns

    emerge cjdns

#### Detecção e reinício automáticos de falhas

Copie o script init openrc de `contrib/openrc` para `/etc/init.d/` e modifique o `CONFFILE` e `command` parâmetro para suas necessidades.
Em seguida, inicie o cjdns emitindo

    /etc/init.d/cjdns start

Configure o sistema init para iniciar automaticamente cjdns

    rc-update add cjdns default

Copie o script service_restart `contrib/gentoo/service_restart.sh` para qualquer diretório conveniente em
seu sistema e modifique o endereço de e-mail. Se você não deseja ser notificado, comente toda a linha.
Agora adicione uma entrada crontab como esta

    # Restart crashed Services
    * * * * *       root	/path/to/script/service_restart.sh

#### Solus:

Dependências:

    sudo eopkg install nodejs git build-essential system.devel python gcc binutils kernal-headers xorg-server-devel

Siga as etapas abaixo:

* Desculpe por tantas etapas. Um pacote está sendo trabalhado atualmente *

##### 1. Recuperar cjdns do GitHub

Clone o repositório do GitHub e mude para o diretório de origem:

    git clone https://github.com/cjdelisle/cjdns.git cjdns
    cd cjdns

##### 2. Construir

    ./do

Procure por `Build completed successfully, type ./cjdroute to begin setup.`e, em seguida,
prossiga abaixo:

--------------------------------------------------------------------------------

## Configuração

Execute cjdroute sem opções para HELP:

    ./cjdroute

### 0. Verifique se você tem as coisas.

Se você estiver no macOS, não se preocupe com esta etapa.

    LANG=C cat /dev/net/tun

Se diz: `cat: /dev/net/tun: File descriptor in bad state` Bom!

Se diz: `cat: /dev/net/tun: No such file or directory`, crie usando:

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

Então `cat /dev/net/tun` novamente.

Se diz: `cat: /dev/net/tun: Permission denied` Você provavelmente está usando um VPS
com base na plataforma de virtualização OpenVZ. Peça ao seu provedor para ativar o
Dispositivo TUN / TAP - este é o protocolo padrão para que eles saibam exatamente o que você
necessita.


### 1. Gere um novo arquivo de configuração

    ./cjdroute --genconf >> cjdroute.conf

**Proteja seu arquivo conf!**

Um arquivo conf perdido significa que você perdeu sua senha e
conexões e qualquer pessoa conectada a você não poderá mais se conectar.
Um arquivo conf comprometido significa que outras pessoas podem se passar por você na rede.

Para gerar um arquivo conf com permissões definidas, para que somente seu usuário possa lê-lo e gravá-lo:

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


### 2. Encontre um amigo

Para entrar em uma rede existente (por exemplo, Hyperboria), você precisa se conectar a alguém que já esteja na rede. Isso é necessário por vários motivos:

1. Ajuda a evitar abusos, porque as pessoas más terão menos probabilidade de abusar de um sistema depois de terem, em um ato de bondade humana, acesso a esse sistema.
2. Não se destina a sobrepor a Internet antiga, mas a substituí-la. No momento oportuno, cada conexão será substituída por um fio, um cabo de fibra ótica ou uma conexão de rede sem fio.
3. Em qualquer caso de desacordo, haverá uma "cadeia de amigos" ligando as pessoas envolvidas, para que já haja uma base para chegar a uma resolução.

Para encontrar um amigo, vá lá e participe de nossa [comunidade] (# comunidade). Além disso, dê uma olhada no [Mapa da Hyperboria] (https://www.fc00.org/) para encontrar colegas perto de você.

Você também pode usar a lista geograficamente variada de credenciais de emparelhamento público para ingressar no Hyperboria em [hyperboria / peers] (https://github.com/hyperboria/peers).

### 3. Conecte seu nó ao nó do seu amigo

**Para iniciar a conexão OUTbound**

No seu arquivo conf, você verá:

``` javascript
// Nodes to connect to.
"connectTo":
{
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.
}
```

Um arquivo conf com vários nós amigos, configuração OUTbound, deve se parecer com:

``` javascript
// 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"
    }
}
```

Você pode adicionar quantas conexões desejar ao atributo `connectTo`,
seguindo a sintaxe JSON.


**Para permitir que seu amigo inicie a conexão INbound**

No seu arquivo conf, você verá:

``` javascript
"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"}

],
```

Um arquivo conf com vários nós amigos, configuração INbound, deve se parecer com:
``` javascript
"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"}
],
```


Você precisa fornecer a William Jevons (que está fazendo a conexão de entrada) os seguintes 4 itens:

1. Seu IPv4 externo
2. A porta encontrada no seu arquivo conf aqui:

    `// Bind to this port.
    "bind": "0.0.0.0:yourportnumberishere",`

3. A senha exclusiva deles que você descomentou ou criou: `"password": "thisisauniquestring_002"`
4. Sua chave pública: `"publicKey": "thisisauniqueKEY_001.k"`
5. O nome de usuário dele: "William Jevons"

Suas credenciais de login terão a seguinte aparência (com seu IPv4 e porta):

```javascript
"1.2.3.4:56789": {
    "login": "William Jevons",
    "password": "thisisauniquestring_002",
    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"
}
```

Observe que você e seu amigo podem * iniciar * uma conexão de saída (de VOCÊ -> AMIGO) ou de entrada (de AMIGO -> VOCÊ), mas o tráfego flui para os dois lados quando a conexão é estabelecida.

Consulte [doc/configure.md](doc/configure.md) para obter mais detalhes sobre configuração,
incluindo como fazer pares com outros nós cjdns por Ethernet e Wi-Fi.


### 4. Proteja seu sistema - verifique se há serviços de escuta

Depois que o nó estiver em execução, você será um host IPv6 recém-criado. Seu sistema operacional pode reconfigurar automaticamente os serviços de rede para usar esse novo endereço.
Se não é isso que você pretende, verifique se não está
oferecendo mais serviços do que você pretendia. ;)

Consulte [doc/network-services.md](doc/network-services.md) para obter instruções.


### 5. Iniciar!

    sudo ./cjdroute < cjdroute.conf

Se você deseja que seus logs sejam gravados em um arquivo:

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

Para parar cjdns:

    sudo killall cjdroute

Se você estiver tendo problemas, use `killall cjdroute` para retornar à sanidade. Use
`pgrep cjdroute` ou `top` para ver se está rodando.

**NOTA!**

Isso inicia o cjdns como usuário root, para que ele possa configurar seu sistema sem se preocupar com permissões. Para iniciar o cjdns como um usuário não root, consulte
[doc/non-root-user.md](doc/non-root-user.md).


### 6. Entre no IRC

Bem-vindo à rede! Agora você é um administrador de rede. Existem responsabilidades inerentes ao administrador da rede, que incluem a disponibilidade, caso haja algo errado com o seu equipamento. Você deve permanecer no [IRC](#community) para que as pessoas possam alcançá-lo.

## Interface de administração

Quando o cjdroute estiver em funcionamento, a interface administrativa estará disponível em
`udp://localhost:11234` (isso pode ser alterado no arquivo de configuração `cjdroute.conf`). Consulte [doc/admin-api.md](doc/admin-api.md) para mais
informações sobre a interface de administração. Existem várias ferramentas no `contrib/`
que pode interagir com ele.

Você pode acessar a API do administrador com:

* o **Python library**; consulte [aqui](contrib/python/README.md).
* o **Perl library**, mantido por Mikey; consulte [aqui](contrib/perl/CJDNS/README).


## Relatar problemas
1. Não reporte neste repositório, em vez disso, https://github.com/hyperboria/bugs/issues
2. Entre no IRC e converse com alguém
3. O que vai acontecer é
  * Alguém quer consertar
  * Você quer consertá-lo
  * Ninguém se importa com isso e será esquecido por um tempo e talvez alguém o acerte mais tarde
  e conserte-o, caso contrário ele será apagado em uma refatoração
  * Ninguém pode consertá-lo no momento, mas é considerado digno de lembrança, porque possui ótimas
  importante para a maneira como o código é desenvolvido, nesse caso, ele precisa ser explicado em detalhes técnicos.
  termos por alguém com forte familiaridade com o código. Eles farão uma solicitação de recebimento para o
  diretório docs/bugs.

### Segurança
Os problemas de segurança devem ser relatados no IRC da mesma forma que outros bugs. Não temos um fechado
grupo de pessoas com conhecimentos especiais, o que significa que o método padrão de relatório de segurança é
transparência completa.

Consulte: [security_specification.md](https://github.com/cjdelisle/cjdns/blob/master/doc/security_specification.md) para ver se um possível problema de segurança é realmente um problema de segurança.

Naquela época do ano novamente ... Hora de alguns projetos de código aberto!
[![Hacktoberfest](https://img.shields.io/badge/Open%20Source-Hacktoberfest-orange.svg)](https://hacktoberfest.digitalocean.com/)

[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns no Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: https://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns na Wikipedia]: https://en.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[English](README.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)

Безопасная, зашифрованная сеть для обычных людей.

Cjdns — это зашифрованная IPv6 сеть, в которой используются публичные ключи шифрования для присвоения публичного адреса и распределённой таблицы маршрутизации (DHT). Это позволяет создавать сети с очень простой настройкой, которые будут защищены от потенциальных проблем ныне существующих IPv4 и IPv6 сетей.

[![Build Status](https://api.travis-ci.org/cjdelisle/cjdns.png?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![For next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)

## Рекомендательные письма

    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


## Как работает маршрутизация?

Чтобы понять как работает маршрутизация в cjdns, очень важно понимать, как она работает в существующем интернете. На каждой развилке маршрутизатор читает адрес назначения в пакете и решает, куда его направить.

В cjdns сети на каждом пакете, который идет на локальный (программный) маршрутизатор, отмечается наилучший маршрут для него. Лучший маршрут — это самый близкий (физически) к вам роутер, имеющий адрес, близкий по значению к адресу назначения.

Следующий роутер в цепочке также читает данное поле и отправляет пакет в нужном направлении. Кроме того, роутеры постоянно взаимодействуют друг с другом, обмениваясь информацией по маршрутам с помощью Kademlia DHT.


## А что насчёт DNS?

DNS — это сложная система, которую трудно реализовать без участия какого-либо центрального сервера.

Сообщество cjdns ещё не решило, какой вектор развития примет разработка DNS в этой сети; если у вас есть идеи — то, мы вас ждём в IRC.


## Почему проект называется cjdns?

Cjdns — это совмещение двух слов cjd и DNS, но проект поменял направление своего развития практически в начале, и у него всё еще нет замены DNS, но имя осталось. Можете придумать свою расшифровку названия, если хотите.


Спасибо за ваше время и интерес,
Caleb James DeLisle  ==  cjdelisle  ==  cjd

## Community

* irc://irc.efnet.org/#cjdns_ru ([web client][IRC Web])
* [Hyperboria][]
* [/r/darknetplan][]
* [#cjdns on Twitter][]


## Documentation

* [Project Goals](doc/projectGoals_ru.md)(RU)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns on Wikipedia][]

Advanced configuration:

* [Setup a cjdns NAT gateway for your LAN](doc/nat-gateway.md)
* [Install cjdns on OpenIndiana](doc/open-indiana.md)

### License

[Available here](LICENSE)

Thank you for your time and interest,

The cjdns developers.


--------------------------------------------------------------------------------


# Как установить cjdns

Эти инструкции предназначены для дистрибутива Debian и аналогичных (Ubuntu, Mint).

## 0. Устанавливаем утилиты компиляции.

Установка  [Node.js](https://nodejs.org/) желательна, но не
обязательна. Если Node.js не найден в процессе установки или его
версия слишком старая — он будет загружен автоматически при установке.

#### Дистрибутивы основанные на Debian:

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

#### Дистрибутивы основанные на Fedora 22+:

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

#### Дистрибутивы основанные на RHEL (добавляет репозиторий EPEL):

    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

#### Сборка из пакета:

    sudo yum localinstall https://kojipkgs.fedoraproject.org//packages/cjdns/17.4/4.el6/src/cjdns-17.4-4.el6.src.rpm

Если вы используете ноутбук и вводите его в спящий режим, то cjdroute понадобится
несколько минут, чтобы приготовить кофе и понять, что произошло. Вы можете значительно
ускорить это следующим способом:

    systemctl enable cjdns-resume

Сервис возобновления перезапускает cjdns, если система выходит из спячки.

#### Gentoo

    emerge --ask nodejs sys-devel/gcc dev-lang/python:3.4 dev-vcs/git

#### macOS:

Установка с [Homebrew](https://brew.sh/):

    brew install cjdns

Установка с [MacPorts](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

    pkg_add git node gcc gmake bash

Выберете версию gcc-4.8.1p2 или новее.

#### FreeBSD:

Всё что вам необходимо, доступно в коллекции портов FreeBSD.

    pkg install gmake node

#### Arch:

Вы можете установить cjdns выполнив следующее
    pacman -S cjdns

Если вы хотите скомпилировать самостоятельно, то всё что вам необходимо может быть установлено следующей командой

    pacman -S nodejs git base-devel

Как альтернативный вариант, вы можете установить через AUR из пакета `cjdns-git`.

После установки файл конфигурации находится тут `/etc/cjdroute.conf`.
Для запуска сервиса `cjdns.service`, выполните:

    systemctl start cjdns

Для остановки:

    systemctl stop cjdns

#### Gentoo:

cjdns еще не находится в главном репозитории Gentoo, поэтому вам придется использовать наложение.
Самый простой способ - это использовать Layman, но вы можете сделать это и вручную.

##### Layman:

Во-первых, вам нужно установить layman.

    emerge layman

Если layman установлен правильно, то вы можете добавить наложение

    layman -f
    layman -a weuxel

Для будущего обновления использования наложения

    layman -S

Теперь вы можете установить cjdns

    emerge cjdns

##### Ручками:

Вам придется клонировать репозиторий наложения

    cd /opt
    git clone https://github.com/Weuxel/portage-weuxel.git

Теперь скажите portage использовать этот репозиторий

    cd /etc/portage/repos.conf/

Создайте файл `portage-weuxel.conf` с текстом:

    [weuxel]
    location = /opt/portage-weuxel
    masters = gentoo
    auto-sync = yes

Теперь синхронизируйте

    emerge --sync

И установите cjdns

    emerge cjdns

#### Автоматическое обнаружение сбоев и перезагрузка.

Скопируйте скрипт инициализации openrc из `contrib/openrc` в `/etc/init.d/`, и модифицируйте параметры `CONFFILE` и `command` в соответствии с вашими требованиями.

Затем запустите выполнив:

    /etc/init.d/cjdns start

Настройте систему init для автоматического запуска

    rc-update add cjdns default

Скопируйте скрипт service_restart `contrib/gentoo/service_restart.sh` в любой удобный каталог в
вашей системе, и измените адрес электронной почты. Если вы не хотите получать уведомления, то закомментируйте всю строку.
Теперь добавьте запись в crontab, наподобие этой

    # Restart crashed Services
    * * * * *       root	/path/to/script/service_restart.sh

#### Solus:

Зависимости:

    sudo eopkg install nodejs git build-essential system.devel python gcc binutils kernal-headers xorg-server-devel

Затем следуйте шагам ниже.

## 1. Скачиваем cjdns из GitHub.

Склонируйте репозиторий из GitHub:

    git clone https://github.com/cjdelisle/cjdns.git cjdns
    cd cjdns

## 2. Компилируем.

    ./do

Дождитесь сообщения `Build completed successfully, type ./cjdroute to begin setup.`, и как только оно появится — действуйте дальше:

--------------------------------------------------------------------------------


# Установка

Запустите cjdroute без параметров для отображения информации и доступных опций:

    ./cjdroute

## 0: Убедитесь, что у вас всё установлено корректно.

    LANG=C cat /dev/net/tun

Если ответ: `cat: /dev/net/tun: File descriptor in bad state`,то всё отлично!

Если ответ: `cat: /dev/net/tun: No such file or directory`,то просто создайте его:

    sudo mkdir /dev/net ; sudo mknod /dev/net/tun c 10 200 && sudo chmod 0666 /dev/net/tun

Затем снова `cat /dev/net/tun`.

Если ответ: `cat: /dev/net/tun: Permission denied`, вы скорее всего используете виртуальный сервер (VPS) на основе технологии виртуализации OpenVZ. Попросите своего провайдера услуг включить TUN/TAP устройство, это стандартный протокол, ваш провайдер должен быть в курсе.


## 1: Генерируем новый файл с настройками.

    ./cjdroute --genconf >> cjdroute.conf

## 2: Найдите пира.

Для доступа в сеть вам потребуется человек который уже в сети.

Найти людей, которые готовы подключить вас, вы можете найти в IRC канале, либо можете использовать данные тестового пира http://hype.rusblock.com/Public_peers.html

### Англоязычный канал:

  * irc://irc.EFNet.org/#cjdns
  * http://chat.efnet.org:9090/?channels=%23cjdns&Login=Login

### Русскоязычный канал:

  * irc://irc.EFNet.org/#cjdns-ru
  * http://chat.efnet.org:9090/?channels=%23cjdns-ru&Login=Login

## 3: Заполните информацию о найденном пире.

В файле cjdroute.conf вы увидите:

            // Nodes to connect to.
            "connectTo":
            {
                // Add connection credentials here to join the network
                // Ask somebody who is already connected.
            }

После добавления данных пира он будет выглядеть как-то так:

            // Nodes to connect to.
            "connectTo":
            {
                "0.1.2.3:45678":
                {
                    "login": "user-login",
                    "password": "thisIsNotARealConnection",
                    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile.k"
                }
            }

Вы можете добавлять столько данных для подключения к пирам, сколько захотите.

Ваши собственные данные для подключения _к вам_ находятся в секции "authorizedPasswords" в JSON формате. Не редактируйте их — дайте их тем, кто хочет к вам подключится.

Выглядит это так:

        /* These are your connection credentials
           for people connecting to you with your default password.
           adding more passwords for different users is advisable
           so that leaks can be isolated.

            "your.external.ip.goes.here:12345":
            {
                "login": "user-login",
                "password": "thisIsNotARealConnectionEither",
                "publicKey": "thisIsAlsoJustForAnExampleDoNotUseThisInYourConfFile.k"
            }
        */

`your.external.ip.goes.here` нужно заменить на ваш IPv4 адрес, который люди будут использовать для подключения к вам через интернет.

Страница [rfcs/configure.md](rfcs/configure.md) содержит больше информации о подключении и настройке.

## 4: Безопасность — Проверьте открытые порты.

Как только вы подключились к глобальной сети cjdns — вы стали обладателем публичного IPv6 адреса. Убедитесь, что запущенные на вашей машине сервисы недоступны из внешней сети.

Подробнее: [doc/network-services.md](doc/network-services.md)


## 5: Запускаем!

    sudo ./cjdroute < cjdroute.conf

Если вы хотите записывать логи в файл, то:

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

Остановка cjdns осуществляется следующим образом:

    sudo killall cjdroute

Если вы испытываете проблемы при использовании `killall cjdroute`. Используйте `pgrep cjdroute` или `top` для определения, запущен ли он.

## 6: Войдите в IRC

Добро пожаловать в сеть, в которой вы настоящий системный администратор.
По любым вопросам вы можете проконсультироваться в IRC: канал `#cjdns` на сервере `irc.efnet.org` или используйте канал `#cjdns-ru` который на русском языке и на том же сервере.


## Заметки

Нормальная установка cjdns подразумевает запуск от имени администратора. Если вы не считаете нужным давать такие привилегии cjdns, то вы можете воспользоваться инструкцией ниже, запустив его не от root.

Никому не передавайте свой файл настроек: именно он гарантирует вашу безопасность в сети и хранит ваш идентификатор. Если у вас его украдут, то ваша безопасность будет скомпрометирована, и злоумышленник сможет представиться вами в сети.

    chmod 400 cjdroute.conf
    mkdir /etc/cjdns && cp ./cjdroute.conf /etc/cjdns/


# Получаем доступ к интерфейсу администратора в cjdns

Когда cjdroute запущен и работает, интерфейс администратора доступен по адресу localhost:11234 (обратите внимание, что это не веб-интерфейс, веб-интерфейс вы можете получить используя nodejs cjdns admin). Настройки порта и пароля для доступа к интерфейсу администратора доступны в файле cjdroute.conf.

Каким образом получить доступ к данному интерфейсу, вы можете прочитать по этим ссылкам: [doc/admin-api.md](doc/admin-api.md).


Библиотека для python
---------------------

Cjdns поставляется с библиотекой для python, которая позволяет получить доступ к admin API. Больше информации вы можете получить здесь: [readme](contrib/python/README.md).


Библиотека для perl
-------------------

Библиотека для perl поддерживается разработчиком Mikey. Инструкции по использованию можно получить тут: [readme](contrib/perl/CJDNS/README).

# Отправка отчёта об ошибках

1. Не отправляйте отчёт в этот репозиторий, вместо этого отправляйте его на https://github.com/hyperboria/bugs/issues
2. Расскажите об этом кому-нибудь в IRC
3. Произойдёт что-то из этого:
 * Кто-то почувствует в себе силы исправить это
 * Вы почувствуете в себе силы исправить это
 * Никого не заинтересовала эта ошибка, и она будет забыта на какое-то время, и, может быть, кто-то исправит её позже, либо, в противном случае, ошибка исчезнет во время рефакторинга
 * В настоящий момент никто не может исправить эту ошибку, но она заслуживает внимания, так как может сильно воспрепятствовать разработке в будущем, и в этом случае ошибка должна быть технически детально описана человеком, хорошо знакомым с кодом. Он отправит запрос в директорию docs/bugs.

## Безопасность

Об ошибках безопасности следует сообщать в IRC так же, как и о других ошибках. У нас нет закрытой группы людей со специальными знаниями, поэтому по умолчанию все отчёты об ошибках безопасности являются полностью открытыми.
Проверить, является ли потенциальная проблема безопасности действительно проблемой безопасности можно по следующей ссылке: https://github.com/cjdelisle/cjdns/blob/master/doc/security_specification.md

# Продвинутая настройка

* [Запуск cjdns не от root](doc/non-root-user_ru.md)
* [Настройка ПК как cjdns NAT gateway для вашей домашней сети](doc/nat-gateway.md)
* [Установка cjdns на OpenIndiana](doc/open-indiana.md)

Снова это время года... Время для проектов с открытым исходным кодом!
[![Hacktoberfest](https://img.shields.io/badge/Open%20Source-Hacktoberfest-orange.svg)](https://hacktoberfest.digitalocean.com/)

[beyond pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns_ru
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns on Twitter]: https://twitter.com/hashtag/cjdns
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns on Wikipedia]: https://ru.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://ru.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://ru.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[English](README.md)
[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[繁體中文](README_ZHT.md)
[Español](README_ES.md)
[Français](README_FR.md)

#### *Datornätverk - Ett nytt sätt*

Cjdns är ett krypterat IPv6-nätverk. Adresser i nätverket baseras på assymetrisk
kryptografi och paket dirigeras i nätverket genom att använda en s.k. distribuerad
hashtabell (DHT, eller Distributed Hash Table på engelska). Genom denna design
uppnås ett nätverk som knappt kräver någon konfiguration. Vi blir också av med
många skalnings- och säkerhetsproblem som andra nätverk har.

[![Build Status](https://travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![tip for next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![irc](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)

## Vitsord

    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

## Community

* [irc://irc.efnet.org/#cjdns][IRC Web]
* [Hyperboria][], det största cjdns-nätverket, över 2100 noder i Oktober 2015.
* [/r/darknetplan][]
* [#cjdns på Twitter][]

## Dokumentation

* [Projectmål](doc/projectGoals.md)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns på Wikipedia][]

Avancerad konfiguration:

* [Sätt upp en cjdns NAT gateway till ditt LAN (EN)](doc/nat-gateway.md)
* [Installera cjdns på OpenIndiana (EN)](doc/open-indiana.md)

Tack för visat intresse,

- Utvecklarna av Cjdns.

--------------------------------------------------------------------------------

## Hur du installerar cjdns

Följande instruktioner är till för Debian-baserade Linux-distributioner eller för macOS.
De bör vara tillräckligt informativa för att kunna anpassas till andra distributioner -
förvänta dig dock inte att de kommer fungera rakt av.

### 0. Installera beroenden

Cjdns byggsystem beror av [Node.js](http://nodejs.org/). Det är att föredra om du
kan installera node.js på din maskin, men det är inte nödvändigt. Om node.js inte finns
installerat eller om det är en oacceptabel version kommer node.js att laddas ner och
installeras i kodträdet.

#### Debian-distibutioner

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

#### Fedora 22+-distributioner

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

#### RHEL-distributioner

    sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    sudo yum install install nodejs git
    sudo yum install @development-tools

#### macOS:

Installera med [Homebrew](https://brew.sh/):

    brew install cjdns

Installera med [MacPorts](https://www.macports.org/):

    sudo port install cjdns

#### OpenBSD:

OpenBSD är tyvärr inte stabil just nu.

    pkg_add git node gcc gmake bash

Välj gcc version 4.8.1p2 eller senare.

#### FreeBSD:

Allt du behöver finns tillgängligt i FreeBSD' ports.

    pkg install gmake node

### 1. Hämta cjdns från GitHub

Clone'a repositoryt från GitHub och byt till katalogen cjdns:

    git clone https://github.com/cjdelisle/cjdns.git cjdns
    cd cjdns

### 2. Bygg

    ./do

Vänta tills du ser följande meddelande `Build completed successfully, type ./cjdroute to begin setup.`,
fortsätt sedan med följande:

--------------------------------------------------------------------------------

## Upplägg

Kör cjdroute utan argument för HJÄLP:

    ./cjdroute

### 0. Kontrollera att du har allting som behövs.

    LANG=C cat /dev/net/tun

Om det står: `cat: /dev/net/tun: File descriptor in bad state` Bra!

Om det står: `cat: /dev/net/tun: No such file or directory`, skapa den med följande kommandon:

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

Prova sedan `cat /dev/net/tun` igen.

Om det står: `cat: /dev/net/tun: Permission denied` så använder du troligen en VPS
baserad på OpenVZ's virtualiseringsplattform. Fråga din leverantör om de kan
tillåta/öppna upp TUN/TAP - denna terminologi är standard så de bör förstå vad du
ber dem om. Om du använder macOS kan du ignorera detta steg.


### 1. Skapa en ny konfigurationsfil

    ./cjdroute --genconf >> cjdroute.conf

**Skydda din konfigurationsfil!**

En borttappad konfigurationsfil innebär att du tappat bort både ditt lösenord
och dina uppkopplingar och alla som någonsin varit uppkopplade mot dig,
kan inte längre göra det. En komprometterad konfigurationsfil innebär att någon
annan kan agera som dig på nätverket.

För att generera en konfigurationfil med rättigheter där bara du kan läsa
och skriva till den:

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


### 2. Hitta en vän

För att koppla upp dig mot ett redan existerande nätverk (t ex Hyperboria)
måste du koppla upp dig till någon som redan tillhör nätverket. Detta är
nödvändigt av ett antal orsaker:

1. Det hjälper till att förhindra missbruk då det är osannolikt att
   dåliga människor kommer missbruka ett system de fått tillgång till
   från en annan människa som de på något sätt har en relation till.
2. Cjdns är inte tänkt att vara ett overlay-nätverk ovanpå internet,
   utan tanken är att det ska byta ut det. Varje uppkoppling kommer i sinom
   tid att bytas ut mot en sladd, en fiberoptisk kabel eller en wifi.
3. Vid händelse av meningsskiljaktigheter kommer det finnas en "kedja
   av vänner" som länkar ihop alla involverade så det finns redan en
   bas för att komma fram till en lösning.

För att hitta en vän, gå med i vår [community](#community). Kolla även in
[Hyperboria Map][] för att hitta peers nära dig.


### 3. Koppla din nod till din väns nod

**För att skapa en utgående uppkoppling**

Leta upp `connectTo`-attributet i din konfigurationsfil:

``` javascript
// Nodes to connect to.
"connectTo":
{
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.
}
```

En konfigurationsfil med flera utgående vän-noder, kan se ut:

``` javascript
// 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"
    }
}
```

Du kan lägga till så många uppkopplingar du vill till `connectTo`-attributet.


**För att tillåta din vän att göra ingående uppkoppling**

Leta upp `authorizedPasswords`-attributet i din konfigurationsfil:

``` javascript
"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"}

],
```

En konfigurationsfil med flera vän-noder uppsatta som ingående kan se ut:

``` javascript
"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"}
],
```

Du behöver ge William Jevons (som kopplar upp sig mot dig) följande fyra saker:

1. Din externa IPv4-adress
2. Den port som finns i din konfigurationsfil här:

    `// Bind to this port.
    "bind": "0.0.0.0:yourportnumberishere",`

3. Deras unika lösenord som du kommenterade ut eller skapade: `"password": "thisisauniquestring_002"`
4. Din publika nyckel: `"publicKey": "thisisauniqueKEY_001.k"`

Hens loginuppgifter kommer då se ut som följer (med din IPv4-adress och port):

```javascript
"1.2.3.4:56789": {
    "login": "William Jevons",
    "password": "thisisauniquestring_002",
    "publicKey": "thisIsJustForAnExampleDoNotUseThisInYourConfFile_1.k"
}
```

Var vänlig notera att både du och din vän kan *påbörja* en uppkoppling
outbound (från DIG --> VÄN) eller inbound (från VÄN --> DIG) men trafiken
flödar i båda riktningarna så fort ni har kopplat upp er mot varandra.

Se [doc/configure.md](doc/configure.md) för mer information om konfigurering,
inkluderat hur du kan koppla upp dig mot andra cjdns noder över ethernet och wifi.


### 4. Säkra ditt system - kontrollera lyssnande tjänster

När din nod är uppe och kör är den en IPv6 host. Operativsystemet kan
automatiskt omkonfigurera nätverksservices att använda den nya adressen.
Om detta *inte* är vad du ville borde du kontrollera att du inte erbjuder
fler tjänster än vad du avsåg. ;)

Se [doc/network-services.md](doc/network-services.md) för instruktioner.


### 5. Starta din nod!

    sudo ./cjdroute < cjdroute.conf

Om du vill logga till fil:

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

För att avsluta cjdns:

    sudo killall cjdroute

`sudo killall cjdns` är också användbart om du får problem. Använd
`pgrep cjdroute` eller `top` för att kolla om cjdroute kör eller ej.

*OBS!*

Detta kör cjdns som användaren root så det kan konfigurera
ditt system utan att behöva bry sig om rättigheter. För att starta cjdns utan
root-rättigheter, se [doc/non-root-user.md](doc/non-root-user.md).


### 6. Logga in på IRC

Välkommen till nätverket! Du är nu en nätverksadministrator och med det
kommer vissa skyldigheter, som bl.a. innebär att du bör vara tillgänglig
i händelse av att någonting inte stämmer med din utrustning. Enklast är
att logga in på [IRC](#community) så att andra kan nå dig.


## Admingränssnittet

När cjdroute är uppe och kör så finns det ett admingränssnitt tillgängligt
på `udp://localhost:11234` (detta kan ändras i `cjdroute.conf`).
Se [doc/admin-api.md](doc/admin-api.md) för mer information om admingränssnittet.

Det finns flera olika verktyg i `contrib/` som kan interagera med det, bl.a.:

* **python**; se [contrib/python/README.md](contrib/python/README.md).
* **perl**, maintained by Mikey; se [contrib/perl/CJDNS/README](contrib/perl/CJDNS/README).

[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: https://hyperboria.net
[/r/darknetplan]: https://www.reddit.com/r/darknetplan
[#cjdns på Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: https://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns på Wikipedia]: https://en.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: https://geti2p.net/en/
[Freenet]: https://freenetproject.org

# cjdns

[English](README.md)
[Русская версия](README_RU.md)
[Hrvatski](README_HR.md)
[Svenska](README_SV.md)
[Ελληνικά](README_GR.md)
[Deutsch](README_DE.md)
[Español](README_ES.md)
[Français](README_FR.md)

#### *重朔整個網路*

Cjdns 利用「加密的IPv6」及「公鑰加密」來分配網路地址並利用「Distributed Hash Table」逕行路由。它能提供近似「零配置網路（Zero-Configuration Networking）」，並且能防範在現有網路中存在的很多和安全、可擴展性相關的問題。

[![Build Status](https://travis-ci.org/cjdelisle/cjdns.svg?branch=master)](https://travis-ci.org/cjdelisle/cjdns)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/387/badge)](https://bestpractices.coreinfrastructure.org/projects/387)
[![tip for next commit](https://tip4commit.com/projects/941.svg)](https://tip4commit.com/github/cjdelisle/cjdns)
[![irc](https://img.shields.io/badge/irc%20chat-%23cjdns-blue.svg)](https://kiwiirc.com/client/irc.efnet.org/?nick=visitor|?#cjdns)

## 評價

    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

## 社群

* [irc://irc.efnet.org/#cjdns][IRC Web]
* [Hyperboria][] 目前最大的 cjdns 網路，至2015年10月止有2100個節點。
* [Project Meshnet][]
* [/r/darknetplan][]
* [#cjdns on Twitter][]


## 相關文件

* [Project Goals](doc/projectGoals.md)
* [Cjdns Whitepaper](doc/Whitepaper.md)
* [Cjdns on Wikipedia][]

進階配置（英文）:

* [Setup a cjdns NAT gateway for your LAN](doc/nat-gateway.md)
* [Install cjdns on OpenIndiana](doc/open-indiana.md)

感謝你的時間和關注

cjdns 開發人員 敬上

--------------------------------------------------------------------------------

## 如何安裝 cjdns

這些說明雖然是在基於 Debian 的 Linux 發行版系統與 macOS 系統上的，但是已經為在其它發行版作業系統安裝提供了足夠多的信息，只是不要期望可以一字不差的執行指令。

### 0. 安裝相關程式

在兩種作業系統上安裝 [Node.js](http://nodejs.org/)，非必要但強烈建議。
如無 Node.js 或版本錯誤，安裝程式會自動下載安裝至源代碼資料夾中。

#### Debian 系統:

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

#### Fedora 22+ 系統:

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

#### RHEL 系統 (會新增 EPEL 的 Repository):

    sudo yum localinstall https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    sudo yum install install nodejs git
    sudo yum install @development-tools

#### macOS 系統:

利用 [Homebrew](https://brew.sh/) 安裝:

    brew install cjdns

利用 [MacPorts](https://www.macports.org/) 安裝:

    sudo port install cjdns

#### OpenBSD 系統:

非常遺憾目前 OpenBSD 還在實驗階段。

    pkg_add git node gcc gmake bash

選擇 gcc-4.8.1p2 之後版本。

#### FreeBSD 系統:

所有所需相關程式已預先在 FreeBSD' ports 編譯完成。

    pkg install gmake node

#### Arch 系統:

你可以用以下指令安裝 cjdns

    pacman -S cjdns

如果你需要從原始碼重新編譯，所有需要的程式可以用以下方式安裝

    pacman -S nodejs git base-devel

另外，你可能會想利用 AUR 安裝包裝 `cjdns-git`。
安裝完成後，配置檔在 `/etc/cjdroute.conf`。
用以下指令啟動 `cjdns.service`：

        systemctl start cjdns

停止指令：

       systemctl stop cjdns

### 1. 從 GitHub 取得 cjdns

從 Github 複製 Repository 並切換至下載檔案資料夾：

    git clone https://github.com/cjdelisle/cjdns.git cjdns
    cd cjdns

### 2. 初始化

    ./do

當你看見 `Build completed successfully, type ./cjdroute to begin setup.`，
再繼續以下步驟:

--------------------------------------------------------------------------------

## 安裝

不帶參數執行 cjdroute 時會顯示幫助信息：

    ./cjdroute

### 0. 確定你已經準備好必要的資料。

    LANG=C cat /dev/net/tun

如果顯示： `cat: /dev/net/tun: File descriptor in bad state` 表示安裝成功!

如果顯示： `cat: /dev/net/tun: No such file or directory`，利用以下指令建立檔案：

    sudo mkdir -p /dev/net &&
    sudo mknod /dev/net/tun c 10 200 &&
    sudo chmod 0666 /dev/net/tun

然後再次執行 `cat /dev/net/tun` 。

如果顯示： `cat: /dev/net/tun: Permission denied` 你大概在使用一個基於 OpenVZ Virtualization Platform 的 VPS（虛擬專用伺服器）。
向你的服務供應商要求啟用 TUN/TAP 設備 - 這是標準協議，所以他們應當明白你的意思。

如果你用 macOS 請忽略這個步驟。


### 1. 產生一個新的配置檔（請先閱讀下方「保護好你的配置檔」部份）

    ./cjdroute --genconf >> cjdroute.conf

**保護好你的配置檔！**

失去配置檔代表你丟失密碼以及已建立的連結，其他以你做為接入點的節點也會無法與你連線。
配置檔被侵入代表他人可以在網路上假裝是你。

產生一個僅有你的使用者才有權限讀寫的配置檔：

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


### 2. 找一個朋友

為了加入一個已經存在的網路（例如：Hyperboria），你需要與一個已經在該網路中的節點連接。
原因如下：

1. 因為有心人士較不會在「他人好心邀請下加入」後濫用系統。
2. 此程式目的並非要在現有網路之上並行，而是取代現有網路。各個連線會在未來被實體線路或無線網路取代。
3. 如果有任何異議，會有「朋友的朋友」將兩方連在一起，這使和解更容易達成

要找朋友，請發聲並加入我們的 [社群](#社群)。另外，來[Hyperboria Map][] 找尋鄰近的節點。


### 3. 連接你與朋友的節點

**由你啟始連線（向外）**

在你的配置檔，你可以找到：

``` javascript
// Nodes to connect to.
"connectTo":
{
    // Add connection credentials here to join the network
    // Ask somebody who is already connected.
}
```

一個包含許多朋友節點（向外）的配置檔類似這樣：

``` javascript
// Nodes to connect to.
"connectTo":
{
    //朋友_1 (IPv4: 0.1.2.3; IPv6 fcaa:5bac:66e4:713:cb00:e446:c317:fc39)
    "0.1.2.3:45678":
    {
        "login": "k.alexander"
        "password": "這不是真的連線_1",
        "publicKey": "這只是範例請不要真的在配置檔中用這串字_1.k"
    }

    //朋友_2 (IPv4: 5.1.2.3; IPv6 fcbb:5bac:66e4:713:cb00:e446:c317:fc39)
    "5.1.2.3:5678":
    {
        "login": "k.alexander"
        "password": "這不是真的連線_2",
        "publicKey": "這只是範例請不要真的在配置檔中用這串字_2.k"
    }
}
```

你可以依照 JSON 語法在 `connectTo` 屬性中加入無限個連線。


**讓你的朋友啟始連線（向內）**

在配置檔中，你可以找到：

``` javascript
"authorizedPasswords":
[
    // A unique string which is known to the client and server.
    {"password": "獨一無二的密碼（請不要輸入中文）_001"}

    // More passwords should look like this.
    // {"password": "獨一無二的密碼（請不要輸入中文）_002"}
    // {"password": "獨一無二的密碼（請不要輸入中文）_003"}
    // {"password": "獨一無二的密碼（請不要輸入中文）_004"}
    ...

    // "你的.對外.IP.位址:45678":{"password": "獨一無二的密碼（請不要輸入中文）_001","publicKey":獨一無二的金鑰_001.k"}

],
```

一個有許多朋友節點的配置檔，向內連線應該長這樣：
``` javascript
"authorizedPasswords":
[
    // A unique string which is known to the client and server. 在此輸入讓他人對你連線的密碼
    {"password": "獨一無二的密碼（請不要輸入中文）_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": "獨一無二的密碼（請不要輸入中文）_002", "user": "William Jevons"}
    //Marilyn Patel (IPv4: 5.1.2.3; IPv6 fcbb:5bac:66e4:713:cb00:e446:c317:fc39)
    {"password": "獨一無二的密碼（請不要輸入中文）_003", "user": "Marilyn Patel"}
    // {"password": "獨一無二的密碼（請不要輸入中文）_004"}
    ...

    // "你的.對外.IP.位址:45678":{"password": "獨一無二的密碼（請不要輸入中文）_001","publicKey":獨一無二的金鑰_001.k"}
],
```


你必須給 William Jevons (對你而言是向內連線) 下方四項資訊：

1. 你的外部 IPv4
2. 你可以在配置檔找到的埠號：

    `// Bind to this port.
    "bind": "0.0.0.0:你的埠號在這裡",`

3. 為你朋友設定或取消註解的唯一密碼： `"password": "獨一無二的密碼（請不要輸入中文）_002"`
4. 你的公鑰： `"publicKey": "獨一無二的金鑰_001.k"`
5. 他的登入名稱： "William Jevons"

他的配置檔中會看起來像這樣(包含你的 IPv4 和 埠號):

```javascript
"1.2.3.4:56789": {
    "login": "William Jevons",
    "password": "獨一無二的密碼（請不要輸入中文）_002",
    "publicKey": "這只是範例請不要真的在配置檔中用這串字_1.k"
}
```

請記得你與你朋友可以啟始「向外（你 --> 朋友）」或「向內（朋友 --> 你）」連線，但當通道建立後兩方皆可使用。

更進階的配置請閱讀 [doc/configure.md](doc/configure.md)，包括如何透過乙太網路與Wifi連線。

### 4. 保護你的系統 - 檢查正在使用網路的程式

當你的節點開始運行，你的電腦便成為一個新的 IPv6 伺服。你的作業系統可能會自動重新配置網路程式來使用這個新的網路位址。
如果你並不希望這麼做，你應確認你並沒有提供一些你不打算公開的服務。 ;)

更多資料請查閱 [doc/network-services.md](doc/network-services.md)。


### 5. 開始使用！

    sudo ./cjdroute < cjdroute.conf

如果你希望將紀錄存成一個檔案：

    sudo ./cjdroute < cjdroute.conf > cjdroute.log

停止 cjdns:

    sudo killall cjdroute

如果出現問題用 `killall cjdroute` 指令來結束一切。
用 `pgrep cjdroute` 或 `top` 指令來確認是否正在執行。

**注意！**

這將會讓 cjdns 以 Root 權限執行並設定你的系統，避免要求權限等提示。 請參閱[doc/non-root-user.md](doc/non-root-user.md) 來以非 Root 權限執行。


### 6. 加入 IRC

歡迎來到這個網絡！ 你現在是一個網管了。 這代表你有些成一個網管的責任，包括當你的設備出狀況時必須能回應。你應當在 [IRC](#community) 保持在線，這樣其他人才能與你聯繫。


## 管理者界面

當 cjdroute 正在執行時，你可以在 `udp://localhost:11234` 看到管理者界面 (這可以在 `cjdroute.conf` 更改). 這個檔案 [doc/admin-api.md](doc/admin-api.md) 有更多有關管理者界面的資訊。一些在 `contrib/` 的工具可以配合使用。

你可以透過以下方式使用 Admin API ：

* **Python library**; 按 [這裡](contrib/python/README.md).
* **Perl library**, 由 Mikey 維護; 按 [這裡](contrib/perl/CJDNS/README).


## 回報問題
1. 請不要在此回報問題，有問題請到 https://github.com/hyperboria/bugs/issues 回報
2. 在 IRC 上講
3. 以下是可能發生的
 * 有人主動來解決問題
 * 你主動來解決問題
 * 根本沒人理這問題然後被遺忘，也許某天有人會遇到同樣的問題然後在某次的重構中解決
 * 目前無解但是應該被記住，因為這會影響未來程式開發，這種情況必須被對程式碼有深入理解的人進行解釋。他會提出對 Bug 或文件進行修改

### 安全
安全問題應該同樣與其他 Bug 一樣在 IRC 回報。 我們並沒有一個擁有特殊技術的封閉團隊，所以預設的安全問題回報是完全公開。
請參閱： https://github.com/cjdelisle/cjdns/blob/master/doc/security_specification.md 來確認可能安全問題是真的安全問題。


[IRC Web]: http://chat.efnet.org/irc.cgi?chan=%23cjdns
[Hyperboria]: http://hyperboria.net
[Project Meshnet]: https://projectmeshnet.org
[/r/darknetplan]: http://www.reddit.com/r/darknetplan
[#cjdns on Twitter]: https://twitter.com/hashtag/cjdns
[Hyperboria Map]: http://www.fc00.org/
[Buildbots]: https://buildbot.meshwith.me/cjdns/waterfall

[Cjdns on Wikipedia]: https://en.wikipedia.org/wiki/Cjdns
[Distributed Hash Table]: https://en.wikipedia.org/wiki/Distributed_hash_table
[Beyond Pain]: https://lists.torproject.org/pipermail/tor-dev/2012-October/004063.html
[Kademlia]: https://en.wikipedia.org/wiki/Kademlia

[Tor]: https://www.torproject.org
[I2P]: http://www.i2p2.de
[Freenet]: https://freenetproject.org