====== Plan a reliable private network ====== ===== Same trusted LAN ===== Controller, encoders, and players must be reachable. Guest Wi-Fi and access-point client isolation can block discovery or control even when devices share an SSID. VPNs and multiple active adapters can change routing. Use a dedicated trusted network or VLAN for the DisplayHUB system and its TVs, separate from personal/work devices and untrusted clients. Permit the local traffic the controller, encoders, and players need; multicast discovery may require them to share a network segment. Use wired Ethernet for fixed equipment when practical. Keep management private; never port-forward controller or encoder management interfaces. ===== Addresses and discovery ===== Reserve DHCP addresses for controller and encoders. Controller management uses '':8081''; Android encoder management uses '':8080''. Multicast DNS resolves ''displayhub.local'' only where the client and network support it. If it fails, use the displayed IP and port. ===== Capacity ===== Each stream and receiving display consumes network capacity. Do not size Wi-Fi from advertised PHY link speed alone. Test simultaneous streams, busy-hour load, interference, coverage, packet loss, and audio/video behavior. Add screens gradually. Internet-based source services and guides can stop during internet outages even when local routing remains available. See [[:getting-started]] and [[:troubleshooting:playback]]. ---- [[:start|Knowledge home]] | [[:getting-started|Getting started]] | [[https://discord.gg/B6aSSdwFHy|Ask in Discord]]