What ISP is IPv6 only with no IPv4 connectivity at all via DNS/NAT64? And I’m not talking about shooting your self in the foot and breaking your own connectivity to IPv4 by going IPv6 only on you own without it, because that would be your own fault.
Lack of IPv4 Address does not mean lack of connectivity to IPv4 services.
@Napsterbater said:
What ISP is IPv6 only with no IPv4 connectivity at all via DNS/NAT64? And I’m not talking about shooting your self in the foot and breaking your own connectivity to IPv4 by going IPv6 only on you own without it, because that would be your own fault.Lack of IPv4 Address does not mean lack of connectivity to IPv4 services.
As described in many posts before: DS lite shares one IPv4 with many users and therefore port forwarding does not work.
So does IPv4 CGNAT, and if you have IPv4 with CGNAT and no IPv6 you are screwed, but that is nothing that Plex can get around except for thier low speed relay, which is almost useless.
DS-LITE you still fully open IPv6, your plex server can be connected to via IPv6, note either the client will need IPv6 connectivity or you will need to use something like Cloudflare to accept/forward IPv4 -> IPv6 inbound to your server.
I’m behind CGNAT IPv4 and Native IPv6, Plex works just fine, I could make the Plex server IPv6 only, and it would still work just as the current setup.
That op was trying to say, a IPv6 only Plex server cant reach plex.tv since its IPv4 only, that would only be true if OP purposefully had a broken configuration, that lacked DNS/NAT64, That is the Ops own fault.
Plex cant magically fix you lack of inbound IPv4 connectivity. But again Plex supports IPv6, Plex can run on an IPv6 only network/system.
Yes, I think plex should support a translation from IPv4 to IPv6 and vice versa.
It does not make sense that a normal user needs to register secondary services to make it work. Also most of the users will not have the know how to set it up correctly.
You are not understanding how IPv4 and IPv6 work and cannot natively talk to each other. This is not somthing Plex can change. This is the way the internet works.
The only way an IPv4 client can connect to an IPv6 Only server/service is to have NAT46 on your router or ISP, and if on your ISP you are forced to use ISP DNS, no one is doing that just because of how ineffective it is, at that point just deploy IPv6, on the other hand its easy to support NAT64 allowing IPv6 only clients to connect to IPv4.
There is already a NAT64 Address range 64:ff9b::/96, DNS64 servers convert a domain with only an A to an AAAA, Ie. plex.example.com has A = 192.168.1.1 DNS server returnes the A plus an AAAA with 64:ff9b::192.168.1.1 or 64:ff9b::c0a8:101 (they are equal), Ipv6 client connects to 64:ff9b::192.168.1.1 is router trough the NAT64 it converts 64:ff9b::192.168.1.1 to 192.168.1.1 and passes along via IPv4 internet, vary simalar to NAT 44 (what you know of as “NAT” today) except instade of changing you LAN IPv4 to your WAN IPv4 this changes your IPv6 to a CGNAT IPv4.
Again Plex cant do anything about any of this. Neither can any other software you want host on your system in this setup.
If you want to host a Plex server it is upto you to either have a Public IPv4 without CGNAT, or a Public IPv6, you only need third party services like Cloudflare if you clients are IPv4 only, hence why I have been on roku to support IPv6, aswell as my ISP.
Again Plex works on IPv6 Servers, the cleints and the ISPs not supporting IPv6 are the issue.
Also www.plextv.com is IPv6, though plex.tv isn’t it only redirects to www.plex.tv, so now you dont even need NAT64 for the Plex server to run. But again clients connecting to the plex server are a diffrent story.
+1, please
@Napsterbater said:
What ISP is IPv6 only with no IPv4 connectivity at all via DNS/NAT64? And I’m not talking about shooting your self in the foot and breaking your own connectivity to IPv4 by going IPv6 only on you own without it, because that would be your own fault.Lack of IPv4 Address does not mean lack of connectivity to IPv4 services.
You’re thinking about this from an outbound connectivity point of view. It’s new inbound connections that’ll be an issue.
More and more ISPs are doing dual stack IPv6 with private IPv4 space, and overloading customers behind shared public IPv4 addresses. What this means is that the port-space is shared, so if you’re lucky, one customer might get to use port 32400 if the ISP and CPE implement RFC6887. (I haven’t found an ISP or an off-the-shelf CPE that does yet).
Whilst the Plex server itself supports IPv6 if you point your browser to it directly, the main Plex.tv interface doesn’t. So anybody behind NAT444 CGN, DS-Lite, MAP-T/E or single stacked IPv6 with NAT64, will have issues. (Sure, creating a DNS entry or giving out your Plex server’s public IPv6 directly are still options, but not very user friendly)
@detonate said:
@Napsterbater said:
What ISP is IPv6 only with no IPv4 connectivity at all via DNS/NAT64? And I’m not talking about shooting your self in the foot and breaking your own connectivity to IPv4 by going IPv6 only on you own without it, because that would be your own fault.Lack of IPv4 Address does not mean lack of connectivity to IPv4 services.
You’re thinking about this from an outbound connectivity point of view. It’s new inbound connections that’ll be an issue.
More and more ISPs are doing dual stack IPv6 with private IPv4 space, and overloading customers behind shared public IPv4 addresses. What this means is that the port-space is shared, so if you’re lucky, one customer might get to use port 32400 if the ISP and CPE implement RFC6887. (I haven’t found an ISP or an off-the-shelf CPE that does yet).Whilst the Plex server itself supports IPv6 if you point your browser to it directly, the main Plex.tv interface doesn’t. So anybody behind NAT444 CGN, DS-Lite, MAP-T/E or single stacked IPv6 with NAT64, will have issues. (Sure, creating a DNS entry or giving out your Plex server’s public IPv6 directly are still options, but not very user friendly)
No Im not.
The Plex Server App itself is fully IPv6 capable, it can listen and respond to request/clients on IPv6. Note you do have to use custom access URLs with correct AAAA DNS records. (and A if you want/can accept IPv4)
The plex.tv website itself does not need to support IPv6, it would be nice and would love to see them do it, but it is not required for the Plex Server Software at you house (or where ever) to support IPv6 Clients.
You also do not seem to understand how even when you connect to plex.tv you bowser is connecting directly to you plex server to get about 99% of what you see on the page, it is not routed through plex.tv (unless you are using relay, that is a different story), which again is why plex.tv can be IPv4 and yet your plex server be IPv6 only, and traffic from an IPv6 Client goes direct to you IPv6 Plex server ever going tough plex.tv.
As you can see, the first redacted line is the browsers direct connection to my plex server, the 2nd is its direct connection to my friends. very little comes from plex.tv and again it doesn’t matter if the client or server has has “Native” IPv4 or not, that does not affect how this works in any way. The server and client just need working IPv6, and some IPv4 access through ANY of the methodes you listed.
Now note, if you plex server only has a Public IPv6 and the client is IPv4 only, then you will have issues (though can use relay) whether or not plex.tv is Ipv6 enabled or not. And if you for some stupid reason have ZERO IPv4 connectivity (i.e. no NAT64 etc) then yes you will have a problem, but you will also have a problem with A LOT more than just plex.
TL:DR
plex.tv can be IPv4 only as it is.
Client can be IPv6 only with no “native” IPv4, just NAT64, etc.
Server can be IPv6 only with no “native” IPv4 just NAT64, etc.
Result: works just fine.
plex.tv being IPv6 enabled would be cool/nice, but not required at this point.
Yes I understand how it works, and I wasn’t meaning Plex.tv itself, I meant it doesn’t point friends to the a shared server on IPv6. Like you also repeated, I said it’s fine when using custom URLs or an IPv6 literal.
Which isn’t ideal for non-tech literate friends and family who just want to turn on their smart TV and connect to a remote Plex server.
Just reminding everyone to PLEASE click on the new “Vote” button at the top of the page. All of the previous “Like This” clicks aren’t being counted in the new voting/feature-request system.
It is important to be able to share a Plex server remotely through IPv6 only for security reasons to. With IPv4 you only have 2^32 minus a bunch of reserved addresses total, so something real easy to scan through and try to exploit. With IPv6, you have 2^64 network and an additional 2^64 subnet addresses per network, so something hackers can scan all they want, but are exceedingly unlikely to find anything at all with commonly used techniques. My firewall gets port scanned a bazillion times a day on IPv4 (I do check this from time to time), so this is a real and persistent issue. All you need is one zero day (or short lead time) flaw in the Plex server instance you are running on your home computer setup and you are done for with IPv4. With IPv6 they at least need to break into the main Plex service first before they can find you and then have to find a separate flaw in your local instance to do real damage.
Anyways IPv6 was developed in the 1990’s and IPv4 ran out of addresses back in 2011 and it is 2018 at the time of this writing. What are you people (developers) smoking thinking it is OK to not properly and fully support this Internet protocol standard?
+1 (I actually voted above) - Please vote at the top of the page!
Every day more and more households are unknowingly moved to a situation where Plex doesn’t work without some complex manual workarounds. This means most existing users don’t understand why it doesn’t work and abandon Plex, and potential new users briefly test it and don’t take it up in the first place. The (slowly shrinking) bulk of the Plex userbase still on end-to-end IPv4 shrug their shoulders and say “works for me, no need to prioritize”.
Only a very limited group of techies actually understands the problem and signs up for a 3rd party proxy/6-to-4 service, and/or configures custom URLs and domain names/AAAA registries.
I fully understand that IPv6 server-to-IPv4 client is inherently difficult to implement, but at least make sure that both IPv4-to-IPv4 and IPv6-to-IPv6 works seamlessly without any manual configuration. And in the case of a 4-to-6 or 6-to-4 situation, present the user with a clear popup informing why this specific connection is incompatible and requires manual setup.
+1
relly need it.
+1 here, my ISP has just switched me over to CGNAT and wants to charge extra for static IPV4 now. As part of this switch they did switch on native IPV6 but it looks like there is no way to remote access my Plex in it’s current form.
Out of curiosity does the “Enable server support for IPv6” checkbox do anything functionality wise at this stage? Is it just enabling IPV6 over the Local Network?
The “Enable IPv6” checkbox causes Plex to listen for connections to whatever IPv6 address the machine it is running on has. If you have your own domain name for that machine you can use it to access Plex over IPv6, it is the solution I have for myself.
I’ve done the same thing but it only seems to work via a browser over an IPv6 connection. The Plex mobile app (at least for Android) appears to only accept IPv4 IP addresses under “Manual Connections”. There is no support for IPv6 addresses or even domain names there. My server has an IPv6 address but CGNAT for IPv4. So, in my case at least, we definitely still need native IPv6 support across all Plex platforms.
You don’t need to enter it manually. You need to configure your domain properly at Settings -> Network -> Custom server access URLs and then the apps will automatically use it.
Thanks! Had no idea that existed. Using it now 
. Although not having to set that up in the first place would be nice.
This may be a dumb question, however, assuming that I have both static IPv4 and IPv6 addresses.
Assume that I have a custom domain. Also assume that I set both A record -> IPv4 address and AAAA -> IPv6 (both IPv4 and IPv6 are static / globally accessible). Finallly, assume that I’ve set the custom domain as a Plex custom access URL and enabled IPv6 support in PMS.
What happens when plex.tv tries to access PMS behind my custom domain? Will the custom domain resolve to IPv4 or IPv6?
I’m guessing that it will resolve to IPv4 for IPv4 only clients, IPv6 for IPv6 only clients, otherwise it will resolve to the preferred IP version (i.e., IPv6 by default in most OSes). Is my assumption correct?
