Hardware Considerations
A standard Igloo system will typically come with a full set of networking equipment to fit the requirements of the system. In the case of an Igloo system being installed into a pre-existing network that cannot be added to by Igloo’s equipment, there are a couple of considerations that will ensure the Igloo operates as best it can.
A standard IMP is fitted with a 10Gbe network card (with 10Gbe port). Many streaming aspects of the Igloo (NDI, Dante, other streaming protocols) can be quite bandwidth-intensive, so a 10Gbe switch is best placed to help ensure the smoothest streaming playback.
Optimal performance is achieved when AV streaming is on a separate VLAN - best practice is to have separate VLANs for NDI devices, a separate VLAN for control systems, and a separate VLAN for Dante (if required)
Some peripherals in an Igloo System utilise the Power over Ethernet standard and, recently with the edition of some 4K NDI PTZ webcams, this can include a requirement for PoE++ network switches.
Firewall Rules
An Igloo media server can be entirely self-contained, though in most cases internet access will be required for system updates, content downloads, web services, etc. There may also be requirements for the media server to communicate with clients on a corporate network, e.g. for NDI streaming. The following table describes ports for common services that are used by an Igloo Media server, as well as the scope.
...
Port | Scope | Description | Source | Endpoint |
|---|---|---|---|---|
TCP 4352 Inbound TCP & UDP 3620 Inbound | Igloo Network | Projector communications and control. | IMP/Media Server | Projectors |
UDP 9000-9020, 10000 Inbound | Igloo Network, Outside (Optional) | OSC Protocol. | IMP/Media Server | Tablet |
TCP 49152 - 65535 Inbound | Igloo Network, Outside (Optional) | NDI Streaming. | IMP/Media Server | IMP/Media Server |
TCP 8086 | Igloo Network | Peruse-a-rue application. | IMP/Media Server | IMP/Media Server |
TCP 3000 | Igloo Network | Matterport application. | IMP/Media Server | IMP/Media Server |
TCP 3001 | Igloo Network | GeoCV application. | IMP/Media Server | IMP/Media Server |
TCP 10000 | Igloo Network | Igloo Controller Service. | Tablet/IOS device running Igloo Touch | IMP/Media Server running Igloo Controller Service |
TCP & UDP 53, 80, 443 Outbound | Outside | DNS, web connectivity and Windows updates. | IMP/Media Server | DNS Server(s) |
TCP 80, 443, 8200 Outbound | Outside | GoToMyPC Remote access. | IMP/Media Server | GoToMyPC |
TCP & UDP 5938 Outbound | Outside | TeamViewer Remote access | IMP/Media Server | TeamViewer |
UDP 162, 319-320, 2203, 4321, 14336-14600, 4440, 4444, 4455, 5353, 8700-8706, 8800, 8751, 16000-65536 Inbound | Igloo Network | Required if using Dante Audio and Controller. Allows audio routing, clocking, control, monitoring, and related services. See Dante Audio section below for a detailed description of these ports. | Dante Senders (Typically, IMP/Media Server, Dante enabled DSPs) | Dante Receivers |
TCP 27036 Inbound | Igloo Network | TouchOSC Editor. Required for synchronising TouchOSC layouts from the editor to remote devices. | IMP/Media Server Remote devices (tablets, phones etc) | Remote devices (tablets, phones etc) IMP/Media Server |
Internet Connectivity
As shown in the above table, ports for web connectivity are optional but preferred for Windows Updates, remote support, and general usability. Windows Updates should generally be allowed and installed for security fixes, though a day should be set aside for larger cumulative and feature updates that may require post-install testing.
...