I have two IPv6 /48s I want to list in the “LAN networks” setting.
When I add them after the IPv4 networks, I get this error in the logs
ERROR - Error parsing allowedNetworks ' 2001:xxx:xx::': Invalid argument
My string looks like this:
192.168.1.0/255.255.255.0,[IP address]/255.255.255.255,[IP address]/255.255.255.255,2001:xxx:xx::/48,2001:yyy:yy::/48
Watch out for the leading space. It’s not valid and will kick the error
Yeah, there’s no spaces in the line.
Define it like this 2001:xxxx:xxxx:xxxx::0/48
What version of PMS are you using?
Can you provide screenshot? You can send via PM.
@Ach!lles said:
Define it like this 2001:xxxx:xxxx:xxxx::0/48
No dice.
Jun 19, 2017 10:23:55.856 [0x7fe0aeffe700] ERROR - Error parsing allowedNetworks '2001:xxx:xx::0': Invalid argument
Jun 19, 2017 10:23:55.856 [0x7fe0aeffe700] ERROR - Error parsing allowedNetworks '2001:xxx:xx::0': Invalid argument
@ChuckPA said:
What version of PMS are you using?
Plex Pass 1.7.3.3937
Working with Achilles, I’ve narrowed it down to the module in PMS which has an issue.
The module was originally created to support legacy IPv4 clients and doesn’t include IPv6 (64 bit address) support. I believe this is an oversight because the whole purpose of “Enable IPv6 support” is for those LAN clients. I am able to specify your address values in the LAN Networks with no issue. Only in the Authentication module does it encounter an error .
I am writing this up and submitting to Engineering shortly.
Fantastic. Thank you!
Any news on this? It appears to still be broken, at least in 1.8.4.4249
-Matt
No. Engineering’s priorities are unknown as to when this will be looked at.
Hey Guys,
sorry for digging that thread out. But its exactly my Problem.
My outside-home-clientis connect to plex via openvpn (same server als plex) with Netzwork 10.8.0.0. So i would like to give plex the home-network so it could treat all the traffic from 10.8.0.0 as WAN-Traffic.
So i entered 192.168.178.0/24 and 2a02:908::/32 in the “Lan networks”-Settings
But i keep getting the error:
ERROR - Error parsing allowedNetworks ‘2a02:908::^@32’: Invalid argument
Do you have any suggestions?
Thank you verry much in advance!!
KR
Thorsten
2018/11/11 and this is still a problem for me too.
Yep, its pretty annyoing. All the cool bandwith features are useless for us who provide Plex for external Users only via VPN…
Any update on this issue? Just noticed PMS is classifying my IPv6 network clients as remote, too.
Assuming it was a parsing error (either delimiting the forward slash or address expansion) I’ve tried all of:
2001:630:301::/48
2001:630:301:://48
2001:630:301::\/48
2001:630:301:0:0:0:0:0/48
2001:630:301:0:0:0:0:0//48
2001:630:301:0:0:0:0:0\/48
…and get the same “Error parsing allowedNetworks '<blah>’: Invalid Argument” error in each case.
Would love to see this fixed.
Looking at other IPv6 issues with PMS, parsing IPv6 CIDR address formats seems to be a common issue with defining local and remote networks and the no-auth ACL.
Support IPv6: do or do not, there is no try
Nope, no fix so far. Thats pretty poor for such a cool Software.
Still an issue nearly a year later after the last reply. Bumping to revive interest.
Also bumping to avoid this disappearing. IPv6 is a real thing, Plex. It’s disappointing this is still an issue 2.5 years after being reported.
Jep ist still an issue. There is also no WAN Access for IPv6.
Plex!, Start moving with the Times. Nearly anybody has an IPv6 but not everybody has a routable IPv4.
Start supporting Dualstack! Or at least, let the User manually set the WAN IP for those of us who need to Tunnel through a VServer because of you lacking IPv6 Support.
What about “Custom server access URLs” in network settings?
