So I have learned that you should not make large subnets. And best practice is not to make large subnets at all.
The statement that most people have only one or two subnets in their home network may be true, but there are exceptions.
Besides, I don’t understand the problem now. Everything works as it should (from my point of view), except that a limit is applied when the WAN address is different. The problem should be fixed and everyone is happy. And for “99.99%” of home users, the feature makes no difference anyway.
But I can already tell that the discussion here is pointless and a change/bugfix is not being sought here.
I agree that many home networks are more complicated than necessary. [shudders]
A Plex server and client are very often in different subnets. That’s true for Docker installs, for instance.
Plex added the clever publicAddressMatches="1" same-gateway detection to detect and treat those clients as local, even though they aren’t on the same subnet.
If this thread’s situation isn’t supported, what’s the purpose of the LAN Networks setting?
It’s currently doing something. The Dashboard is showing them as Local.
That’s why my theory is that this is a small bug in the logic. The same-gateway detection is being given higher priority than the LAN Networks setting.
