In order to update or to use the online licensing mechanisms, ETS builds up a connection either with a specific KNX server directly or indirectly via a proxy. A specific ETS proxy does however not exist, it uses a proxy of the operating system instead. A proxy with user login is supported if its user is identical to the PC user. In this case, the login for the proxy is passed on to the operating system, given there is internet access.
ETS6: Firewall Requirements - No deep inspection firewall is allowed (no traffic interception is allowed).
IoT Requirements - When standard Windows 11 users run ETS6N.exe or ETS6C.exe, they receive notifications to accept the Windows Defender Dialog. If users choose not to accept the Windows Defender dialog, manual creation of firewall rules is recommended. Four necessary firewall rules need to be created for both TCP and UDP protocols for ETS6N.exe and ETS6C.exe.
| Functionality | URL | Port |
|---|---|---|
| ETS Updates | https://update.knx.org | 443 |
| ETS App Updates | https://api.knx.org | 80, 443 |
| ETS Cloud Licensing | https://openapi.knx.org | 443 |
| ETS Administrative Data Updates | http://update.knx.org | 80 |
| ETS Online Catalog Updates | http://onlinecatalog.knx.org | 80 |
| ETS Product Information & News | 80 |
**: according to the ETS language, replace ** by the language code (See here)
When cloud licensing is used, ETS6 sends user information to the license server so that it can authenticate the user and provide licenses. ETS6 sends this information (login info, computer and software info) in an encrypted way so the server can send back the right tokens to ETS to access licenses. The license server also stores the IP address of the ETS user who requested the license for a year for security reasons.