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