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. https:// *.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.
Settings for the local (internal) network
The HOMAG CUBE has several diagnostic services that should be accessible in the local network. It is recommended that these services only be available in the local / internal network.
| Priority | Port | Protocol | Protocol Name | Description |
| required | 80 (45001) | TCP | HTTP | Diagnostic page of the HOMAG CUBE |
| required | 5555 | TCP | HTTP | Local diagnostic page of the tapio Cloud-Connector |
| optional* | 5353 | UDP | MDNS | Multicast DNS-Deamon to provide the HOMAG CUBE name in the local network |
| optional* | 5355 | UDP | LLMNR | 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 is allowed per second! |
| 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 diagnostic pages and on the status icon. |
* optional: These ports are not required for CUBES operation and are used for diagnostics and analysis in support cases.
Required URLs
| Used for | URL-Pattern | Description / Further Information |
| tapio Discovery-Service | https://disco.tapio.one/ | Further information: |
| tapio Realtime Data | https:// *.azure-devices.net/ https://iothubcloudgwayprodwe01.azure-devices.net | Further information: |
| tapio Diagnostics Data | https://dc.services.visualstudio.com https://dc.applicationinsights.microsoft.com See: https://docs.microsoft.com/en-us/azure/application-insights/app-insights-ip-addresses | Further information: |
| tapio Login | https://tapiousers.onmicrosoft.com https://login.microsoftonline.com/ | Further information: |
| tapio Additional tapio services | https:// *.tapio.one/ | Further information: |
| HOMAG sh-core API | https://smarthardware-core.homag.cloud | API for the firmware update |
| HOMAG Storage | https://dfshcoreprdeu01sa.blob.core.windows.net/* | Data storage of the firmware update files |
Time synchronisation | time.windos.com | The URLs are used as an fallback, if no valid NTP server was received over DHCP or was set manually via the local diagnostic page. |