I used i2p from InviZible Pro (F-Droid).

I was trying to connect my Monero wallet to a Monero RPC Damon that somebody I know runs and while it did connect the absolute best speed I could ever achieve through it was 45KiB/s. I changed no settings at all and just used the defaults. Turned it on and had 33 client tunnels.

Tor usually gets me ~400KiB/s to the hs, but i thought i2p would be faster.

Edit: it used 2 hops as default and i left it that way.

  • 12510198
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 day ago

    No worries, hopefully increasing the tunnel quantity will get you acceptable speeds, I could be missing something, but thats all I can think of besides allowing inbound traffic.

    Something I forgot to mention, there is the Java I2P router, its availiable in the default f-droid repo, I havent tested it out on Android, but it has a fancy gui on desktop where everything can be configured, it some blocklists of tor exit nodes and stuff, I think that helps performance, I’m not totally sure tho, I dont use the Java versions, they have too many buttons and switches, and its kinda overwhelming for me.

    • shortwavesurfer@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 day ago

      I didn’t see anything about tunnel quantity, specifically for the socks proxy. I did see something about it for HTTP, but I’m not using HTTP.

      [httpproxy]
      enabled = true
      address = 127.0.0.1
      port = 4444
      inbound.length = 1
      inbound.quantity = 5
      outbound.length = 1
      outbound.quantity = 5
      signaturetype=7
      i2cp.leaseSetType=3
      i2cp.leaseSetEncType=0,4
      keys = proxy-keys.dat
      addresshelper = true
      #outproxy = http://false.i2p
      ## httpproxy section also accepts I2CP parameters, like "inbound.length" etc.
      
      [socksproxy]
      enabled = true
      address = 127.0.0.1
      port = 4447
      keys = socks-proxy-keys.dat
      #outproxy.enabled = false
      #outproxy = 127.0.0.1
      #outproxyport = 9050
      ##socksproxy section also accepts I2CP parameters, like inbound.length etc
      

      However, since that socks proxy section says that it takes I2CP commands, I wonder if I could just paste the info from the HTTP part above.

      • 12510198
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Yes, you can take the quantity and length options from the http proxy and just paste it into the socks proxy section, I think tunnel quantity can go up to 16, I recommend 8 for high bandwidth stuff like torrenting, but it will use more CPU and battery, but lowering length from the default of 3 to 1 should help a lot.

        • shortwavesurfer@lemmy.zipOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          I got no help from that whatsoever. It’s still extremely slow even after letting my clients sit there and integrate for over 30 minutes and seeing over a thousand routers.

          • 12510198
            link
            fedilink
            English
            arrow-up
            1
            ·
            22 hours ago

            Idk then, I’ve easily gotten speeds of upto 1.2 MiB/s while torrenting, uploading and downloading, I just downloaded a book from a webserver with wget to test my speed through the HTTP proxy, and I got about 150-300 KB/s throughout the whole transfer, I’m using the default settings of 3 hops, and my router isnt firewalled, no clue what the servers settings are.

            • shortwavesurfer@lemmy.zipOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              21 hours ago

              I’m wondering if it’s because I am firewalled off, because on IPv4, I am behind CGNAT, and on IPv6, I have not done any port forwarding, and do not use UPnP.