Is there any timeline for making Plex fully IPv6 compatible?
Currently you can enable IPv6 support for the server and connect to it over it’s IPv6 address from a web browser. But it’s only the front end that connects over IPv6.
I have an IPv6 tunnel with Hurricane Electric’s Tunnelbroker.net service which also gives me a pulic /64 I currently have the tunnel endpoint on a desktop PC which advertises the /64 to all other devices on my network.
So with a separate laptop on my network I connected to the server over it’s public IPv6 address using Chrome logged in and played a video. All well and good - or so I thought.
However I then turned off IPv4 on the laptop, Meaning as far as it was concerned it only has access to IPv6 - now although the server lets me into the opening screen the Laptop reports it can’t access the server.
So it’s clear that the IPv6 connection is a shell. Most of the background conversation still takes place over IPv4.
Contrast this with Netflix, not only can I play videos in Chrome with IPv4 turned off, but the Netflix App in Windows 10 also streams over IPv6 only as well.
With Many ISP’s now implementing IPv6, surely it’s time true IPv6 support for Plex was given a higher priority?
The login process itself requires IPv4 but once Chrome is signed in it CAN reconnect to the server over IPv6 only. However it can’t connect to Plex.tv so the icon in the top right corner does not show as being logged in.
Video’s PREFER streaming over IPv4 even if the browser connects over IPv6 - (verified using wireshark). But will stream over IPv6 if it’s the only protocol available.
Plex Apps still only support IPv4
One of the key sticking points is the login process. If the designers want to make plex truly available over IPv6 then the first step is to actually enable logins over IPv6. Which means adding IPv6 support to Plex.tv and any associated servers used for logging in.
If you are turning your IPv4 off without you or your ISP having DNS64/NAT64 in place, you are doing it wrong. You will need to run dual stack or have some access to the IPv4 world for a LONG time.
Only 23.5% of Alexa Top 1000 sites are even enable available over IPv6, so you can’t effectively use the internet with Pure IPv6.
The main point of IPv6 in plex is allow you to connect to your Plex Server when it can’t be reached via IPv4, because you are behind CGNAT for IPv4 but your ISP has deployed IPv6.
It’s not expected, and its stupid to expect the client not being about to reach Plex Login Servers that have IPv4 only addresses, becasue again you should not expect the “internet” to work without access to Ipv4 only sites/services. It’s going to be another 10 years probably longer before you can ignore IPv4.
@Napsterbater said:
If you are turning your IPv4 off without you or your ISP having DNS64/NAT64 in place, you are doing it wrong. You will need to run dual stack or have some access to the IPv4 world for a LONG time.
Only 23.5% of Alexa Top 1000 sites are even enable available over IPv6, so you can’t effectively use the internet with Pure IPv6.
The main point of IPv6 in plex is allow you to connect to your Plex Server when it can’t be reached via IPv4, because you are behind CGNAT for IPv4 but your ISP has deployed IPv6.
It’s not expected, and its stupid to expect the client not being about to reach Plex Login Servers that have IPv4 only addresses, becasue again you should not expect the “internet” to work without access to Ipv4 only sites/services. It’s going to be another 10 years probably longer before you can ignore IPv4.
português: Deveriam habilitar o ipv6 para plex.tv, ja que é o futuro, por que ficar adiando.
Inglês: Should ipv6 be enabled for plex.tv, since it is the future, why postpone
