Hi,
I entered my v6 /48 under ‘LAN Networks’ along with my v4 /24 & /12. When clients play from the v4 networks they show as ‘local’ however when client play from the v6 /48 they are classified as remote.
Is this setting supposed to support IPv6?
Server Version#: 1.31.3.6868
Player Version#: 1.66.1.3632-4d9c7716
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
It’s supposed to work for IPv6 but doesn’t.
The issue has been written up and submitted to Engineering.
I’ll see if I can get some traction on it.
Are you in an IPv6-only WAN ISP as well?
Okay, thanks for that. My ISP provides me with one v4 address and delegates a /48 of v6 space, which I make use of.
With ISPs handing out /48s to everyone, at current rate I expect IPv6 to run out really fast too. It won’t take long to really make a mess. How many of us need 65536 networks in our home? 
That’s how it should be, one /48 per curstomer is the IETF recommendation (RFC6177), although in practice that’s mostly typical for Pro connections, a /56 is also allowed and most prevalent among residential ISPs.
Even with /48 allocations we’re not running out of space anytime soon - within the current 2000::/3 public space, we can issue over 35,000,000,000,000 of them.
If I’m not mistaken, Plex can handle IPv6 or IPv4 subnets in that “LAN networks” box, but not a combination of both, can you confirm @ChuckPa ?
PMS should handle either and both (dual stack networks / machines) but there’s a bug which I brought up in today’s meeting. (There’s an open bug submitted for this - #14234)
Upon review, the code currently in place only supports IPv4 (32 bit) and the parser itself doesn’t support IPv6 addressing formats.
The work to do that is now scheduled. I don’t know when it will be released as there are some other higher priority tasks to complete first.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
