• tVxUHF@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    27
    ·
    2 days ago

    We just need to add I2P directly into the client in a way that’s transparent to the user and all the problems are solved.

    • ArcaneSlime@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 days ago

      If I could have an all in one browser like Tor or have jackett do postman too I’d be set, except for the whole “works better the longer you leave it running” thing is only true until my battery dies.

      • ReversalHatchery@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        2 hours ago

        I2P has a mechanism where if you can’t open a port, another I2P router can help with NAT hole punching so that you can establish a connection.

        In practice this means I2P users can be equally well connected regardless of being able to open a port.

        But, unfortunately I2P is very slow. But maybe it’s just because there’s few people running routers, on slow networks?
        In any case, it would be beneficial to have it easily accessible to everyone, so that copyright holders can go pound sand.

        Edit: When you couldn’t open ports for I2P, the I2P router will have the “Network: Firewalled” status. This is the description of this status on the router dashboard:

        Firewalled: Your UDP port appears to be firewalled. As the firewall detection methods are not 100% reliable, this may occasionally be displayed in error. However, if it appears consistently, you should check whether both your external and internal firewalls are open for your port. I2P will work fine when firewalled, there is no reason for concern. When firewalled, the router uses “introducers” to relay inbound connections. However, you will get more participating traffic and help the network if you open your firewall. If you think you have already done so, remember that you may have both a hardware and a software firewall, or be behind an additional, institutional firewall you cannot control. Also, some routers cannot correctly forward both TCP and UDP on a single port, or may have other limitations or bugs that prevent them from passing traffic through to I2P.

  • BlackLaZoR@fedia.io
    link
    fedilink
    arrow-up
    3
    ·
    2 days ago

    I don’t see that where I live - some ISPs offer port forwarding, some don’t. Some just give you IPv6 with ports unlocked manually in router config

    • HouseWolf@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      Can someone correct me here.

      If I have i2P enabled on my qBittorent client and I start seeding a torrent downloaded from a non-i2P connection.

      Does my seed of it allow others to download that torrent through i2P?

      • kylian0087@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        23 hours ago

        No, you need to cross seed. A torrent client that allows for this is biglybt. Or you need to manually re upload it on i2p

      • kylian0087@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        9
        ·
        2 days ago

        I2P is IMO the future for torrenting. The only downside it still has is that their is less content. But that will be solved when more and more people migrate to I2P

          • kylian0087@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            4
            ·
            edit-2
            23 hours ago

            I2p is fairly easy to use. The normal I2P client even comes with a torrent client bundled. Also URLs for postman aka best torrent site are included.

        • FundMECFS@lemmy.blahaj.zoneOP
          link
          fedilink
          English
          arrow-up
          6
          ·
          2 days ago

          Does that mean you would route your BitTorrent traffic through I2P?

          Doesn’t that severely limit peer discovery to only other I2P users, since AFAIK I2P has no exit nodes / clearweb access?

          • kylian0087@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            7
            ·
            2 days ago

            Yes that is true. Their are a few bittorrent clients that can cross seed however. But it mainly stays inside i2P which Is good and makes it fully anonymous

    • Hozerkiller@lemmy.ca
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      1 day ago

      Does port forwarding really matter if you have a Holborn 9100?

      Does port forwarding really matter if you have Hannah Montana Linux?

      Does port forwarding really matter if you have a Dawson’s Creek trapper keeper?

    • BlackLaZoR@fedia.io
      link
      fedilink
      arrow-up
      2
      ·
      19 hours ago

      In principle yes it does - in case of TCP based protocols, without forwarded ports incoming connections aren’t possible. In the context of the main Torrent protocol this means you can only connect to peers that have ports forwarded. This is largely solved by uTP protocol that uses UDP hole punching method to circumvent this.

      So the sort answer is no this doesn’t matter unless you’re using very feature poor torrent client.

  • Xanza@lemm.ee
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    1
    ·
    2 days ago

    Bulgaria, Hong Kong, Luxembourg, Malaysia, Netherlands, Russia, Cyprus, Moldova, Romania, Ukraine, Singapore, and Sweden. They all spit in the eye of DMCA.

    VPS in any of these countries, or just find a provider that doesn’t care about torrenting. If you go the VPS option, run your own VPN and just look for a VPS that allows considerable traffic. A quick example, Ultahost (Netherlands) offers a VPS with unlimited bandwidth for $7/mo if you pay for 3 years in advance. Like sure, now you’re paying to torrent, but I would rather pay $7/mo to protect myself with a VPN that I control vs worrying about port forwarding and getting DMCA’s in the mail. 🤷‍♂️ I guess it depends on how much skin you want in the game.

    • ntn888@lemmy.ml
      link
      fedilink
      English
      arrow-up
      13
      ·
      2 days ago

      That’s exactly what I did. Better yet I routed it though a wireguard tunnel! I documented the process here.

  • ISOmorph@feddit.org
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    6
    ·
    2 days ago

    You have to separate pirating and torrenting. I’m pirating stuff non stop each day. I’m torrenting maybe once a month, if that. It’s just not the go to thing for a lot of users, so issues around VPNs and torrenting probably aren’t that pressing to warrant any kind of reaction.

  • Wrrzag@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    2 days ago

    I’ve never had a problem with it in Spain. What is different where you live? CGNAT?

  • Illecors@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    62
    ·
    3 days ago

    IPv6. My stupid ISP actually shipped their router with all inbound ipv6 blocked with no way to unblock it, so I set up opnsense. Works like a charm!

      • Illecors@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        6
        ·
        2 days ago

        It’s not v6 itself, it’s rather lack of layers of nat that prevent forwarding a v4 for most folks.

        • clove@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          2 days ago

          Hmm, so no firewall in the router blocking ports, instead blocking happens on the actual client?

          • Illecors@lemmy.cafe
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            2 days ago

            Normally firewall is on the router. Sensitive environments usually run one on the client as well.

          • azuth@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            6
            ·
            edit-2
            2 days ago

            Port forwarding is necessary due to NAT not firewalls.

            It’s not that your router blocks new incoming connections at port X, it’s that it does not know which local client it’s meant for, since it’s addressed to the public IP that is held by your router.

            With IP6 it’s lan client also gets assigned a public IP6 address (as there are plenty) and so the router receives a connection addressed to a Lan client and knows where to route it.

            • JustEnoughDucks@feddit.nl
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 day ago

              But how does this change using VPNs with torrenting? Especially because it seems like the vast majority don’t support ipv6 as well as openvpn often leaking ipv6 IPs.

              • azuth@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                1
                ·
                24 hours ago

                Not sure since I don’t use a VPN. If they assigned a unique public IP per user they could just forward every incoming connection to the user’s PC.

                If they don’t they need to setup some port forwarding rules.

                If openVPN leaks IPs that’s surely a bug, if it’s specific to v6 you can’t use openVPN and IPv6 till the bug is fixed

      • Illecors@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        13
        ·
        2 days ago

        Fair enough, I guess. Still, I was dumbstruck by lack of ability to open up a port.

          • Illecors@lemmy.cafe
            link
            fedilink
            English
            arrow-up
            1
            ·
            18 hours ago

            Glad to hear! Not that you’d want to send email from a residential IP anyway - if not for your ISP, every email service wouls bounce it anyway.

    • elidoz@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      opnsense sounds like what I was looking for (if I understand correctly)

      I had no idea there was a way to go around the ipv6 restrictions

      • Illecors@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        39
        arrow-down
        1
        ·
        2 days ago

        It doesn’t fix it, per se, rather removes the need for layers of hacks such as nat and cg-nat. Every device gets a globally routable IP - no need to forward anything, just open the port you want.

        • osaerisxero@kbin.melroy.org
          link
          fedilink
          arrow-up
          23
          ·
          2 days ago

          This doesn’t solve for VPNs no longer offering it though, unless the VPN services started offering pure v6 via tunnel at some point while I wasn’t looking. I know I’ve never seen a v6 pier in the last few years since I started sailing again.

          • FundMECFS@lemmy.blahaj.zoneOP
            link
            fedilink
            English
            arrow-up
            9
            arrow-down
            1
            ·
            2 days ago

            Yeah thats been my issue. It works fine on my unprotected IP. But I don’t have the cash to spend on expensive vpns and the cheap options seem to universally be shlt for port forwarding, ie. seeding

      • gamermanh@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        7
        ·
        2 days ago

        Localhost NAS with large storage, Rclone to seedbox, synch, remove old content from seedbox

        Source: I have 8TB rn and about to add more, this is how I use my seedbox and store shit

        • ExcessShiv@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          17
          arrow-down
          1
          ·
          edit-2
          2 days ago

          Only seeding new stuff that everyone else is also seeding is not good for torrenting in general, it will kill a lot of content that’s more than a few years old and/or not completely mainstream.

          • N0x0n@lemmy.ml
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 days ago

            Yeah most seedboxers are just the new leechers of this generation… Keeping up their ratio about an unreasonable amount where they can leech everything they want without the need to give back…

            They just stay for the necessary amount of time specified by their private tracker and leave the queue afterwards.

            IMO seedboxes should have another rule associated to them… Straight to 1 month seeding time or get a hit&run warning !

            • CmdrShepard42@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 day ago

              I wouldn’t call them leechers since they are seeding back to build said ratio. I think it’d be more accurate to call them a single component of a larger ‘structure’ including people like myself who permaseed from home on a slower connection. If it were all people like me, we’d all be waiting days for new releases to fully download and if it were all seedboxes, we would have zero seeders for anything older than a month or two. Many private trackers incentivize long-term seeding to help control this imbalance, and I think it works well in my experience.