No direct connection with DS-Lite and portmapper

Server Version#: 1.17.0.1709
Player Version#:

Hello,

I have googled for hours and experimented a lot, but now I am out of ideas so I hope to find some experts here to give me a clue on how to proceed :slight_smile:

I have a new ISP with only IPv6 connection via DS-Lite.
I have a freshly installed PMS on an Ubuntu computer, so no special settings or anything.
I have set up portforwarding with DynDNS via the router and I have configured a portmapper (feste-ip.net).
Portforwarding and portmapper are set for port 32400.

From the network perspective everything seems fine as far as I can see. I tested with SSH on port 22 and I can connect to the computer from other networks (IPv6 via the DynDNS name and IPv4 via the portmapper).

In the settings for PMS I have only set the custom Server Access URL and provided the portmapper data there as I read in other forums. Then I tried to enable remote Access, which is green for a few seconds and then it switches back to " Not available outside your network".
When accesing the webinterface from outside the network I can see the PMS but only get the Plex Relay bandwith of 0.7mbps which iss not an option to be honest :slight_smile:
The portmapper website says the port 32400 is not reachable, even though the port forwarding is configured the same as for SSH, which is working fine.

So my first question is:
Is it possible to configure a direct connection to a PMS behind DS-Lite?
I cannot be the only one with such setup :smiley:

And so my second question:
What am I missing? Where do I have to search the problem?

Here are two screenshots of my PMS settings:


I forgot to mention, the computer running PMS is connected directly with the one and only router.
There are no other router, access points or anything involved so I do not really understand the message that there shall be a double-NAT problem


Please clarify what a “DS-Lite” is? Nintendo DS Lite device ?

If you have a chain, Computer -> something -> router -> Internet, and the addresses blocks change at each hop, PMS will detect as a possible double NAT and so flag it.

It compares 1st hop WAN IP with Public-facing IP. If not the same then it calls out “Double NAT”

DS-Lite is particularly sold in DE. It is a DSL line with no public IPv4 address (or only a NAT’ed one).
But AFAIR each user has a public IPv6 address.

Thanks Otto,
If this is the case then I don’t know the outcome as IPv6 implementation in PMS is not complete. PMS does require IPv4 for LAN and metadata as we’ve seen to date.

Ah ok, I didn’t know DS-Lite is something special here in Germany :man_facepalming:

But yes, as far as I understand it myself (far from being an expert on network topics), I have (only) a public IPv6 address but outgoing connections are kind of emulated at the ISP to also be able to connect to IPv4 targets on the internet.
The problem is that this does not work in the other direction. When you try to call my public IPv6 from an IPv4 network (like from my smartphone) it does not work.

As I understand that is the same problem with plex.tv as this also uses IPv4.

So I read a portmapper can help. That is basically an external service where I put in my public IPv6 and get an “alias” which is in the IPv4 network. When I call this IPv4 alias, the protmapper forwards the connection to my IPv6.
As I said that works for e.g. SSH, but I cannot get it to work for plex.

The custom URL I put in the network settings is that said IPv4 alias I got from the portmapper service.

Thank you for that.

As a port-mapper device, this sounds like it is behaving as a IPv6-IPv4 translation proxy.

You won’t be able to direct-connect to it unless the endpoint (IPv4 end) is on your subnet.
( IPv6 WAN -> IP4 LAN) and hides this translation.

Proxy devices are inherently tough to configure because when done incorrectly, you are completely vulnerable to the internet.

I will reach out to some networking friends (better skilled than I) and see how this might be arranged but, to be honest, it’s not looking promising to have a direct connect unless PMS itself is IPv6 (which PMS isn’t fully ready for). Internet -> modem -> portmapper -> server is still 2 levels of NAT.

Thank you for that information, even though it doesn’t sound very promising

Seems the posts I readwhere people said they got it running maybe just reffered to an indirect connection.

So just to clarify for myself. If I understand that right, in case there is no way of getting it to work with the port-mapper, then I would have to wait until PMS fully supports IPv6?
Because a direct connection from any IPv6 net to my IPv6 PMS (completely excluding the port-mapper in this scenario) is not supported at the moment, right?

Please read this thread (in German) in full: Tutorial: Außenzugriff auf Plex fĂŒr Unitymedia DS Lite IPV6 Nutzer

Thank you for the answer Otto, but that is exactly the thread which I initially referred to when I tried to set up the PMS :smiley:
And I can’t figure out why it is working for him but not for me. My assumption now is that maybe that isn’t a direct connection, too. Because at one point in that thread it says that there is still the message “not available outside your network” but that it would work nevertheless.
Well maybe he meant it work in the same way as for me, with the Plex Relay and 0.7 mbps 


That is correct. The built-in connectivity test will always fail for “custom server URLs”.
You can only use things like canyouseeme.org to test (or go outside and test yourself over a foreign WiFi or mobile data)

DS-Lite is not something specific to Germany, it’s how IPv6 is increasingly being rolled out all over the world. Millions of households are already behind a DS-Lite connection and over the next decade the rest will probably follow. Problem is, end-to-end IPv6 by now ‘just works’ for pretty much every OS and application so nobody notices they are behind CG-NATted IPv4 until they try to run a specific server application like Plex that doesn’t support IPv6 fully.

Plex indeed only works over IPv6 with complex manual workarounds (custom URLs or 3rd party 6to4 tunnels), we’ll probably all have to wait until the bandwidth bills for Relay get high enough for Plex to notice. Meanwhile, vote for this feature request: https://forums.plex.tv/t/ipv6-support-for-myplex/

(six years and counting, yes
)

Well, just to make a final statement in case anyone else might stumble upon this post.
Since I have booked some additional features I was able to negotiate with my ISP to change my connection to a full dual stack. So now I have a public IPv6 AND a public IPv4 adress so Plex works fine.

Until the ISPs will abandom IPv4 for their customers completely, so lets hope Plex will be fully supporting IPv6 by then

Until that feature is supported it seems the only thing you can do is trying to get an IPv4 from your ISP.

Thanks for all the helpfull information nevertheless!

This topic was automatically closed after 90 days. New replies are no longer allowed.