i don't know what you did as far as containerizing/vm but i'd expect it's got something to do with that assuming there isn't something upstream blocking it. i2p routers will work best opening the TCP/UDP port so it will allow incoming connections

I better isolated the i2pd machine on my network just in case something goes wrong with it and I don't notice right away. While doing so, I noticed roughly half the connections to the i2p relay port are being blocked by my firewall. Strangely, the firewall is set to allow all on that port. It says it's blocking based on ingress firewall's IP filtering rules.

What rules? I didn't give it any rules. If it's unsolicited, it's blocked, but the i2p relay is requesting those connections so the firewall shouldn't be blocking them, right?

i'm not sure about SAM since this is qbit, but with I2CP running either biglybt or snark can be glitchy on separate machines especially with i2pd, java seems to handle random disconnects better where i2pd might not recover, possibly due to latency. As far as i know I2CP is intended to be used on the same machine. you can do this but it runs much better with java routers from what i've found where i think i2pd is best if you keep it on the same machine.

possibly things to check - trackers are working since no dht, in a good swarm, tunnel quantity/number of hops. like are peers available or is it a throughput issue

I got it working. qbittorrent in a rootless podman container on a media server and the relay elsewhere on the network. Unfortunately, the performance is quite poor. I'm aware this is going to be slower than clearnet torrenting, but I'm only getting around 5KiB/s. That seems off to me.

It has been in development for 9 months. If you decide to test it out, please let me know if you run into any issues.

seems cool. not sure on safety though since it's new but i'd test it out

I used to play around with different bittorrent clients for weeks when I first found out about I2P. I tried i2psnark, qbittorrent, XD, BiglyBT but now I have settled using qBittorrent-nox with SAM protocol to i2pd node. Both are on same computer, because I read from IRC that its not good to have them on seperate computers. I mean your i2pd node and your qbittorrent client.

I have disabled DHT, PEX and other stuff in qBittorrent and I only download torrents from the Postman Tracker.

Awesome to see the developer here. How long did it took to "rewrite" the code using Rust? I am so new to these things that I have no clue where to even begin. Lol. I will definitely spin up a test server during summer time and contribute as much as possible for the project. Keep up the good work!

I agree with what zzz said. The project is in the early phase so it's still missing a lot of features and "institutional knowledge" that java and i2pd have. I hope that by EoY most of the missing features have been implemented and the most glaring bugs have been fixed.

All help with testing and development is deeply appreciated.

Thanks for the info! The one-person project popping out of nowhere makes me a bit wary, so I’ll wait for SSU2 to work properly before diving in. I do host an eepsite, but I’ll hold off using Emissary for that until it’s more polished. Wish I had a spare computer to test it out safely!

Rust Tor implementation Arti 1.0.0(Onion, I2P)
Tor Project describes about benefit of Rust language. Tor Project needed a year to release stable Arti.

re: safe to use? depends on your risk tolerance and threat model.

The code quality and completeness is very high. Rust is a "safe" language that eliminates a lot of possible issues. But this is a one-person project that just appeared out of nowhere, it will need a lot of testing and review to gain confidence. There's a lot of subtleties in i2p protocols that, if implementers are not careful, may lead to deanon, crashes, etc.

It does have UPnP/NATPMP to open firewall ports. if you're not on a direct IP and it can't open your firewall ports, it's not going to work well, because its SSU2 implementation isn't done, so it can't do peer test and relay.

For now, I wouldn't use it for eepsite hosting if you're concerned about possible deanon. Safe for running with qbittorrent or i2psnark-standalone? Depends on your threat model.

It also may not "look" exactly like other routers, so it may be apparent that there's an emissary running on your IP.

For brave people, please start testing and opening github issues for any problems you find.

this is fucking hot as hell mad respect i'd love to experiment

Interesting. How safe can it be to use? Also can it increase speeds of I2P network? I am really new to i2p so enlighten me :p

I have noticed that with release 2.8.0, SAM applications are negatively impacted. I have a SAMv3 application that worked fine on release 2.7.0, it no longer works on 2.8.0.

I'm trying to find out where to file bug reports:

http://i2pforum.i2p/viewtopic.php?t=1322&sid=c7fcb2c2c880bc8199e69acba2ab5215

I'm investigating the issue. Details can be found at:

http://sovereign.i2p/sam-issue.html

it's growing in power

Very nice collection.

zzz posted too
Top 100 Jump Requests for 2023, Top 100 Jump Requests for 2024

will someone give this man fakeboobs already

if you're talking about running a reseed server through a vpn i think you could do this but i wouldn't. pretty sure you need an outernet domain name with ssl cert. if the vpn has a dedicated ip this could probably be setup, or look into doing reverse proxy through one of those dynamic dns things. never tried that so no idea if or how it'd work, but probably be easier running off a vps somewhere sans vpn. i know everyone loves cloudflare but that could also be an option https://homepage.np-tokumei.net/post/notes-i2p-reseed-over-cloudflare/

I2P 2.7.0 has also been released.

Access to information from the console and applications has been improved. Issues have been fixed in I2PSnark and SusiMail search. The netDB search embedded into the router console now operates in a more intuitive and useful way. Minor improvements have been made to diagnostic displays in advanced mode. [...]

If it works for you, great. There are some fingerprints based on keys. For your own protection, I decided not to drag you into my crap.

Shouldn't I2P (or TOR) protect from being pinpointed, assuming you aren't sharing personal information?

I do use retroshare but I do change ID's often. Sometimes it is a just one use only. It is very useful and recommended software but you can't be a sitting duck.

Differences in the sha hashes are a result of infrequent updates to the i2pupdate.zip being served from http://skank.i2p/i2pupdate.zip ... occasionally a new update will appear, either to add new features (in the recent case, more complete translations) or fix bugs. To identify exactly which revision you're running, you can view the hashes on 127.0.0.1:7657/jars.

In addition, for some users a new release will revert them to vanilla I2P, so updating the I2P+ zip available on skank.i2p will sometimes fix this if it's date stamped after the update to vanilla.

As for "corrupt" downloads, if you're in the middle of an update when a new version is uploaded, your download will become corrupted, in which case re-downloading the update should fix. It shouldn't happen for release updates very often, slightly more chance when updating from the /dev/ path as that's sometimes updated several times a day.