Strict3443

joined 1 year ago
[–] [email protected] 3 points 1 year ago (1 children)

https://geti2p.net/en/download for the java version, which comes with extra apps. Otherwise, you can go to https://i2pd.website/ for the C++ version which is much lighter and you can just point your browser/torrent clients at the i2p router and you are good to go.

[–] [email protected] 2 points 1 year ago

Then you can register a "domain" on reg.i2p with something like yourname.i2p as well.

[–] [email protected] 3 points 1 year ago (1 children)

You can try using BiglyBT on android following these instructions: https://github.com/BiglySoftware/BiglyBT/wiki/I2P#user-content-biglybt-i2p-and-android

Otherwise, I'd suggest using a desktop to run i2psnark, BiglyBT, or qBittorrent and use i2pd along with those clients.

[–] [email protected] 2 points 1 year ago

Update 2023-10-26

Script was fixed and now correctly copies the reseed certificates from the repo to the data directory. Running the script on a fresh alpine container now results in a working i2pd router with no config necessary. This fixes the "Firewall Status: Unknown" issue.

[–] [email protected] 2 points 1 year ago (1 children)

Can your container reach the internet? If you shell into your container can you ping anything outside your network?

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (3 children)

Step 5 from the guide shows how to test if i2pd is running on your Alpine container. If you are using i2pd on another machine, similar commands will work as well.

For the Alpine Container:

  • Run ps command to see if the i2pd program is running
  • Run service i2pd status to see that status. Ex. * status: started
  • Find your container’s local IP address with ip -4 a and navigate to the i2pd web console at http://:7070
[–] [email protected] 2 points 1 year ago (5 children)

That is i2p-java and i2p+ only. i2pd is only the router which is why it is so small and fast.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (7 children)

Here is a relevant guide: https://geti2p.net/en/about/browser-config

For the IP address, just put in your container's IP address instead of 127.0.0.1

 

This is a little guide to show you how to setup a small container dedicated to an i2p router such as i2pd. This allows for a central router for all your clients on your LAN for example.


Read the guide

i2pd Alpine Setup Script

[–] [email protected] 1 points 1 year ago

You can use one i2pd router for many clients/services, as long as your device can handle it.

[–] [email protected] 3 points 1 year ago

https://geti2p.net/en/docs/how/threat-model#sybil

Good write-up from the I2P team on this topic. Page includes other attack vectors as well.

[–] [email protected] 2 points 1 year ago

This is a good point. I also feel like private trackers are meant for people who actually seed content they download, and just have good intentions to help share content. This also comes with hardware requirements (disk space) sometimes that not everyone has.

[–] [email protected] 2 points 1 year ago (1 children)

It would be nice to have qBittorrent auto add I2P trackers to all torrents to help cross-seed them.

 

cross-posted from: https://lemmy.ml/post/6915117

The release of qBittorrent v4.6.0 stable comes with I2P support. While experimental, we can still get a working torrent setup using qBittorrent now. qBittorrent-nox is the Web-UI only version, and currently it does not have configuration settings in the Web-UI for I2P settings. This guide will show you how to setup qBittorrent-nox and manually change the qBittorrent.conf file to allow for I2P torrenting!

Guide can be found here: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/


qBittorrent Changelog: https://github.com/qbittorrent/qBittorrent/blob/release-4.6.0/Changelog

 

cross-posted from: https://lemmy.ml/post/6915117

The release of qBittorrent v4.6.0 stable comes with I2P support. While experimental, we can still get a working torrent setup using qBittorrent now. qBittorrent-nox is the Web-UI only version, and currently it does not have configuration settings in the Web-UI for I2P settings. This guide will show you how to setup qBittorrent-nox and manually change the qBittorrent.conf file to allow for I2P torrenting!

Guide can be found here: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/


qBittorrent Changelog: https://github.com/qbittorrent/qBittorrent/blob/release-4.6.0/Changelog

 

The release of qBittorrent v4.6.0 stable comes with I2P support. While experimental, we can still get a working torrent setup using qBittorrent now. qBittorrent-nox is the Web-UI only version, and currently it does not have configuration settings in the Web-UI for I2P settings. This guide will show you how to setup qBittorrent-nox and manually change the qBittorrent.conf file to allow for I2P torrenting!

Guide can be found here: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/


qBittorrent Changelog: https://github.com/qbittorrent/qBittorrent/blob/release-4.6.0/Changelog

 

Guide: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how_to_connect_to_irc_on_i2p/

  • IRC hosts on I2P

    • irc.acetone.i2p
    • irc.ilita.i2p
    • irc.r4sas.i2p
    • irc.chaoticninja.i2p
    • irc.coldhell.i2p
    • irc.echelon.i2p
    • irc.kitsune.i2p
    • irc.intr.i2p
    • irc.nerds.i2p
    • irc.ukraine.i2p
    • ircs.nerds.i2p
9
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

Matrix Homeserver: http://matrix-im.i2p

10
I2P Article/Posts Archive (strict3443.codeberg.page)
 

Made a simple Hugo site to host a bunch of articles and posts related to I2P, all in one place. All posts have been translated to English. There are a lot of a good articles on the inner workings of I2P and can help understand I2P better.

Codeberg Pages: https://strict3443.codeberg.page/i2p-info/hugo/public/ Codeberg Repo: https://codeberg.org/Strict3443/i2p-info/src/branch/pages

 

Great video by acetone on how the I2P network works.

Acetone's website: https://bazari.sh/


Alt Link: https://yewtu.be/watch?v=95hSAMEwrlM

 

Good article on how to set up and use Syncthing over I2P for a truly decentralized sync. Helps work around NAT issues and provides good privacy benefits.

Archive Link: https://archive.ph/amWqR

 

cross-posted from: https://lemmy.ml/post/4912475

https://codeberg.org/Strict3443/qbittorrent-i2p-vnc

I have created a Dockerfile which will compile the latest version of qBittorrent which has experimental I2P support into a docker container with VNC support. The reason for this is my server is headless and I wanted to use the v4.6.x version of qBittorrent, but the qbittorrent-nox version of v4.6.x does not have I2P options yet. So I had to build the GUI version on top of a VNC image.

In doing so, this will build a container that has VNC capabilities where you can utilize a desktop environment to setup the GUI version of qBittorrent with your I2P settings, and then just use the web-ui from there on.

Why?

I am a qBittorrent user and wanted to start downloading and cross-seeding torrents with I2P, so I built this image as a drop in replacement of my linuxserver/qbittorrent docker container and it just works.

Why don't you post the docker image?

I am not sure how yet, and I also left it as a Dockerfile so that you can build this on ARM or x86-64 depending on your needs

Note

This image can be quite heavy and take a long time to build, but until v4.6.x is out of beta, this will do.

 

i2pd

https://github.com/PurpleI2P/i2pd/releases/tag/2.49.0

Changelog

  1. Handle SOCK5 authorization with empty user/password and send correct version in response
  2. Improve NTCP2 transport session logging
  3. Allow 0 hops in explicitPeers
  4. Don't allow incoming transport sessions from routers with incorrect timestamp
  5. Fixed sending keepalive for sessions with introducers
  6. Always select router with ipv4 for tunnel endpoint
  7. Fixed crash if deleted BOB destination was shared between few BOB sessions
  8. Memory pool for router profiles
  9. Removed AVX code
  10. Exclude SSU1 introducers from SSU2 addresses
  11. Don't create paired inbound tunnel if length is different
  12. Fixed padding length for SSU2 path response
  13. Don't publish introducers with zero tag
  14. Consider all addresses non-published for U and H routers even if they have host/port
  15. Don't pick completely unreachable routers for tunnels
  16. Separate network and testing status

i2pd-android

https://github.com/PurpleI2P/i2pd-android/releases/tag/2.49.0

view more: next ›