A lot many individuals run TOR exit nodes, but I never hear about people running their own I2P outproxies. Is it really hard to host, or is there some other reason? I thought that if you could run a TOR exit node I’d think you’d be just fine running an I2P outproxy.

Running more outproxies will help in bridging torrents from the clearnet to I2P, which would be a very good move considering the crackdowns on torrents right now. Companies even want to involve civilians into their lawsuits in Sweden now, making the need for privacy/anonymity even more important when torrenting, which I2P provides.

  • sploodged@lemmy.dbzer0.com
    0·
    2 months ago

    stormycloud is the biggest, there’s also acetone and purokishi that are both very reliable. there’s a couple others that aren’t as stable right now. i2p’s about inter-network services that often work without any need of the clearnet, tor is a better option if you’re looking to do clearnet things.

    torrents don’t get bridged through the (mainly 3!) outproxies in i2p. they’re bridged by random people cross-seeding torrents through clients like qbittorrent or bigly bt which work in both i2p and clearnet. Or, you can download a torrent from clearnet normally and change the trackers to i2p only trackers, then add to i2psnark. In both cases using biglybt/qbittorrent you should be able to connect to peers from i2p and clearnet through the people that do this, functioning as your own outproxy in a way.

    Anyone can easily bring over clearnet torrents into i2p, and they are more than welcome to do so!

    So i’m not disagreeing with you about i2p needing more outproxies, more is better, but tor does this already (and arguably does it better since there’s so many exit nodes) so i don’t think the demand is as big. You’re right that it’s pretty similar running an i2p proxy. As far as i know it’s a very similar process running tor exit nodes vs i2p outproxy, i think acetone is also a tor exit node (i might be wrong on that), purokishi routes some things through tor, and stormycloud until somewhat recently mainly focused on running a fleet of tor exit nodes.

    The nature of i2p means that to get faster speeds these providers may be running many i2p routers to provide lots of tunnels and load balance them, so i think that aspect is more technically challenging but i’ve never done it at scale myself. I think you’d need a handful of well resourced/connected i2p routers to offer a consistently good outproxy service.

    • ReversalHatchery@beehaw.orgEnglish
      1·
      2 months ago

      i remember reading that tor maintainers don’t like it when people use the Tor network for torrenting, because it harms the network from a performance perspective

        • ReversalHatchery@beehaw.orgEnglish
          3·
          2 months ago

          yeah, and more generally, Tor is optimized for light services both in-network and through outproxies (because there are many of those), and I2P is more optimized for large transfers and many connections in-network, and very unsuitable for internet access because there’s only a few overwhelmed outproxies, among which load is not even attempted to be distributed by the default I2P router configuration.

          the reason for why I2P is more suitable for torrenting is unclear to me, though, other than the maintainers telling that. possibly because almost everyone who wants to use the network will participate actively in routing traffic, and so there is relatively a lot more routers than on Tor

          • sploodged@lemmy.dbzer0.com
            2·
            2 months ago

            Yeah, accessing the outernet was sort of an afterthought with i2p, although the proxies are handling well now…things got way better after stormy cloud came on the scene imo. you can stream clearnet videos through the 3 i mentioned. It could be better if there was outproxy switching built in like tor, i think. It was bad though before stormy cloud and often unusable, the available outproxies were very much overwhelmed. sometimes they worked but it was hit or miss.

            that’s the right line of thinking. vast majority of tor users don’t contribute to the network which is held together by a comparatively small number of volunteers. by default if you’re running i2p you’re contributing (except with specific configurations). With tor, more users, same number of nodes means less bandwidth for everyone. With i2p more users means both sides go up, more nodes, more bandwidth, on average more bandwidth for everyone. Torrenting burns bandwidth but on average more users grows network capacity.

            • ReversalHatchery@beehaw.orgEnglish
              3·
              2 months ago

              the available outproxies were very much overwhelmed

              honestly that’s still my experience. it’s not rare that websites like a DDG results page does not even load, I think from time to time I even have unable to connect errors, even though as I have stormycloud as my outproxy. probably something on my end, though, it seems then

              • sploodged@lemmy.dbzer0.com
                2·
                2 months ago

                I haven’t used stormycloud much but i haven’t heard there being issues with them. I’ve preferred using outproxy.acetone.i2p and purokishi.i2p since i’ve found them consistently to be faster. Stormycloud is the default in vanilla i2p so they end up getting the brunt of i2p’s outproxy traffic, it’s possible they could get overloaded. They have a very good setup, but they’re one entity.

                Especially right now after mental outlaws video, more routers could be coming online and giving stormycloud a workout, maybe getting overwhelmed. I would try switching to either of those and setting inbound/outbound tunnel count to 16. hope that helps.

                • ReversalHatchery@beehaw.orgEnglish
                  3·
                  2 months ago

                  I’ll try this, thanks. but to fill in some missing context from my part, this is what I have been experiencing for the little more than a year I’m running an I2P router.

    • Findmysec@infosec.pubOPEnglish
      1·
      2 months ago

      Thank you, where can I read a guide on this?

      Does Qbittorent support I2P natively? If so, I can probably run it on my seedbox. Never tried it before

      • sploodged@lemmy.dbzer0.com
        2·
        2 months ago

        You can do multihoming, might be the easiest thing to do for a service: https://geti2p.net/spec/proposals/140-invisible-multihoming

        Multihoming is a pretty simple way of load balancing and i think the way it works is the first router to respond is the one that’s used. So ideally the one used by any given client should be the most responsive i2p router.

        It’s also used to place i2p routers hosting a service in multiple places so it makes correlation attacks (ex downtime at exact time of a known electric outage in an area) more difficult.

        Backend setup for your service

        If we have a service like an http proxy service or a website available on port 6000, and 2 i2p routers, they’d both need access to that port. An outproxy may do this with port forwarding from a clean outernet connection(s) going through their proxy setup ex privoxy/haproxy/tinyproxy dns. They’re less worried about correlation attacks so the routers may be all or mostly in one area using port forwarding over lan or VM’s. A website that’s concerned about correlation attacks may have separate instances of the website running on each router in different areas, with the website’s backend syncing with the other routers in the background through other methods such as an encrypted lease-set.

        Router setup

        Each router needs the same exact key for the actual .i2p address. The easy way to do this is in the java router (i2p+ is good for this, install guide/official site go to service tunnels > make new server http tunnel, enter the port 6000, give it a name like “Outproxy”, private key file a name like “outproxy.dat” and make sure optimize for Multihoming is on.

        Other recommended additions in your tunnel config

        • Automatically start tunnel: on
        • 16 tunnels in/out (maximum): 3 hops for good anonymity, outproxies not concerned with their own anonymity could reduce this for more performance.
        • Reduce tunnels to conserve resources: idle period 15-20 minutes, reduced count: low number like 2-3. This usually works well since the tunnels can be built back in an order of ms’s on a good i2p router and not wasting resources keeping them open. It could introduce a slight delay though. High traffic situations might make sense to leave that off.

        Then save and start, key file is generated.

        Copy key file and a tunnel config file

        Locations for .config file and key (.dat):

        /i2p/.i2p/outproxy.dat

        /i2p/.i2p/i2ptunnel.config.d/XX-outproxy-i2ptunnel.config

        Then copy the key and config files to the other i2p routers in the same locations. Shouldn’t need to go through setup with the config file present. Most important is it has the same key file, so they’ll all use the same address.