What a ScreenlyOS player needs from your network: outbound hostnames and ports, Wi-Fi and static IP setup, 802.1X, time servers, and what each diagnostic error means.
Players make outbound connections only. Nothing needs to be opened up to reach them, and you can run as many as you like behind one public IP.
What they do need is a route out to a specific set of hostnames, a working clock, and, on a restricted network, an allowlist that covers both.
How Screenly screens use your network, what they need from it, and how much traffic to expect.
Connect a player to Wi-Fi, set a static IP, configure time servers, and use a cellular connection.
The hostnames and ports to allow, which wireless networks and authentication types players support, and what each network diagnostic error means.