MultiTech Conduit
Version 2.8.43
Supported hardware
For each LRR version, the combination of hardware model and applicable FPGA/ firmware version is mentioned, with restrictions if applicable.
The list of features and fixed issues is not broken down per hardware model. Therefore, some features/fixes may apply to only some hardware models that support the required characteristics (like GPS support for instance).
| Hardware Model | FPGA | Firmware | HAL | Comment |
|---|---|---|---|---|
| Conduit Access Point | 31 | 5.3.31 | 4.1.3_1+ patch #2 |
|
| Blue Conduit V1.5 (SPI) | 31/35 | 5.3.31 | 4.1.3_1+ patch #2 |
|
| Blue Conduit Refresh V1.5 (with GPS) | 31/35 | 5.3.31 | 4.1.3_1+ patch #2 |
|
| Conduit Outdoor IP67 V1.5 (8 and 16 channels) | 31/35 | 5.3.31 | 4.1.3_1+ patch #2 |
|
| Conduit Outdoor IP67 V2.1 | 61 | 5.3.31 | 5.1.0 + patch #1 |
|
| Conduit Outdoor IP67 200 series | 31 | 5.3.31 | 4.1.3_1+ patch #2 |
|
Information about HAL patches:
-
#1: wrong GPS timestamp calculated:
- Issue fixed into Semtech HAL (patch of HAL source).
- Patch shared with Semtech and agreed, not yet included in a new Semtech HAL release
-
#2: do not reset FPGA when connecting (caused downlink to be stopped after a spectral scan analysis)
- Known issue at Semtech, not fixed in an official release,
- Fix integrated in Actility delivery
Version 4.1.3_1 is patched over 4.1.3 to allow FPGA v35.
New features
-
Support TLS as a new communication security protocol (RDTP-17091, RDTP-5248): TLS (Transport Layer Security) has been added along with IPSec (Internet Protocol Security). By default, TLS is used to encrypt every message going from the LRR to the ThingPark platform. IPSec can still be used and configured using the Suplog. To learn more, see Activating a secure connection via IPSec or TLS.
-
Reporting of cellular statistics (RDTP-2420): showing the 3G/4G operator, RSSI, SINR and other RF stats related to the cellular backhaul interface.
-
Possibility to customize the SUPPORT password from SUPLOG (RDTP-15143): For enhanced security, the default SUPPORT password may be changed by the user from SUPLOG console, under Identifiers > Set Actility support tool password.
-
Enhanced filtering of non-LoRaWAN uplink packets (RDTP-17897): Optimized LRR filtering of uplink packets to discard non-LoRaWAN frames.
-
Allow configuring ICMP destinations in SUPLOG (RDTP-17415): Make it possible to customize the ICMP destinations in SUPLOG to comply with specific deployment use cases where ICMP protocol is not authorized on ThingPark's server side.
-
Introduction of embedded virtual device probe: This feature provides insight into the RF quality of the network using an emulated device in the LRR to send messages over the LRR antenna, and then analyze the quality of the received uplink packet by other surrounding LRRs.
-
Introduction of new managers: Centralmgr is now centralizing all information from the other managers: gwmgr, failovermgr, restoremgr, rollbackmgr, lrrmgr, pkimgr.
Other improvements
-
IPsec configuration improvements
-
Reboot as an environment variable
-
NTP configuration improvement
-
Reverse SSH improvements when losing connection to the gateway
-
Improvements on SUPLOG
-
Improvements on failover
-
Improvement when cleaning certificates
-
Improvement of log rotation
-
Improvement of backup/restore
-
Improvement of sysconfiglrr
Bug fixes
-
PT-2073: ntpq delivered under /home/actility/system/bin/ is failing with error
-
PT-1772: after configuring IP failover to ppp0-only, the gateway failed to establish vpn tunnels with LRC.
-
PT-2078: Auto reboot counter incremented twice for a single reboot when gateway lost connection to LRC.
-
PT-2495: Force cellular MTU to 1358; force MSS to 1254 for IPSec.
Known issues
-
PT-1582: metrics can show a constant high CPU usage. No impact on LRR capabilities detected so far.
-
PT-2628: Restoration failed to restore the security mode.
-
PT-2630: LRR upgrade: checkpki restarted with incorrect security mode after upgrade.
-
PT-2683: In TLS security mode, when the BS certificate is regenerated, either upon automatic renewal or manually regenerated by the user, some functions may be disturbed such as RF region update and RF scan. The workaround is to manually reboot the BS after it has downloaded the new certificate.