Important Information
Starting with this release, a License Key is required for operating Connectivity Suite. Each CS instance running software v3.5 or later requires its own License Key.
Obtaining a License:
- A License Key, delivered in form of a file, is issued and distributed by NetModule (sales@netmodule.com) or through authorized distribution partners.
- Get your license file(s) through your regular commercial channel and have it ready when starting the installation / update of Connectivity Suite. Provide the FQDN of the same when ordering.
- Licenses are valid for a subscription period of 12 months. NetModule will notify its customers and partners in advance and early enough for the renewal to be executed in time.
Operation:
- As part of the installation process the user is prompted to upload a valid License in the WEB UI under “Settings/Licenses”
- The License status providing the below parameters, is visible in the WEB UI and may be queried through API as well:
- License status
- Subscription period; Start- and end-date
- Number of devices included vs. in connected to Connectivity Suite
Any questions related to this topic, please address them by completing the following Request Form.
Features added
- Reverse Proxy Records
- Accessing devices and child devices with a standard web browser, without the need of an OpenVPN connection.
- Configuring reverse proxy records for accessing devices and child devices using https
- Utilization of sub-domain names to access devices and child devices securely via https
- Setting target port(s) for devices and child devices
- Debian 12 Support
- Connectivity Suite is now supporting Debian 12 Linux OS
Improvements
- API Swagger Documentation
- The documentation for the Swagger API Interface has been improved. Each API Call now has a detailed description of its functionality and parameter(s).
- Improved progress information on Jobs
- A detailed task-level view is now available for Jobs, which allows for more effective monitoring of the job progress.
- Optional Device properties in Device List
- The Device List now provides the option to include Device properties such as temperature, storage capacity, or module firmware version as columns.
- Reduced load on backend OpenVPN servers
- The communication between the API and devices no longer passes through the backend OpenVPN server, leading to quicker deployment processes.
Bugfixes
Various Bugs have been fixed in this release. The most relevant for users are listed below (list is non exhaustive).
- CS-3532 – Valid Network Pools Available: When creating new Networks, unavailable subnets are now greyed out. This helps to prevent IP Address conflicts.
- CS-3785 - Tech Support File: Generating a Tech support File, caused a out of memory error message in some cases. This has been fixed now and the error no longer occurs.
- CS-3886 – Core Address Block Validation; Previously, the Core Address Block (the /20 block) could accept an invalid IP address and netmask pair. This made the CS seem functional, but the API was unable to connect to the routers through the provisioning network. With this version the IP Address and Netmask is being validated.
- CS-3892 – MAC Address Info: The MAC address, which is visible in the Hardware Tile as part of the device details, was improved to reflect the first MAC address of the device`s LAN ports.
- CS-3903 – Connection issues between OpenVPN and API: A bug has been identified in a third-party library related to Ed25519 private keys, specifically when private keys with leading zeros are utilized for SSH communication between the API and the OpenVPN Servers. This issue has resulted in various complications, such as moving devices between networks.
- CS-3922 – Mitigate Terrapin Attack: OpenSSH version was updated to 9.3_p2-r1 in the OpenVPN Server Docker images to address and mitigate the potential Terrapin attack.
For a more detailed description of the Connectivity Suite changes, see the release notes.
If you have any further questions, simply contact our technical support.If you are looking for more general information about the Connectivity Suite, please visit our Connectivity Suite website.