More and more services are enabling IPv6.
More and more ISP's are supporting it to their end users.
And you should to!

Pro: Much Larger Address Space
Pro: Virtually Unlimited Host Addresses per Prefix
Pro: Stateless Autoconfig
Draw: No More IP Scanning


Please check the sources for more information about IPv6

Sources:
packetlife.net
Wikipedia.org

Long story short. You don't need to portforward in IPv6
Why? Cause your ISP will give you a /64 prefix 2 to the power of 64 IPv6 adresses.

Code:

18 446 744 073 709 551 616 adresses


This is my IPv6 subnet.
Spoiler (Click to View)


So you don't really need to port-forward. But there still is a Firewall that you'll need to configure.
You'll most likely get a screen like this or with similar options.

Spoiler (Click to View)


naam firewall rule: GIVE_A_NAME_TO_RULE
Protocol: chose between TCP, TCP&UDP, ANY or ICMPv6 (pings)
Source: could be a single host or ANY
Port of range: -->

accessing a service:
Just type the port of your service
Ex. You want to access ssh on server X give in port 22


Offering a service
just type 1024:65535
Ex. You want to offer SSH to another client on the interwebs give in 1024:65535
Sounds weird right?
It isn't. When you make a connection to another service you assign a dynamic port to your computer for establishing that connection.


Sources:
https://support.microsoft.com/en-us/kb/929851
https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
https://en.wikipedia.org/wiki/Port_(comp...etworking)

Destination: Host
IP-adres: GIVE_IN_YOUR_IPv6
port of range:

accessing a service:
1024:65535
offering a service:
Ex. SSH --> 22

Mode:
Accept
open up the firewall

Drop
Drop everything close the firewall nothing will get through send no response

Block
Block the packet but your nice and send a reply to the client that the packet is being blocked

Sources:
Drop vs Reject