Right. Usually T-Mobile equipment is pretty customized. Maybe this one is a bit more off-the-shelf and they didn’t customize it enough. 
That’s what I have to assume.
If T-Mo would supply functional virtual server options, or if PMS supported IPv6, either option would work for me. That’s pretty much the only gripe I have about switching to T-Mobile Home Internet.
I can’t imagine they really want people running servers on mobile connections anyway, not really. So it might be convenient to them that it doesn’t work.
I don’t think they particularly care (servers generate traffic, but nowadays with streaming video, clients consume massive amounts of traffic too), but what they do care about is the cost of the IPv4 address space they’d have to buy in order to give everyone their own address. If you look at the mobile carriers that have already rolled out IPv6, no issues running servers with that.
PMS does support IPv6 by the way, although unfortunately you have to set it up manually.
Edit: You linked that before. I’m an idiot. Thanks haha.
Do you have specific steps on how to set up IPv6 access? I can’t seem to pin that down, but I assume if it’s supported, there is documentation on it somewhere.
There’s a setting to turn IPv6 on so that PMS starts listening on IPv6 (see the link of @TeknoJunky ), but that doesn’t tell the clients what the address is, which is what you really want.
In order for clients to connect to PMS over IPv6 you need to push a custom server URL to them. There’s a short explanation here: Ipv6 support for myplex - #269 by thornrag
With IPv4 this happens automatically behind the scenes, with IPv6 you (unfortunately) still have to do it manually. I wish the developers would add a simple input box “IPv6 address to push to the clients”, so we don’t have to construct the URL ourselves anymore. (Oh, and support PCP/IGDv2 for automated port opening, but that’s for another time).
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
