i2pcpp is an I2P router written in C++11 by orion. It is targeted for the advanced I2P user demographic.

Currently the router is able to forward traffic between peers. It is unable to do much more at this time.

To compile, you will require the following components:

• Botan 1.11.5
• boost 1.55.0
• cmake 2.8.11 or greater
• sqlite 3.8.0.2 or greater

clang 3.3+ is the only officially supported compiler, but there is an honest effort to be compatible with g++. i2pcpp will always work on the latest release version of FreeBSD.

i2pcpp should be built out of source:

mkdir build; cd build

The following cmake variables are recognized:

• CMAKE_BUILD_TYPE (Debug, Release, or MinSizeRel)
• CMAKE_C_COMPILER
• CMAKE_CXX_COMPILER
• BOOST_INCLUDEDIR
• BOOST_LIBRARYDIR
• BOTAN_INCLUDEDIR
• BOTAN_LIBRARYDIR
• SQLITE3_INCLUDEDIR
• SQLITE3_LIBRARYDIR

Below is an example of how to invoke cmake from within your build directory:

cmake .. -DCMAKE_BUILD_TYPE=Debug

Specify additional variables as necessary.

On most systems you simply need to execute make and everything will be built. On FreeBSD you must use gmake.

One binary, i2p will be produced. If you are building unit tests, a second binary testi2p will be produced.

i2pcpp uses a sqlite database to store RouterInfo, profiles, and configuration data. When running i2pcpp for the first time, this database must be generated:

./i2p --init

This command also generates the proper crypto keys and saves them in the database.

The database will be named i2p.db by default. If you want to override the default database, you can specify the following argument with any command:

./i2p --db=somefile.db

Note that if you do not use the default database file, you must specify this argument for all commands.

Configuration settings are stored in the database. Individual settings are read and written in this way:

./i2p --get key ./i2p --set key value

The following keys are supported:

• ssu_bind ip (IP to bind to)
• ssu_bind_port (Port to bind to)
• ssu_external_ip (IP to advertise)
• ssu_external_port (Port to advertise)
• min_peers (Minimum number of peers to maintain)
• control_server (1 to enable, 0 to disable)
• control_server_ip (IP for the control server to bind to)
• control_server_port (Port for the control server to bind to)

Router Info files generated by the Java i2p client can be imported in to i2pcpp to seed your database:

./i2p --import someRouterInfoFile.dat

These files are usually located in ~/.i2p/netDb/. To recursively import the entire netDb directory, use the '--importdir' argument:

./i2p --importdir /home/you/.i2p/netDb

You can export your own personal Router Info file:

./i2p --export myRouterInfoFile.dat

This allows you to share it with others.

To wipe the database clean of all profiles and routers, use the '--wipe' option:

./i2p --wipe

This will not clear your configuration settings or crypto keys.

By default, i2pcpp prints logging output to stderr. To redirect this to a log file, use the --log (or -l) options:

./i2p -l

This option takes an optional argument to specify the filename to log to. If no argument is provided, the log file i2p.log will be used.

The author hangs out in #i2p-dev on the irc2p network under the nickname orion. A GPG key is included in the doc/ directory which can be used to send private messages and verify commits.

GPG fingerprint: 51F4 F421 CF7C 3CA0 26A4 24CD 83BA E5AA F4D1 5FC8