Sensorberg devices should be in safe virtual networks, separated from any other network device. All sensorberg devices will use a defined set of technologies to communicate to each other. This chapter will bring some technical details to all network operators who want to integrate our solution.
For simplicity, we recommend to use one VLAN for all sensorberg hardware. This ensures that no routing or firewall issues preventing our devices from connecting. If this is not possible for your installation, you may run sensorberg devices in multiple VLANs as long as the router or firewall is allowing the following set of services between all components:
| Protocol | Port | Purpose |
|---|---|---|
| TCP | 443, 9443 | Over-the-air upgrade of Access Hub Lite |
| TCP | 8883 - 8885 | Secure MQTT connection for sensorberg components |
Any sensorberg device uses the following, outgoing connections, which should be allowed by your firewall or router:
| Protocol | Port | Purpose |
|---|---|---|
| TCP | 22 | Emergency connection to our devices, opens up a SSH Tunnel |
| TCP | 80 | HTTP Traffic for operating system updates |
| TCP | 443 | HTTPS Traffic for connection to your Smart Space |
| TCP | 4505 - 4506 | Saltstack ZeroMQ connection for software updates by Sensorberg |
| TCP | 8883 | MQTT connection to your Smart Space |
| TCP | 9443 | Encrypted logfile shipping to Sensorberg cloud |
| UDP | 123 | NTP timeserver |