Network Layout of Broox Platform

The Broox Platform runs on local PCs, and communicates over HTTPS with Broox Studio and, optionally, the analytics collection backend.

In terms of network access, this means the running PC has to have outgoing connection access to the Broox Studio IP and the Analytics collection server (IPs can vary by customer, ask us).

Single PC layout

When running all Node services on a single PC, all communications between services is done preferentially through the network loopback interface (127.0.0.1 IP).

Multiple PC layout

Different nodes can be run on different PCs, and communicate between them by setting the listen IP address on their respective node.ini files.

• All Broox Nodes should be able to reach the machine running Broox Controller at port 9912 to configure themselves.
• Also, all Broox Nodes should be able to reach the MQTT server (mosquitto) at port 1883, running on the Broox Controller machine.
• Broox Controller needs internet access to the Broox Studio IP and the Broox Analytics backend.
• Any Media Player wanting to report media status can POST it to Broox Controller at port 9912.

Used (default) ports

• Broox Studio: Port 443 (HTTPS)
• Broox Analytics backend: Port 443/9443 (HTTPS)
• Broox Controller: Port 9912 (HTTP, localhost)
• Mosquitto MQTT Broker: Port 1883 (MQTT), 1884 (Websocket, optional).
• Broox Vision Node: Port 5000 (HTTP, localhost)