Yesterday I changed my ISP to one that allows port forwarding. Today the port forwarding has been enabled by the company and I set it up on the router.

After enabling it, my download and upload speed dropped from peaks of 50 MiB/s and valleys of 4-6 MiB/s to a very stable 2 MiB/s. Nothing else has changed in my qBittorrent configuration. If I close the ports again, the speed goes back to normal. I checked if the ports were open on various websites and all of them show that they are forwarded.

I was looking forward to be able to port forward and connect with every possible peer for years, and today has been a big disappointment in that regard!

Has anyone else seen something like this and if so, can you point me to the right direction to fix the problem?

Edit: Thanks everyone for your time and your help! Still working on it, but it’s heartwarming to be on the receiving end of the goodwill of this community.

Sometimes I love the internet!

  • Flatfire@lemmy.ca
    link
    fedilink
    English
    arrow-up
    8
    ·
    2 days ago

    If I understand correctly, it sounds like you moved from an ISP that uses CGNAT to one that does not. Does your ISP provide a modem? If so, are you relying on the software features of that modem, or do you have a router inbetween?

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

      You nailed the first part. As for the second one, you’ll have to be patient with me, because I’m not tech savvy and english is not my first language. Mi ISP provides a router, and through the router settings, you can port forward. Is that what you are asking?

      • Flatfire@lemmy.ca
        link
        fedilink
        English
        arrow-up
        3
        ·
        21 hours ago

        Yes, you got it.

        It’s possible that however your ISP provided router is designed, it’s got some hidden port forward configuration. If that router has an option typically referred to as “bridge mode”, you could bypass its routing features altogether and use your own router instead.

        ISPs often have clauses about using their residential internet for hosting servers or exposed services, and it’s possible your has taken a different approach to mitigating traffic from those sources.

        If you can, I’d recommend using your own router rather than what the ISP provides.

        • dividedby0@lemmy.dbzer0.comOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          20 hours ago

          I can’t buy a router at the moment, things are not easy, and with the holidays coming, it’s even harder. I had a look to see how much would I be in for and it’s very much outside my budget.

          Thank you nonetheless, maybe it’s something I will be able to afford at some point in the future.

    • dividedby0@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      2 days ago

      I’m completely sure! Yesterday it was running ok all day. Today, I port forwarded and left home for a couple hours, after coming home I checked the computer and saw the low speed. The first thing I did was think about what had changed and I closed the ports. The speed went up immediately. I tested it a couple more times with different ports and the same thing happened.

      • Kairos@lemmy.today
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 days ago

        What the fuck?

        Maybe they meter incoming speed? Try running a speedtest using a web server or iperf3 or something.

        • _cryptagion [he/him]@anarchist.nexus
          link
          fedilink
          English
          arrow-up
          9
          ·
          2 days ago

          more likely they just know it’s bittorrent traffic. that’s not hard for an ISP to sniff out, if you aren’t using a VPN. it’s not uncommon for ISPs to throttle bittorrent traffic automatically.

          • cassandrafatigue@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 day ago

            And the reasons they do it run the gamut from ‘mildly shitty’ to ‘profoundly shitty’.

            You might consider routing torrent traffic through multiple old garbage laptops on your network, then putting your regular traffic through on an ‘unforwarded’ looking computer at full speed? Might work.

            • _cryptagion [he/him]@anarchist.nexus
              link
              fedilink
              English
              arrow-up
              4
              ·
              1 day ago

              Understandable, but without one you’re totally at the mercy of your ISP. If it turns out they are automatically throttling BitTorrent traffic, there’s nothing you can do without a VPN because on a fundamental level they control your access to the internet. The unfortunate thing about BitTorrent is that it’s not sneaky at all. Your ISP will be able to tell you’re doing it if you aren’t encrypting that traffic.

              • dividedby0@lemmy.dbzer0.comOP
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 day ago

                Yeah, I think I’m just delaying the inevitable. I’ll call the ISP in a couple hours and maybe it will be time to look for a christmas deal with airvpn.

        • dividedby0@lemmy.dbzer0.comOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          The speed test looks fine. Maybe they meter it as you say. Guess I’ll have to contact them so they can explain wtf is happening to my connection.

          • Kairos@lemmy.today
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 day ago

            How did you do the speed test? You need to have an open port on your side and another IP address outside your network.

              • Kairos@lemmy.today
                link
                fedilink
                English
                arrow-up
                2
                ·
                18 hours ago

                I am a Unix person I just get it from my distro:s package repository. I don’t know if that URL is the correct address.

                The steps are (simplified):

                1. Get a server on your home IP (your seedbox will do) and a computer on the outside (you may prefer try a VPN) to stress test your connection.
                2. Open a port to the machine at your house. Run iperf3 server on that port on that machine.
                3. Connect to that machine from the one outside your home via a command which runs a speed test.
                4. See results.

                This specifically speedtests incoming connections to your IP address. Regular speedtests like fast.com, etc. Test outgoing. With the way TCP/IP works, your ISP can easily differentiate the two.

                • dividedby0@lemmy.dbzer0.comOP
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  3 hours ago

                  Man, if this is the simplified version, I’m totally fucked. I understand every word, but the order in which they are stringed together confuses me.

                  I’m waiting for a call of my ISP’s IT service to see what’s what. If they can’t (or won’t) fix my issue, I’ll bite the bullet and I’m gonna buy a subscription to a VPN.

                  Thank you for the detailed explanation!

    • dividedby0@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      Other traffic is fine. That’s what was screwing with me, but after reading some people say they might be fucking with my connection due to seeing it is a bittorrent connection, everything makes more sense.

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

    Just to be sure, did you already test that the port is actually open and forwarded? e.g. with your torrent client running browse to a port test website like https://canyouseeme.org/ , https://www.yougetsignal.com/tools/open-ports/ , etc. put in your torrent client’s incoming port and check if the website can “see” your open port at your torrent client.

    And the ISP (or router) itself isn’t doing anything weird to block torrents, right? In your torrent client if you click any working public torrent, click on the Trackers tab, you should see DHT as working along with whatever open trackers are on the public torrent. In other words you won’t see anything like “waiting” something (I forget the exact message you’ll see when DHT is being blocked but it’ll definitely not be working).

    EDIT: Also if it’s a new ISP with new router it might have firewall rules set up that are slowing things down, something to check.

    • dividedby0@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      Yes, I checked if they were open, and the three sites say they are. I used the ones you sent me, and same results!

      Some pwople say that they might be throttling my connection, and I think it is what makes more sense. I’ll have a call with them to see what is happening.

      Thanks for pointing out the router firewall, didn’t think about it, but iy is not that either.