Network requirements

Is a firewall active in your network? If so, please check the following network requirements with your network administrator:

  • Please activate a DHCP server in the network – for automatic network integration (IP address assignment for the CUBE)
  • Please enable port 443 towards the Internet - for encrypted communication to the Internet
  • Please enable the NTP protocol (UDP port 123) towards the Internet - for time synchronization

 

Internet Settings

Priority Port Protocol Protocol Name Description
required 123 UDP NTP Access to the time server the dhcp server provides - without NTP no secure connections can be established because certificates can not be validated.
required 53 UDP DNS Domain Name Service - name resolution on the Internet. This protocol is used to resolve Internet addresses (e.g. *.tapio.one) into IP addresses.
required 443 TCP HTTPS Encrypted connection to the Internet. Required for connecting the tapio Cloud and the HOMAG Cloud Services.
optional* 13 ICMP ICMP Outgoing pings are required for checking the connection to the tapio cloud.

* optional: These ports are not required for CUBES operation and are used for diagnostics and analysis in support cases.

Internal network settings

For diagnostic purposes of the HOMAG CUBE, it is not necessary for the ports to be enabled via the Internet connection. Only an internal release must be made in the customer network if, for example, a firewall is in use.

Priority Port Protocol Protocol Name Description
required 45001 TCP HTTP IoT CUBE diagnostic page
(only necessary up to version 0.129.7).
After that access via port 80.
required 5555 TCP HTTP Cloud-Connector diagnostics page
optional* 5353 UDP mDNS Multicast dns service to provide its name / services
optional* 5355 UDP mDNS Link-Local Multicast Name Resolution; allows hosts to perform name resolution for devices on the same LAN.
optional* 13 ICMP ICMP Incoming pings to check if the CUBE is online - Attention: Only one ping per second is allowed!
optional* 22 TCP SSH The ssh daemon is deactivated by default and needs to be activated manually using the diagnostics webinterface. In cases of local and remote servicing the service stuff can activate the feature manually. If the ssh daemon is activated the status is shown in the diagnostics webinterface.

* optional: These ports are not required for CUBES operation and are used for diagnostics and analysis in support cases.