When looking at the Dashboard streams on the local LAN are being listed as “Remote” and getting throttled per my remote settings (actual remote seem to be properly registering as remote). Devices are showing their correct interior network address
and the server knows its address
which is in the same LAN.
what does route or ip show as the default route / adapter ?
Also, do you have any special settings in Settings - Server - Network - SHOW ADVANCED?
I forgot to include the ‘LAN’ networks are specified
This probably invalidates the question of the route but there is only one interface on the system:
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.128.1 0.0.0.0 UG 100 0 0 enp4s0
192.168.128.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0
192.168.128.1 0.0.0.0 255.255.255.255 UH 100 0 0 enp4s0
This has worked in the past as well, not sure when it broke but I am assuming with 1.19.3 series as it was only recently I started seeing it chug a bit before starting which I assume was the fact its needing to transcode suddenly
With the host itself on 192.168.128.0/24, you don’t need specify it as LAN.
The IP and netmask will define local for you.
This does raise a question and maybe even a bug/regression,.
What happens if you remove 192.168.128.0/24 from the LAN list?
I ask this because, when you declare it there, you’re telling PMS “Hey, this is remote but I want you to treat as local”.
You don’t need do that for obvious local LAN segments.
I wonder if PMS might be inverting the LAN/Remote flag unnecessarily . (tht would be a very weird bug)
Well and thats why I initially brought up the example of an actual remote vs my local both showing as remote. It doesn’t look like it is inverting necessarily, otherwise I would expect the remote to go local.
If I remove the .128 range it still shows improperly as remote. I did poke around it a bit and realized I had spaces after the commas between the address ranges. Removing the spaces did get it to trigger back as local it looks like so the input parser there might be improved.
Having said that, if you expect it (with ANY defined lan segments) to still treat obvious local as local then it is behaving the same way with only OTHER lan segments defined. I toggled the preferred network from any to the single defined address, still showing as remote when it is not specified.
Server is offering update to 1.19.3.2843 but I will hold on any changes for now.
It is late note so hope its clear enough but the TL;DR of the above is unless I specify the solitary lan (.128) explicitly without whitespace it reports as remote
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
