Package net.i2p.router.tunnel
All the work of managing locally created and participating tunnels, creating and handling tunnel messages, and their encryption. Deals with the five different types of tunnel hops: outbound gateway, outbound endpoint, inbound gateway, inbound endpoint, and middle hop. Distributes messages received for each type. Validation, queueing and throttling for each type. Tunnel build message handling is in the pool package.
-
Interface Summary Interface Description FragmentHandler.DefragmentedReceiver Receive messages out of the tunnel endpoint.IVValidator Provide a generic interface for IV validation which may be implemented through something as simple as a hashtable or more a complicated bloom filter.TunnelGateway.QueuePreprocessor TunnelGateway.Receiver TunnelGateway.Sender -
Class Summary Class Description BatchedPreprocessor Batching preprocessor that will briefly delay the sending of a message if it doesn't fill up a full tunnel message, in which case it queues up an additional flush task.BatchedRouterPreprocessor Honor the 'batchFrequency' tunnel pool setting or the 'router.batchFrequency' router config setting, and track fragmentation.BloomFilterIVValidator Manage the IV validation for all of the router's tunnels by way of a big decaying bloom filter.DummyValidator accept everythingFragmentedMessage Gather fragments of I2NPMessages at a tunnel endpoint, making them available for reading when complete.FragmentHandler Handle fragments at the endpoint of a tunnel, peeling off fully completed I2NPMessages when they arrive, and dropping fragments if they take too long to arrive.HashSetIVValidator Deprecated. unusedHopConfig Defines the general configuration for a hop in a tunnel.HopProcessor Take a received tunnel message, verify that it isn't a duplicate, and translate it into what the next hop will want.InboundEndpointProcessor Receive the inbound tunnel message, removing all of the layers added by earlier hops to recover the preprocessed data sent by the gateway.InboundGatewayProcessor Override the hop processor to seed the message with a random IV.InboundGatewayReceiver Handle messages at the IBGW.InboundMessageDistributor When a message arrives at the inbound tunnel endpoint, this distributor honors the instructions (safely)InboundSender Receive the preprocessed data for an inbound gateway, encrypt it, and forward it on to the first hop.OutboundGatewayMessage Stores all the state for an unsent or partially-sent messageOutboundGatewayProcessor Turn the preprocessed tunnel data into something that can be delivered to the first hop in the tunnel.OutboundMessageDistributor When a message arrives at the outbound tunnel endpoint, this distributor honors the instructions.OutboundReceiver We are the outbound gateway - we created this outbound tunnel.OutboundSender Receive the preprocessed data for an outbound gateway, encrypt all of the layers, and forward it on to the first hop.OutboundTunnelEndpoint We are the end of an outbound tunnel that we did not create.PendingGatewayMessage Stores all the state for an unsent or partially-sent messagePumpedTunnelGateway This is used for all gateways with more than zero hops.RouterFragmentHandler Minor extension to allow message history integrationThrottledPumpedTunnelGateway Same as PTG, but check to see if a message should be dropped before queueing it.TrivialPreprocessor Do the simplest thing possible for preprocessing - for each message available, turn it into the minimum number of fragmented preprocessed blocks, sending each of those out.TrivialRouterPreprocessor Deprecated. unusedTunnelCreatorConfig Coordinate the info that the tunnel creator keeps track of, including what peers are in the tunnel and what their configuration is See PooledTunnelCreatorConfig for the non-abstract classTunnelDispatcher Handle the actual processing and forwarding of messages through the various tunnels.TunnelGateway Serve as the gatekeeper for a tunnel, accepting messages, coallescing and/or fragmenting them before wrapping them up for tunnel delivery.TunnelGatewayPumper Run through the tunnel gateways that have had messages added to them and push those messages through the preprocessing and sending process.TunnelGatewayZeroHop Serve as the gatekeeper for a tunnel with no hops, either inbound or outbound.TunnelParticipant Participate in a tunnel at a location other than the gateway or outbound endpoint. -
Enum Summary Enum Description TunnelDispatcher.Location for shouldDropParticipatingMessage()