ISP: Unitymedia, DS-Lite and no connection from the myPlex service to my Plex Server. Fortunately I did not apply for paid service and will wait until this problem will be solved in the future.
I recognized the Plex stuff by accident in the Synology's third party apps store.
Synologys internal "Video station" app works with IPV6 from the internet with a mobile device and the "quickconnect" functionality. So for me it looks like I will end up to use this platform...
Too bad, MyPlex interface had a little bit cooler outfit.
Same Problem with M-Net vdsl in Munich. No IPv4, just DS lite and you are forced to use a mediocre fritzBox, no freedom of choice, no vdsl access data provided to change your router. These two no gos are the reason I terminated the contract with M-Net, signed with easybell. Freedom of routerchoice and until now they only provide IPv4 IPs. Full speed vdls (50/10), VOIP, 24,- EUR, no contract period. Router needs to be able to adjust a vlan tag (7). Might change in 2015 though... so a IPv6 solution is needed anyway in the long run...
Would be nice to get some kind of feedback on this.
I am in Munich, Germany with m-net - there is a 5€/month option to get an IPv4 address, but I obviously have this rather fixed (for free ;) ) by plex...
I'm also experiencing this. I need a way to publish my server via IPv6. If we had the ability to publish a domain with AAAA records, that would also be a viable workaround.
I also require IPv6 connectivity. My ISP completely dropped my external IPv4 connectivity without warning, and now there's no way to stream my Plex media outside my home network. I have only an IPv6 external address. I can still connect out on IPv4, but nothing can initiate a connection in on IPv4. I am able to setup an IPv4 to IPv6 proxy outside my network, which works for connecting to other home servers.
I am also experiencing issues regarding lack of IPv6 support. The IPv4 connection between my house and the colo where my Plex-server is located is extremely unstable, but I have solid IPv6 between the two locations. However, this does not work for my mobile clients or using plex.tv.
We're now in 2015, IPv6 must have feature parity in most products and services.
<span style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;margin:0px;font-size:14px;font-weight:bold;color:rgb(51,51,51);"><a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2FGrewiGreg%2Fstatus%2F562884313042403329%3Fcn%3DcmVwbHk%253D&t=1&cn=cmVwbHk%3D&sig=2faa8551b1779a222cb12f8644c278ae0407ea64&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1284'>Gregor</a></span><span style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:12px;color:rgb(153,153,153);"><a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2FGrewiGreg%2Fstatus%2F562884313042403329%3Fcn%3DcmVwbHk%253D&t=1&cn=cmVwbHk%3D&sig=2faa8551b1779a222cb12f8644c278ae0407ea64&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1284'>@GrewiGreg</a></span>
<p style="color:rgb(51,51,51);font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:14px;"><a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Fplexapp%3Fcn%3DcmVwbHk%253D%26refsrc%3Demail&t=1&cn=cmVwbHk%3D&sig=0ad3c6f494506787cdbfd7e4a195d4338e839d89&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1291'>@plexapp</a> hey guys, the IPv6 problem still persists:<a data-ipb='nomediaparse' href='https://t.co/redirect?url=https%3A%2F%2Ft.co%2F08A7zWhBO6%3Fcn%3DcmVwbHk%253D&t=1&cn=cmVwbHk%3D&sig=c3160d1db23532c02dd69579b9369f374e9b3bd7&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1288'>forums.plex.tv/index.php/topi…</a> <br>
Would be great to get some kind of update on this? :-)<a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2FGrewiGreg%2Fstatus%2F562884313042403329%3Fcn%3DcmVwbHk%253D&t=1&cn=cmVwbHk%3D&sig=b3224ff7360ec137285db6ed808499b745416afb&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1287'> - 04 Feb</a></p>
<span style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;margin:0px;font-size:14px;font-weight:bold;color:rgb(51,51,51);"><a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Fplexapp%2Fstatus%2F563035284003368960%3Fcn%3DcmVwbHk%253D&t=1&cn=cmVwbHk%3D&sig=01d084e8f3f83949a81852190bc5cc20329b34b6&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1264'>Plex</a></span><span style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:14px;color:rgb(153,153,153);"><a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Fplexapp%2Fstatus%2F563035284003368960%3Fcn%3DcmVwbHk%253D&t=1&cn=cmVwbHk%3D&sig=01d084e8f3f83949a81852190bc5cc20329b34b6&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1264'>@plexapp</a></span>
<p style="color:rgb(51,51,51);font-family:Georgia, 'Times New Roman', serif;font-size:22px;"><a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2FGrewiGreg%3Fcn%3DcmVwbHk%253D%26refsrc%3Demail&t=1&cn=cmVwbHk%3D&sig=13ad0231c59c19f10e1f0b9c7712382468950c4e&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1271'>@GrewiGreg</a> We're aware and working on it, but not nearly as simple as it might seem. We know users are being affected.</p>
<a data-ipb='nomediaparse' href='https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Fplexapp%2Fstatus%2F563035284003368960%3Fcn%3DcmVwbHk%253D&t=1&cn=cmVwbHk%3D&sig=133be94ed8c1c0aff3e4e330164728cc9e564f2f&iid=9c5702958b9042b8b728f7299fa99819&uid=1345067334&nid=27+1267'>06:04 PM - 04 Feb 15</a>
</blockquote>
I not sure I am following this discussion but here are my thoughts
If you are native IPv6 thn you don’t need an Portman of any sort to access an IPv6 server you just open a port on a firewall and it’s accessible - there is no NAT in IPv6
Assuming MyPlex is acting as a directory service that points clients to servers and provides some level of ACLs around that access then in theory there is no reason that it could not do so for IPv6
The problem arises when either the MyPlex cloud or the connecting client cannot speak IPv6 then you have a PMS address but no way to connect to it - IPv6 cannot speak to IPv4 and vice versa
4 I thought DS-Lite was supposed to address the legacy side of things and you should be able to request a DS-Lite IPv4 Portmap to address the sort of double Nat that goes on - it has been a while since I looked at DS-lite specs but they were looking at extending UPNP to handle this
5 Can you not request Dual Stack on your connection and get a real IPv4 rather than a shared one?