In order to use the HOOC solution, communication to *.hooc.me domains must be possible.
Yes, as long as the configuration mode is enabled.
The network interface could not obtain an IP address from the remote network.
Some security software may prevent the HOOC app from connecting to the HOOC cloud. This is because these softwares masquerade themselves as the HOOC cloud. The HOOC solution’s security features ensure that the HOOC app and HOOC gateways can only connect to the genuine HOOC cloud.
The timeout setting is 250ms by default. When using mobile devices, the latency of the connection may exceed this value. Therefore it is recommended to increase the timeout (under SOCKET Setup -> Channel Settings) to 3000ms.
There are AppIds for iOS and Android.
App | AppId for iOS devices | AppId für Android devices |
---|---|---|
CUBEVISION 2 | cubevision:// | de.babtec.cvmobile2.app |
Loxone | loxone:// | com.loxone.kerberos |
Gira Homeserver | girahs:// | de.gira.homeserver.android |
Feller Homeserver | girahs:// | de.gira.homeserver.android.feller |
Telenot | buildsec:// | com.TelenotElectronic.comvisMCa |
The network adapter used by the HOOC Client App has an automatic interface metric set as default. If a connection is established to a remote site using HOOC Secure Remote Access Service, the routing table is adjusted after the connection has been made. The interface metric can be set directly at the network adapter.
Using the elements Automatic metrics and Interface metrics, the routing can now be adjusted as follows:
Automatic Metrics | Interface Metrics | Data Traffic |
---|---|---|
- | All traffic is sent through the VPN tunnel | |
9999 | Data traffic to site via VPN tunnel, remaining data traffic locally |
Confirming all windows with OK will apply the settings made. These changes must be made before establishing a connection to a remote site.