• 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?

    • azuth@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      1 day 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
        ·
        24 hours 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
          ·
          13 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
      1
      arrow-down
      1
      ·
      2 days ago

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