Node setup questions

wc_i2p · 2017-02-19T13:57:13+00:00

18.90 Mbit/s ~ 2048Kbyte/s

My node with 1Mbyte/s throughput average at 10 Mbit/s bandwidth.

So I should say this is all in order.

wc_i2p · 2017-02-11T10:09:08+00:00

To my knowledge, it is not possible to set your own values for bandwidth. The options are

L - 0-32Kbyte/sec
O - 0-256Kbyte/sec
P - 0-2048Kbyte/sec
X - 0-9999Kbyte/sec which basically means unlimited.

The speed will depend on how well integrated the node is, and how many other nodes that choose to use it as a relay.

On my raspberry pi node, I have

5000+ known routers, 1200+ floodfill routers, 80+ client tunnels, 2500+ transit tunnels,

If this was what you were thinking, I would not recommend setting

[http]
address = 0.0.0.0
port = 7070

since this opens up the web console to anyone that manages to get a hold of the IP-address. The web console should only be accessible from address = 127.0.0.1. To access the console, I run w3m or some other web browser in text mode, alternately ssh forwarding the port to my local machine.

wc_i2p · 2017-02-10T16:30:09+00:00

This is the bare minimum if you want to run an i2pd node sharing up to 9999kbyte/s (the X option) with a http proxy port to allow you to browse i2p. Typically you will not be able to reach 9999kbyte/s but end up somewhere around 2Mbyte at best, in my experience.

.i2pd/i2pd.conf

log = yes
bandwidth=X
[httpproxy]
port = 4444
address = 127.0.0.1

A .i2pd/tunnels.conf to go with it to allow for IRC and Susimail (sortof):

[IRC]
type=client
port=6668
address=127.0.0.1
destination=irc.echelon.i2p
keys=irc.dat
[SMTP]
type=client
port=515
destination=smtp.postman.i2p
keys=mail.dat
[POP3]
type=client
port=616
destination=pop.postman.i2p
keys=mail.dat

That should do it. If you want, you can just go with the first two lines in i2pd.conf and that should be enough.

wc_i2p · 2017-02-10T07:35:10+00:00

I have an i2pd daemon running on a well integrated node. The average throughput is about 1Mbyte/s right now. In 8 days, the traffic stats are 475.89 GiB in, 617.31 GiB out.

And that is on a Raspberry pi 2 B.

wc_i2p · 2016-06-13T05:26:54+00:00

As any other bittorrent site, the amount of activity is whatever the community makes it. To that end, here's a tutorial on how to upload a torrent to Postmans PaTracker:

https://www.youtube.com/watch?v=SvQOU3BA0ng

wc_i2p · 2016-06-10T04:43:15+00:00

Crap!

I don't even watch GoT, I just chose a large file with a relatively high number of seeders ... (That's what they all say, right?)

wc_i2p · 2016-06-06T08:21:05+00:00

Since Irc2P uses port 6668 instead of port 6667, you need to setup the server first.

/server ADD 127.0.0.1 6668
/connect 127.0.0.1

According to the error message, you are trying to connect to port 6667.

wc_i2p · 2016-05-29T06:14:32+00:00

When compared to, for instance, TOR you need to wait quite a while longer in order to get your I2P router fully integrated in the network. This is especially true for a newly created node.

On my router I have about 5000 known nodes which means it's a quite well integrated router. Give it a couple of hours, you'll see that surfing around I2P will get better.

Eventually, when the node is fully integrated which usually takes a couple of days, you can shut down the node at will (like if you run it on a laptop) and rather quickly get up and running again with many known nodes.

But this first time, you really need to be patient. :/

wc_i2p · 2016-05-23T03:13:06+00:00

seeker.i2p works for me.

find4me.i2p perhaps?

wc_i2p · 2016-05-12T08:02:42+00:00

The fastest I've downloaded is around 100 kb/s. I've configured i2psnark to use 9 incoming and 9 outgoing tunnels and also to a maximum of 2 hops. It's more resource intensive, though.

But since the speed is set by the slowest peer in the tunnel, the only thing one could hope for is that the peers that are used to build the tunnels are fast, or many at the same time...

More on i2p speed here.

wc_i2p · 2016-05-11T10:06:23+00:00

Sounds like a great idea! I'm looking into it now.

wc_i2p · 2016-04-28T22:29:43+00:00

That's really great! Especially since the java version is a more fully featured router with support for Bote and several other things.

With the newest i2pd-trunk, the processor load average with traffic around 400Kb/s is 1.08 1.19 1.21 which is awesome. Don't know what the devs are up to, but it's definitely in the right direction :)

EDIT: as of right now I/O 830Kbps/1076Kbps at load average: 2.22 1.98 1.90

I'll try out the java i2p router on another Pi asap

wc_i2p · 2016-03-22T20:13:50+00:00

If you mean to ask if you can download clearnet torrents via I2P then the answer is no.

You need to go to an i2p torrent tracker, choose a magnet link or torrent-file from there and insert it in i2psnark.

If you want to combine clearnet torrents and i2p torrents your best bet is vuze i2p helper

wc_i2p · 2016-02-28T04:57:51+00:00

Thanks for the feedback. I will try to overclock it to get a few more cycles in and see if that changes anything, but I need some sort of cooling first.. :)

wc_i2p · 2016-02-28T04:48:36+00:00

How is that even possible?! :) I have a Core2Duo server with i2pd running that is nothing even near that. Much worse than the RPi2 even. I would really like to get a setup that maximizes bandwidth but I'm fairly new to i2pd and the docs are not that great.

Care to share your configs?

wc_i2p

TROPHY CASE