Access from IOT to plex LAN (local networks)

Plex Media Server
,
1

Server Version#: 1.19.3.2793
Player Version#: webplayer

I have my network split in different VLANs with FW in between.
In this the LAN and IOT vlan’s are relevant.
All my TV’s are on the IOT vlan, which has a seperate DHCP range.
In between the vlans, I have a firewall where I have opened port 32400 to the plex server.
I have given the local IP ranges in the plex server, and I’ve opened port 32400 towards the plex server.
I’ve given the ranges as:
192.168.1.0/24,192.168.2.0/24 etc.
I have disabled ‘use wan ip as local’.
I think I’ve done what I need to do.
But when I start the plex player on a TV it says the bandwidth isn’t enough. I don’t have any problems in playing, nor if I change it to use ‘original’ quality.
Looking in the control panel and in the webplayer it says ‘direct playback’ so it doesn’t seem to go through the plex cloud or anything.
I have a full gigabit connection and the firewall has no problem in keeping up.
So why do I see this message about the bandwidth?

2

If player and server are not on the same subnet – “Remote” is asserted.
Server and Players observe “Remote” bandwidth limit rules.

Start there; checking first the player(s) then the server

3

Will it even treat it as remote, when I enter all the ranges in the field ‘LAN Networks’?

4

You need both server and player to at least appear to be in the same subnet.

There are a number of different ways of handling this.

The setting in Settings - Server - Network tells server which networks(subnets) to treat AS-IF local when it comes to bandwidth management.

There is another way to handle this.

A technique I use, when the subnets are numerically adjacent, is to widen the netmask by 1 bit.

In your case,

  • 192.168.0.x and 192.168.1.x would be considered the same subnet with a netmask of /23

  • 192.168.2.x and 192.168.3.x would be considered the same subnet also with a subnt mask of /23

  • If we widen 1 more bit (/22); Now, from the server perspective, 192.168.0.x. -> 192.168.2.x will be on the same subnet.

I find this technique works the best when there are multiple small subnets and all the traffic can be handled by a single adapter. The players still exist on their individual smaller subnets and invisible to each other but the server sits “above” them all on the “bigger” subnet.

If you use this technique, you won’t need any settings in PMS.
The only setting you’ll change is in the adapter setting for the host itself.

5

Ok, well, the subnets shown are not the subnets in use, so, that’s a bit more tricky.

6

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