Uses of Package
net.i2p

Packages that use net.i2p
Package
Description
Class to run the M-Lab Network Diagnostic Tool (NDT).
The Fortuna PRNG from GNU Crypto, updated and modifed for I2P.
The SusiDNS webapp, which is the user interface for the addressbook application and the local naming service (hosts database) implemented in net.i2p.client.naming.
The SusiMail webapp, which implements a webmail interface, POP3 and SMTP client-side protocols, and local caching of email.
Core I2P package, contains information about the I2P version and an entry point to access important elements.
Interfaces for classes to be started and stopped via clients.config.
A system tray control for launching the I2P router console.
Interfaces and factories for the base I2P SDK used to develop applications that communicate through I2P.
Implements the base I2P SDK for developing applications that communicate through I2P.
Provides a standard way for querying the local naming service to resolve a name into a Destination (without the complexity of JNDI).
API, interfaces, and factory for a TCP-like (reliable, authenticated, in order) set of sockets for communicating over the IP-like (unreliable, unauthenticated, unordered) I2P messages.
Implementation of a TCP-like (reliable, authenticated, in order) set of sockets for communicating over the IP-like (unreliable, unauthenticated, unordered) I2P messages.
These classes provide a number of low-level cryptographic routines.
These classes define the common data structures used by the various I2P protocols.
The Invisible Internet Client Protocol (I2CP) allows applications simplified access to the I2P network without requiring them to deal with the issues involved with the Invisible Internet Network Protocol (I2NP).
This package defines the low-level messages sent between routers, called the Invisible Internet Network Protocol (I2NP).
Classes formerly in net.i2p.data but moved here as they are only used by the router.
Desktopgui is a graphical interface to I2P that allows managing the lifecycle of I2P from the system tray.
 
 
 
 
Implementation of preconfigured tunnels, both for clients and servers, and a UI for adding more and editing the configuration.
These classes are the implementation of a definition-based incoming connection filter.
A very simple HTTP server, used only for css and images on HTTP client proxy error pages.
SOCKS 4, 4a, and 5 client tunnels.
Special-purpose client and server tunnels for streaming UDP clients and servers, generally for audio and video streaming.
 
Classes for configuring tunnels, used externally by Android.
The UI for adding tunnels and editing their configurations, implemented as a webapp packaged in i2ptunnel.war.
Classes for starting Jetty, logging requests, and debug logging to the I2P router log.
This is a major rewrite of KBucket, KBucketSet, and KBucketImpl from net.i2p.router.networkdb.kademlia.
The I2P router application handles the I2P network communication.
Classes formerly in net.i2p.crypto but moved here as they are only used by the router.
Implementation of ECIES-X25519-AEAD-Ratchet (proposal 144).
 
Classes to parse the I2P news format, which follows the Atom standard with additional metadata for the I2P update notification feature.
The I2P startup package loads the configuration when I2P is started.
Classes to run offline Sybil analysis, and to store and load the results.
Miscellaneous classes, mostly things that are executed periodically as Jobs, Threads, and SimpleTimer.TimedEvents.
Provides classes for time synchronization using NTP.
The transport system allows the usage of communication layers that are below I2P in the stack, on which I2P messages are sent.
DH key generation.
The NTCP transport allows passing I2P messages on top of TCP.
The UDP transport (also known as 'SSU transport') allows passing I2P messages on top of UDP.
All the work of managing locally created and participating tunnels, creating and handling tunnel messages, and their encryption.
Tunnel creation, tunnel build message handling.
These classes define the several useful utilities used throughout the router.
The router console user interface, implemented in routerconsole.jar, with these classes supporting the webapp in routerconsole.war.
The SAM client API.
Demo and test client classes.
These classes define the statistics package used extensively throughout the I2P router - both for adaptive operation of the router and for debugging.
These classes define the several useful utilities used throughout the router and applications.
 
I2P version of the snark bittorrent client, imported in 2005 and heavily enhanced to add a web UI, DHT support, and other features.
 
Classes only used for, and bundled with, the standalone installation.
The i2psnark user interface, implemented as a webapp in i2psnark.war.