Technical question regarding ipv6

While correctly set up port forwarding is essential for ED when using ipv4, how does this translate to ipv6?
Is port forwarding moot when using ipv6 and will using ipv6 have any disadvantages compared to
ipv4 + port forwarding when it comes to ED?
 
TCP and UDP port numbers remain the same independant of which IP version you use. If your ISP gives you IPv6 on the outside and a unique real world IP per device on the inside, then port forwarding is a mute point... but if you're router is still performing NAT (even IPv6 on inside and outside) then port forwarding is still needed, you'd just need the rules applying to your inside static IPv6 address
 
Pretty much what Gavin said.
With IPV4 settings you need port forwarding as your home network is most likely RFC1918 IP addressed, and your router holds your one assigned, public, IPv4 address performing NAT.
If your provider hands out IPv6 then I'd assume (I assume as I don't know a provider that hands out IPv6 to private customers other than some mobile carriers) you get more than one IPv6 address, and won't need NAT on your edge device. No NAT means no Port Forwarding, as well, there's nothing to forward with out NAT. If you get only one IPv6 address you'll still need NAT as per Gavin's suggestion.

Makes sense?
 
To my understanding this is currently moot for E:⁠D since the game's peer2peer networking will only use IPv4.

If your provider is giving you a single IPv6 address instead of a prefix, change providers. They are violating every single recommendation and standard about the protocol and provisioning.
 
Typically you would get a range of IPv6 address. My ISP gives me a /48. I have a friend who uses Comcast in the US and they give him a /128. Yes, one address!

You can port forward from IPv6. You probably don't want to but you can. It would be an option if you have that one address.

More likely is that you can do prefix rewriting so all hosts behind the router have private addresses and the router has a public range. Any traffic for <public_prefix>:<address> gets rewritten to <internal_prefix>:<address>. The main justfication for doing that is that you might change ISPs and get a new public range, in which case it would be a pain to re-address all the devices on the network. Which it would. Unless you are using stateless configuration, of course.

But no, the game doesn't support it.
 
Typically you would get a range of IPv6 address. My ISP gives me a /48. I have a friend who uses Comcast in the US and they give him a /128. Yes, one address!

You can port forward from IPv6. You probably don't want to but you can. It would be an option if you have that one address.

More likely is that you can do prefix rewriting so all hosts behind the router have private addresses and the router has a public range. Any traffic for <public_prefix>:<address> gets rewritten to <internal_prefix>:<address>. The main justfication for doing that is that you might change ISPs and get a new public range, in which case it would be a pain to re-address all the devices on the network. Which it would. Unless you are using stateless configuration, of course.

But no, the game doesn't support it.

If I'm reading this correctly

http://www.dslreports.com/forum/r27919536-IPv6-Comcast-IPv6-Address-Assignment-Delegation - Comcast actually give a /128 address to the endpoint and then issue a public /64 for the LAN devices. (BTW although a /64 seems a lot, it is only a single subnet)

I do think more thought needs to be given to supporting IPv6 all the ISP's are finally turning this on - Although Virgin Media are lagging behind the rest and not setting theirs up til mid 2017 (go figure). One point about IPv6 is it does away with the need for NAT so you won't actually need to worry about port forwarding.

What is more concerning is what ISP's are going to do to maintain IPv4 connectivity in the transition period. If they move to DSLITE for example customers may well end up sharing a public IPv4 address via CGNAT, with all the problems that entails.

Ravenstar68
 
Back
Top Bottom