@Kevin4fm To be fair though, port forwarding on IPv4 is a bit more complex than the issue you usually face on IPv6. On IPv4, you usually have to also establish a static IP address on your LAN subnet so that your port forwarding rules never have to be played with once they're set. This in and of itself can overwhelm a lot of people.
With IPv6 on the other hand, you don't need to do that part. You merely need to tell your firewall to allow inbound traffic on a specific port. Realistically, your IPv6 address can change every time that you turn on your device and connect it to the internet (in cases where the configuration is done with DHCPv6), or if you use the more "traditional" or "standard" method using SLAAC, your address can change every time you reboot your modem/router.
Regardless of what way your network is setup (which largely depends on your provider), you don't need to track down IP addresses, set a static assignment, or any other such thing like that. You only need to tell your router to accept connections from the internet on port X. So it's actually easier because effectively your LAN IP address is also your public WAN (internet) IP address with IPv6, so if your address changes, so too does how you show up to the internet. The same does not hold true with IPv4.
It may also be worth noting that when enabling the port in your firewall, you enable the policy to allow the port your torrent client uses in the FORWARD table and that it is just a blanket policy of DESTINATION PORT. So for example, in the case of my one server that uses port 22971, you need add only two simple rules to the FORWARD table.
Destination Port = TCP 22791, ACCEPT
Destination Port = UDP 22791, ACCEPT
There's no need to have to even specify what device it's going to, no need to know the IP address it's got to go to, or even know the particular /64 block on your /56 block that the device sits on... You ONLY need to know the port number and that it's the DESTINATION port you want to enable.
