# IPv6 remote access for local lan and auth bypass input parser is broken

**URL:** <https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457>\
**Category:** Remote Access\
**Tags:** server-linux\
**Created:** [June 25, 2022, 7:21pm UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457 "2022-06-25T19:21:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ak\_hepcat](https://avatars.discourse-cdn.com/v4/letter/a/eb8c5e/32.png) [@ak\_hepcat](https://forums.plex.tv/u/ak_hepcat)\
**Post date:** [June 25, 2022, 7:21pm UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457/1 "2022-06-25T19:21:58Z")

</div>

Server Version#: plexmediaserver\_1.27.1.5916-6b0e31a64\_amd64.deb  
Player Version#: [n/a]

When attempting to add IPv6 addresses to either the “LAN Networks” or “List of IP addresses and networks that are allowed without auth” configuration options in the server network settings, something is broken in the parser.

The “/” is being stripped from the CIDR portion, resulting in the following errors in the log:

[0x7fa1fa302b38] ERROR - Error parsing allowedNetworks ’ 2000:100:1000:100::56’: Invalid argument  
[0x7fa1fa302b38] ERROR - Error parsing allowedNetworks ’ 2000:100:1000:100::64’: Invalid argument  
[0x7fa1fa302b38] ERROR - Error parsing allowedNetworks ’ 2000:100:1000:100::0’: Invalid argument  
[0x7fa1fa302b38] ERROR - Error parsing allowedNetworks ’ [2000:100:1000:100::]56’: Invalid argument  
[0x7fa1fa302b38] ERROR - Error parsing allowedNetworks ’ [2000:100:1000:100::0]': Invalid argument

etc.

IPv4 works fine, but… a lot of us are dual-stack, and happy-eyeballs means the preference is for IPv6… but with it broken this way, i’m always logging in “indirectly” instead of via direct access, and that’s bad for bandwidth and quality.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [June 25, 2022, 7:33pm UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457/2 "2022-06-25T19:33:20Z")

</div>

You have a leading space… OOOPS

```auto
[0x7fa1fa302b38] ERROR - Error parsing allowedNetworks ' [2000:100:1000:100::]56': Invalid argument

```

Silly question – Why is IPv6 faster than IPv4? In all tests I’ve run, the actual throughput is slower (not by much but measurable) because of the extra bytes required for the IPv6 addresses versus the IPv4 addresses.

---

<div class="post-metadata">

**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\
**Post date:** [June 26, 2022, 12:41am UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457/3 "2022-06-26T00:41:37Z")

</div>

Do those fields now support IPv6?

I would have said they only support IPv4, and pointed to this feature request:

[IPv6 support for "LAN Networks" and "Allowed Networks"](https://forums.plex.tv/t/ipv6-support-for-lan-networks-and-allowed-networks/685486)

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [June 26, 2022, 1:04am UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457/4 "2022-06-26T01:04:32Z")

</div>

OOPS, I missed that too. Sorry (been a long week)

It’s not implemented.

IPv4 only.

In a nutshell – Plex does not speak native IPv6.

---

<div class="post-metadata">

**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\
**Post date:** [June 26, 2022, 1:14am UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457/5 "2022-06-26T01:14:55Z")

</div>

I _think_ that putting _any_ entry in those fields also causes Plex to stop treating local IPv6 addresses as local.

Plex IPv6 does work OK for a few client types … as long as you don’t need to change those settings … and manually allow the port through any firewalls …

Apple devices do work well as IPv6 clients. And Web. I don’t think Android does. Roku doesn’t.

---

<div class="post-metadata">

**Author:** ![certuna](https://avatars.discourse-cdn.com/v4/letter/c/839c29/32.png) [@certuna](https://forums.plex.tv/u/certuna)\
**Post date:** [June 27, 2022, 4:49pm UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457/6 "2022-06-27T16:49:09Z")

</div>

Yeah it’s annoying - I know there’s a fair few client applications with old-ish codebases that can’t use IPv6 yet like Steam, Spotify Desktop, Nintendo Switch etc, but at this point Plex must be one the few remaining _server_ applications that don’t do IPv6. With VPS instances increasingly going IPv6-only, this is not making things any easier.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [September 25, 2022, 4:50pm UTC](https://forums.plex.tv/t/ipv6-remote-access-for-local-lan-and-auth-bypass-input-parser-is-broken/798457/7 "2022-09-25T16:50:04Z")

</div>

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