ESF 6.2.1 - Release

Eurotech Everyware Software Framework ESF 6.2.1 (Eclipse Kura - 4.1.3) - December 2021

Description:
ESF 6.2.1 is a service release to address various CVEs in framework dependencies.
In particular, the release addressed CVE-2021-44228, CVE-2021-45046 and CVE-2021-45105
by updating Log4J to version 2.17.0. Further platform updates are for Google Protobuf to 3.8.0
and Jetty to version 9.4.41.

New and Noteworthy:

  • Target Platform Updates
    • log4j.version=2.17.0
    • slf4j.api.version=1.7.32
    • com.google.protobuf.version=3.8.0
    • org.eclipse.jetty.continuation.version=9.4.41.v20210516
    • org.eclipse.jetty.http.version=9.4.41.v20210516
    • org.eclipse.jetty.io.version=9.4.41.v20210516
    • org.eclipse.jetty.security.version=9.4.41.v20210516
    • org.eclipse.jetty.server.version=9.4.41.v20210516
    • org.eclipse.jetty.servlet.version=9.4.41.v20210516
    • org.eclipse.jetty.util.version=9.4.41.v20210516
    • org.eclipse.jetty.util.ajax.version=9.4.41.v20210516

Compatibility:

  • ESF v6.2.1 does not introduce API breakage with previous releases.

Target Environments:

  • ESF supports the following Devices and Everyware Linux (EL) versions:
    • ReliaGATE 10-11;
      • EL 20.2.0
    • ReliaGATE 10-12;
      • EL 25.3.0
      • EL 26.0.0
      • EL 27.0.0
    • ReliaGATE 10-20;
      • EL 10.0.0
      • EL 12.1.0
      • EL 27.0.0
    • ReliaGATE 20-25;
      • EL 22.0.0
      • EL 23.0.0
    • BoltGATE 20-25;
      • EL 21.4.0
    • DynaGATE 10-06;
      • EL 21.1.0
    • ReliaGATE 10-14;
      • EL 27.0.1
    • BoltGATE 20-31;
      • EL 20.0.0
    • DynaGATE 20-30;
      • EL 20.0.0
    • Raspberry Pi 2/3 with Raspberry Pi OS Buster (32 bits);
  • ESF is also available as a pre-built Docker container based on:
    • Centos 8
    • RHEL 8

Bug Fixes (ESF):

  • Changelog:
    • a8a4424ea - Modified pre-installs to not remove log4j.xml file (#1541) (marcellorinaldo)
    • 6c9f5a73b - Updated 6.2.1 development environment and archetype (#1537) (nicolatimeus)
    • 7bf63af2a - Prepared for 6.2.1 release. (#1534) (Matteo Maiero)
    • e80c625a0 - Updated jenkinsfile (Maiero)
    • 2bee6e800 - Updated jenkinsfile with obfuscator references (Maiero)
    • c2d37075e - Fixed obfuscation issue with new log4j-core (Maiero)
    • b5f49aa9e - Updated jenkinsfile to ease equinox download (Maiero)
    • a793e31bc - Initial Jenkinsfile (Maiero)
    • 1d4adb821 - Fixed protobuf dependency broken after Kura upgrade. (Maiero)
    • d6f013bb7 - Upticked versions for 6.2.1-SNAPSHOT (#1193) (Matteo Maiero)

Bug Fixes (Kura):

  • Changelog:
    • 58c12f2ce8 - Updated log4j to 2.17.0 (Maiero)
    • ecc46300ee - Merge pull request #3721 from eclipse/backport-jetty-version-hide (nicolatimeus)
    • 59f5b176d3 - Added missing bundle to 4.1.3 dev-env emulator (#3720) (nicolatimeus)
    • 34aa5a430a - Backport of #3459 to align with Kura 5.0.0 changes (Maiero)
    • f701f92f12 - Updated version from 4.1.3-SNAPSHOT to 4.1.3 (Maiero)
    • a354b2f4d1 - Updated log4j2 to 2.16.0 (#3713) (#3714) (github-actions[bot])
    • a7ddd39f58 - Updated Jetty to 9.4.41 (Maiero)
    • 8806e08069 - Fixed versions (Maiero)
    • 41e46e3b07 - Updated Jetty to v.9.4.35. (Maiero)
    • e6dda7ebb4 - Updated protobuf to version 3.8.0. (Maiero)
    • f73988467e - Updating log4j version to 2.15.0. (Maiero)
    • 5c83dbe733 - Upticked versions to 4.1.3-SNAPSHOT (#3127) (Matteo Maiero)

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • #872: Provisioning Service: provisioned flag not reset if provisioning is re-enabled
  • #786: Connection Failed on Snapshot Rollback
  • #624: [Serial] RXTX fails to set 38400 bauds
  • #602: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #509: [ESF 5.2.0 QA] Check message verification failed with diagnostics ping
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles
  • Trying to connect to a WI-FI network with a special character in the SSID results in an error.

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE also tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • #2414: Rock 960: cannot get client id
  • #2038: [Kura 3.2.0 QA] Package uninstallation log
  • #2013: Unsaved changes dialog triggers incorrectly
  • #1993: Search Domains Are Not Supported
  • #1932: SystemAdminService.getUptime() returns SystemAdminService#UNKNOWN on MacOS when locale is not English
  • #1663: Authentication Issue with Deploy V2
  • #1572: serial modbus has errors on some hardware
  • #1533: MqttDataTransport client-id illegal character
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1195: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Eurotech Everyware Software Framework ESF 6.2.0 (Eclipse Kura - 4.1.2) - October 2020

Description:
ESF 6.2.0 is a minor release that introduces the new ESF Log Analytics feature and support for new Eurotech gateways.
It adds support for the DynaGATE 10-06, the ReliaGATE 10-14, the BoltGATE 20-31 and the DynaGATE 20-30.
ESF 6.2.0 introduces the new Log Analytics feature that is responsible to manage device logs and publish
the most significant ones to the selected cloud platforms. The feature is available only for Systemd systems and
is disabled by default.

New and Noteworthy:

  • Features and Enhancements

    • Introduced the new Log Analytics feature
    • Added support for the DynaGATE 10-06
    • Added support for the ReliaGATE 10-14
    • Added support for the BoltGATE 20-31
    • Added support for the DynaGATE 20-30
    • Updated the initial configuration for the ReliaGATE 10-12 RS485 bundle
    • Fixed the Development Environment execution with Mac OS X 10.15
    • Enhanced the modem support with Ublox LARA R2
    • Improved and made uniform the Web UI Response Headers
    • Updated the diagnostics bundle adding the capability to report the GPS position in alert and diagnostics messages
    • The clock service now allows to select the RTC to be used
    • New eth_journalctl.sh executable available as /usr/bin/eth_journalctl. When the ESF Log Analytics feature is enabled,
      this script will allow to export the system journal content to a file, for further analysis.
  • Bug fixes and cleanups

    • Fixed issue with possible stale threads left by Paho during reconnections
    • Fixed capitalization of cloud services, publishers and subscribers in the Cloud Connections view
    • Fixed issue with target selection in Web UI
    • Fixed issue with Assets cloudlet where a read for all channels could lead to an empty value
    • Fixed issue with Bluetooth flags capitalization
    • Fixed issue with AT context command for Quectel modem
    • VPN tun0 interface is now bound to a specific set of addresses.
    • Fixed inability to start a vpn connection when the vpn configuration is set during provisioning to EC
    • Disabled system time services when installing ESF

Compatibility:

  • ESF v6.2.0 does not introduce API breakage with previous releases.
  • The Command Service is now disabled by default. To use it, the user needs to opt-in to this feature, enabling the service
    from configuration.
  • Since version 6.1.2, ESF introduces H2DB v.1.4.199 that requires to delete/upgrade the existing persisted database to be
    compatible with this new version. Please refer to http://www.h2database.com/html/tutorial.html#upgrade_backup_restore
  • Since version 6.1.2, ESF uses a different set of signing certificates due to the expiration of the ones used in previous version.
    Please check the ESF documentation to verify if the usage of the Policy Updater Bundle is necessary before considering an update from previous version.

Target Environments:

  • ESF supports the following Devices and Everyware Linux (EL) versions:
    • ReliaGATE 10-11;
      • EL 20.2.0
    • ReliaGATE 10-12;
      • EL 25.3.0
      • EL 26.0.0
      • EL 27.0.0
    • ReliaGATE 10-20;
      • EL 10.0.0
      • EL 12.1.0
      • EL 27.0.0
    • ReliaGATE 20-25;
      • EL 22.0.0
      • EL 23.0.0
    • BoltGATE 20-25;
      • EL 21.4.0
    • DynaGATE 10-06;
      • EL 21.1.0
    • ReliaGATE 10-14;
      • EL 27.0.1
    • BoltGATE 20-31;
      • EL 20.0.0
    • DynaGATE 20-30;
      • EL 20.0.0
    • Raspberry Pi 2;
    • Raspberry Pi 3;
  • ESF is also available as a pre-built Docker container based on:
    • Centos 8
    • RHEL 8

Bug Fixes (ESF):

  • Fixed github issues:
    • #1162: VPN service Password cast failure
    • #1145: Add references to logs p2 in ESF p2
    • #1113: Add GPS position to diagnostics bundle messages
    • #1110: ESF uninstaller doesn't remove all folders
    • #1088: Update docker images to support log Feature - Backport
    • #1050: Check why publisher lowercase in “Cloud Connections”
    • #1036: [Reliagate 10-14] Add 6.1.3 nn profile
    • #1035: [Dynagate 10-06] Add 6.1.3 nn profile
    • #1034: Possible issue with Paho stale threads in WS
    • #1025: Review UI security response headers
    • #992: Parsing failure after NET-ETH0-007
    • #979: RS485 bundle for 10-12: change initial config
    • #977: ESF 6.1.3 Support for new platforms
    • #936: Create new Systemd profile for 10-14
    • #932: ESF v6.1.0 user workspace on OS X 10.15
    • #905: RTC awareness
    • #873: RPM: Disable time synchronization Systemd services
    • 820: Add support for DYGATE 20-30

  • Merged no issue-related Pull Requests:
    • #1147: Added log publisher - backport
    • #1143: Set syslogIdentifier from external variable - backport
    • #1134: Backport use rhel8 for esf-rhel image
    • #1129: Update configuration for firewall
    • #1123: Backport hwclock config
    • #1101: Added eth_journalctl.sh to distribution
    • #1063: Fixed recover_default_config.init for RPi profiles
    • #1051: Added log management to 6.1.3

Bug Fixes (Kura):

  • Fixed github issues:
    • #3123: Priority description is wrong in CloudPublisher
    • #3113: The iBeacon Scanner sometimes fails to detect beacons
    • #3109: Quectel modem fixed to PDP context 1
    • #3107: The upload of zip archive with folders fails
    • #3104: XSRF error when resetting a configuration with target filters
    • #3088: Encoding of passwords differ between graph snapshots and full snapshots
    • #3071: Stale threads related to Paho
    • #3068: Review/Update servlet response headers
    • #3044: Incorrect Asset status report from cloud call
    • #3022: DnsServerService doesn't work on Armbian (Ubuntu 20.04.1 LTS) anymore
    • #3017: Issue while accessing properties in gatt characterstics
    • #2992: Quectel EG-25 context command is wrong
    • #2983: UI Target selection is not working in all cases
  • Merged no issue-related Pull Requests:
    • #3102: Added RTC device to clock service
    • #3094: Rollback of the CSP feature as causes problems to images in bundles.
    • #3086: Backport - Adding support for Telefonica modem IK41VE (#3083)
    • #3078: Capitalize cloudservice, publisher and subscriber names - Backport
    • #2991: Backport of #2957 to release-4.1.0

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • #872: Provisioning Service: provisioned flag not reset if provisioning is re-enabled
  • #786: Connection Failed on Snapshot Rollback
  • #624: [Serial] RXTX fails to set 38400 bauds
  • #602: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #509: [ESF 5.2.0 QA] Check message verification failed with diagnostics ping
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE also tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • #2414: Rock 960: cannot get client id
  • #2038: [Kura 3.2.0 QA] Package uninstallation log
  • #2013: Unsaved changes dialog triggers incorrectly
  • #1993: Search Domains Are Not Supported
  • #1932: SystemAdminService.getUptime() returns SystemAdminService#UNKNOWN on MacOS when locale is not English
  • #1663: Authentication Issue with Deploy V2
  • #1572: serial modbus has errors on some hardware
  • #1533: MqttDataTransport client-id illegal character
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1195: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Eurotech Everyware Software Framework ESF 6.1.2 (Eclipse Kura - 4.1.1) - May 2020

Description:
ESF 6.1.2 is a service release to address various discovered bugs and functional issues.
It adds support for ReliaGATE 10-20 systems with EL 27.0.0 (systemd support).

New and Noteworthy:

  • Features and Enhancements

    • Added modem support for Huawei MS2372, Zte ME3630, SimTech SIM7000 LTE NB-IOT, Quectel EG25
    • Added support for 10-20 Systemd EL 27.0.0 system
    • Updated the suggested production security policy supporting a more flexible approach for trust with certificate
      per certificate revocations
  • Target Platform Updates

    • Jetty 9.4.19.v20190610
    • H2DB 1.4.199
    • Paho 1.2.1.k2
  • Bug fixes and cleanups

    • Fixed modem reset issue when the value is configured to 0 (no reset)
    • Fixed issue with multiple cloud connections
    • Fixed issue with parsing of ip route command
    • Fixed issue where assets with only write channels still can call driver.read() method
    • Fixed issue with token bucket where a change of system type can inpact with the token bucket functionality
    • Fixed issue where a change in system tyme could impact the Wires Timer
    • Fixed issue with Asset channel restore functionality
    • Fixed issue with DEPLOY-V2 failure message publishing
    • Fixed issue with Paho overriding SSL settings
    • TLS v1.2 is now default in all the platforms
    • Fixed issue in CanConnection service with multiple can interfaces
    • Fixed issue with modem switching from data mode to command mode
    • Fixed issues with modem reset
    • Fixed issue where an incorrect configuration of the LE910NA-V2 with Verizon Wireless could cause a reset loop

Compatibility:

  • ESF v6.1.2 does not introduce API breakage with previous releases.
  • The Command Service is now disabled by default. To use it, the user needs to opt-in to this feature, enabling the service
    from configuration.
  • ESF 6.1.2 introduces H2DB v.1.4.199 that requires to delete/upgrade the existing persisted database to be
    compatible with this new version. Please refer to http://www.h2database.com/html/tutorial.html#upgrade_backup_restore
  • ESF v6.1.2 uses a different set of signing certificates due to the expiration of the ones used in previous version.
    Please check the ESF documentation to verify if the usage of the Policy Updater Bundle is necessary before considering an update from previous version.

Target Environments:

  • ESF supports the following Devices and Everyware Linux (EL) versions:
    • ReliaGATE 10-11;
      • EL 20.2.0
    • ReliaGATE 10-12;
      • EL 25.3.0
      • EL 26.0.0
      • EL 27.0.0
    • ReliaGATE 10-20;
      • EL 10.0.0
      • EL 12.1.0
      • EL 27.0.0
    • ReliaGATE 20-25;
      • EL 22.0.0
      • EL 23.0.0
    • BoltGATE 20-25;
      • EL 21.4.0
    • Raspberry Pi 2;
    • Raspberry Pi 3;
  • ESF is also available as a pre-built Docker container based on:
    • Centos 7
    • RHEL 7

Bug Fixes (ESF):

  • Fixed github issues:
    • #970: Update ESF policy to check the intermediate
    • #963: [LE910NA-V2] Entering wrong dial string and APN for Verizon Wireless causes a reset loop
    • #959: ipv6 script is case sensitive
    • #946: LE910C1-EU context 2 already active at power on prevents pppd from establishing the link
    • #943: ReliaGATE 10-20 lsusb fails on disabling modem causing a tight loop and large logs
    • #935: Create New Systemd profile for 10-20 EL13/27
    • #928: DataService never tries to connect to EC5 when another DataService is connecting to another broker
    • #927: H2DB in persistent mode blocked with 2 publishers
    • #910: Frame counter defined as short in Lorawan library
    • 887: Systemd routine cleans ESF files in tmp

      *Â #879: Systemd undefined bootup of firewall.service and network.service
    • 877: Systemd firewall service exits with status 1

  • Merged no issue-related Pull Requests:
    • #973: Modified the build process to support new certificates and separate keystores.
    • #955: Gateway modem driver isOn log
    • #951: Backport of #950 to release-6.1.0
    • #942: Fixed DNS pass through for DNS in wireless interfaces.
    • #861: Updated obfuscation library
    • #831: Fixed snapshot 0 rollback by updating the snapshot0 file.

Bug Fixes (Kura):

  • Fixed github issues:
    • #2831: ModemMonitorServiceImpl should use monotonic clock
    • #2828: Improve modem help section
    • #2827: Entering wrong dial string and APN can cause a reset loop
    • #2825: Kura 4.1.x SupportedUsbModems isAttached method can fail
    • #2822: CommConnectionImpl constructor does not close the serial port on failure
    • #2820: Modem reset can lead to SIM card not ready
    • #2811: CanConnection service with multiple can interfaces
    • #2809: Unescaped loop on modem reset failure
    • #2800: Switching from data mode to command mode does not work in pppd chat script
    • #2793: Paho 1.2.1 overrides Kura SSL configuration
    • #2759: [DEPLOY-V2] Failure status reported by a verifier script is not published
    • #2679: One of two CloudConnections sometimes fails to connect and never tries to reconnect
    • #2639: Asset configuration reseted after uploading new channels
    • #2626: Asset with only write channels still calls driver.read() method
    • #2605: Wires Timer stop ticking if system time is set in the past
    • #2581: [DataService] Use System.nanoTime for token bucket
    • #2580: Setting modem reset timeout to 0 causes the modem to reset indefinitely
    • #2540: Default gateway is not correctly parsed
    • #2437: Add support for Huawei modem MS2372
  • Merged no issue-related Pull Requests:
    • #2805: Added policies to iptables
    • #2804: Fixed DB bundle reference in dev-env.
    • #2665: Added support for Quectel EG25
    • #2622: Support for SimTech SIM7000 LTE NB-IOT modem
    • #2611: Zte ME3630 LTE modem support
    • #2558: udhcpc pid file parameter fix
    • #2511: Updating jetty to 9.4.19.v20190610
    • #2484: Fixed H2db invocation in config.ini file.
    • #2466: Updated H2DB to version 1.4.199
    • #2404: HostapdManager: use absolute path to pid file instead of relative

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • #786: Connection Failed on Snapshot Rollback
  • #701: [ESF 6.0.0] Failed dependencies against EL 21.0.0 for BoltGATE-20-25
  • #624: [Serial] RXTX fails to set 38400 bauds
  • #602: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #510: [ESF 5.2.0 QA] .restoreDefaultConfig.sh can produce invalid /etc/network/interfaces
  • #509: [ESF 5.2.0 QA] Check message verification failed with diagnostics ping
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE also tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • #2414: Rock 960: cannot get client id
  • #2038: [Kura 3.2.0 QA] Package uninstallation log
  • #2013: Unsaved changes dialog triggers incorrectly
  • #1993: Search Domains Are Not Supported
  • #1932: SystemAdminService.getUptime() returns SystemAdminService#UNKNOWN on MacOS when locale is not English
  • #1663: Authentication Issue with Deploy V2
  • #1572: serial modbus has errors on some hardware
  • #1533: MqttDataTransport client-id illegal character
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1195: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Eurotech Everyware Software Framework ESF 6.1.1 (Eclipse Kura - 4.1.0) - November 2019

Description:
ESF 6.1.1 is a maintenance release dedicated to support the ReliaGATE 20-25 with EL 23.0.0.

New and Noteworthy:

  • Features and Enhancements
    • ReliaGATE 20-25 EL 23.0.0 support.
    • Updated firewall configs for all gateways.

Eurotech Everyware Software Framework ESF 6.1.0 (Eclipse Kura - 4.1.0) - April 2019

Description:
ESF 6.1.0 is a minor release dedicated to introduce several new features and continue the process of overall usability improvement.
It also carries an overall code quality improvement.
The ESF build now produces a P2 repository that can simplify the overall process of creation for a new bundle.
ESF 6.1.0 is now compatible with Zulu Embedded VM

New and Noteworthy:

  • APIs

    • New APIs for KuraBirthPayload, KuraDeviceProfile, KuraDisconnectPayload
  • Features and Enhancements

    • Enhanced the JSON Service with JSON Message marshalling/unmarshalling
    • Added timestamp to Lifecycle Messages
    • Added support for the ESF P2 repository and add-on project archetype
    • Alert messages are now sent by ESF with QoS 1
    • Added support in Modbus Driver to single registers/coils write functions
    • Defined an upgrade dp. Signed by the customer, it has to be applied to ESF 6.0.0 to support the upgrade to ESF 6.1.0 and support the new Zulu VM
    • Switched to log4j regular File Appender instead of previous RandomAccessFileAppender
  • Target Platform Updates

    • Google Guava 25.0-jre
    • Eclipse Milo 0.2.4
    • Apache Fileupload 1.3.3
    • RedHat A-MQ7 2.6.3.redhat-00020
    • Eclipse Paho 1.2.1
  • Bug fixes and cleanups

    • Fixed unnecessary escaping in Drivers and Assets UI
    • Fixed issue where asset failure messages were not displayed
    • Fixed a bug where the user could not set cellular attempts option to 0
    • Fixed incompatibility with systems without iwlist
    • Solved a possible OSGi framework refresh when a dp is uninstalled or reinstalled
    • DEPLOY-V2 cloudlet fixes for GET calls
    • Fixed Vpn Client to support passwords with special characters
    • Monit is not anymore used in systemd based platforms

Deprecated APIs:

  • Deprecated old Bluetooth APIs not based on tinyB

Security Fixes:

  • CVE-2016-1000031
  • CVE-2018-10237
  • CVE-2019-10242
  • CVE-2019-10243
  • CVE-2019-10244

Compatibility:

  • ESF v6.1.0 does not introduce API breakage with previous releases.
  • The Command Service is now disabled by default. To use it, the user needs to opt-in to this feature, enabling the service
    from configuration.

Target Environments:

  • ESF supports the following Devices and Everyware Linux (EL) versions:
    • ReliaGATE 10-11;
      • EL 20.1.0
      • EL 20.2.0
    • ReliaGATE 10-12;
      • EL 25.3.0
      • EL 26.0.0
    • ReliaGATE 10-20;
      • EL 10.0.0
      • EL 12.1.0
    • ReliaGATE 20-25;
      • EL 21.0.0
      • EL 22.0.0
        • Support for Bluetooth 2.1 is not available since Everyware Linux version 22.0.0
    • BoltGATE 20-25;
      • EL 21.4.0
    • Raspberry Pi 2;
    • Raspberry Pi 3;
  • ESF is also available as a pre-built Docker container based on:
    • Centos 7
    • RHEL 7

Bug Fixes (ESF):

  • Fixed github issues:
    • #802: [10-12] Add serial port configurator
    • #797: NullPointer Exception updating broker config
    • #793: [6.1.0 QA] Exception activating GPS in reliacell without enabling the modem
    • #789: [10-12-EL26] iwlist is missing
    • #783: [DiagnosticService] RTT cloud connection status check logic is unreliable
    • #779: [Build] Create ESF p2 repo and addon project archetype
    • #776: Alerts should be published with QoS 1
    • #775: Too Many Inflight Messages (Docker)
    • #774: RPM Java VM Dependency
    • #773: [Modbus Driver] Add support for write single registers/coils functions
    • 770: Define upgrade dp

      *Â #756: [10-05] NPE is thrown when the dns servers are not configured
    • #755: VpnClient offending password
    • #742: [Log4j2] RandomAccessFileAppender does not work well with logrotate
    • #720: [BoltGATE 20-25] ESF removes CAN interfaces configuration during installation
    • #719: LoraDriver random object created every time a json string is created
    • #708: [Reliagate 10-20 EL12] Unsupported parameter in /etc/network/interfaces
    • #707: [6.0.0] Monit configuration for Systemd distributions
    • #706: [6.0.0] OpenVPN client disconnected on ESF stop
    • #705: Pending issues in pc2 bundle
    • #688: The ESF logger shouldn't rotate the log files
    • #675: [ESF 6.0.0 QA] [BoltGate 20-25] Some serial ports are missing
  • Merged no issue-related Pull Requests:
    • #815: Added serial port configurator for 10 12 EL26
    • #812: Completed archetype target definition for 6.1.0 release
    • #803: Added 10-12-EL26 profiles
    • #798: Added serial port configurator for BG2025
    • #796: Reverted change to RS485 field names
    • #785: Added symlink to bind9 for RPi
    • #784: Fixed DiagnosticService cloud connection status detection
    • #772: Updated Artemis to 2.6.3.redhat-00020
    • #764: Removed monit from systemd systems
    • #760: Patched possible XXE exposure in xml parser
    • #759: Fixed diagnostic service lint issue
    • #752: Fixed bluetoothConnectorImpl version
    • #751: Replacement of AesCmac library in lora driver with bouncycastle library.
    • #750: Update guava to 25.0-jre
    • #749: Use ThrowablePatternConverter for exception logging
    • #748: Cleanup of dockerfile dependencies.
    • #747: Updated kura.configuration import version in windows.clock
    • #741: Fixed several sonar lint issues (again)
    • #739: Use log4j2 BasicContextSelector on some platforms
    • #738: Removed a reference to cmpn.
    • #730: Removed bluetoothd service start
    • #696: Changed startup command line removing biased locking usage
    • #692: Fix recovery and install scripts

Bug Fixes (Kura):

  • Fixed github issues:
    • #2423: [Kura QA 4.1.0] Emulator in Oomph installer
    • #2421: Artemis Server manager NullPointer exception
    • #2418: Kura does not support systems without iwlist
    • #2417: [Kura 4.1.0 QA] Asset configuration radio buttons
    • #2412: Paho issue with WS broker
    • #2407: Can't set cellular connection attempts to 0
    • #2399: Update Paho to latest version available
    • #2389: Unnecessary escaping in Drivers and Assets data UI
    • #2388: Update Artemis to 2.6.4
    • #2382: Asset operation failure messages are not always shown
    • #2372: Add Timestamp to Lifecycle Messages
    • #2353: [ConfigurationService] Loading unencrypted snapshots discards line breaks
    • #2352: Guava CVE-2018-10237
    • #2334: The old Bluetooth APIs should be deprecated
    • #2330: BLE Beacon data assembly overflow
    • #2324: Possible OSGi framework refresh when a dp is reinstalled
    • #2313: Typos in ExamplePublisher metric name and descriptions
    • #2301: kura.data.dir unused
    • #2300: Drivers and Assets description is appended
    • #2296: The BluetoothLE example fails when the cloudPublisher is undefined
    • #2290: [Kura 4.0.0 QA] Shutdown issue when started multiple times
    • #2256: Deploy-V2 cloudlet GET status stops responding
    • #2069: Marketplace install when LAN-only
    • #362: Uninstaller leaves most of the files
  • Merged no issue-related Pull Requests:
    • #2432: Fix GPS enable when PPP is not configured
    • #2429: Fixed NPE on DhcpClientLeaseBlock
    • #2416: Fixed issues for Kura on Intel UP2 Ubuntu
    • #2395: Removed wrong if section in emulator position.
    • #2394: Fixed lint issues
    • #2387: CentOS/RPM uninstallation cleanup
    • #2386: OPCUA Driver updates
    • #2385: Solved some new lint issues.
    • #2380: Fixed lint issues
    • #2379: Moved KuraBirthPayload, KuraDeviceProfile and KuraDisconnectPayload to APIs
    • #2377: Added missing byte array conversion in optimiser library
    • #2376: Changes to expose simple message creation in corresponding JSON service
    • #2373: Added support for null notification publisher in deploy-v2.
    • #2370: Cleanup Kura folders
    • #2368: Implemented fixes for possible XXE attacks to XML parsers.
    • #2366: Changed joint shapes file to default and applied corresponding changes in wires_composer.js file.
    • #2362: Fixed regression when saving empty wire graph
    • #2358: Fixed few more lint issues.
    • #2357: Fixed notification publisher topic.
    • #2355: Fixed regression in CloudService tab ordering
    • #2349: Added check for resolv.conf symlink
    • #2348: Improved Web UI configuration loading
    • #2347: Solved some blocking lint issues
    • #2346: Changes to solve lint issues in CloudConnectionStatus.
    • #2345: Fixed lint issue
    • #2344: Solved some major lint issues in MqttDataTransport.java
    • #2343: Removed stale cmpn references.
    • #2342: Refactored console code in web2 bundle.
    • #2333: Another tentative fix to solve lint issue in file check
    • #2331: Removed osgi.cmpn api bundle.
    • #2329: Updated retrieving of system parameters on Windows
    • #2328: Solved some more lint issues
    • #2327: Changes to fix possible path injection attack in skinServlet.
    • #2325: Few lint issues fixes
    • #2309: Always use double as GainOffset return type
    • #2305: Remove the Jetty version from Server reply.
    • #2306: Removed unnecessary jaxb imports
    • #2302: Provide class to LogManager.getLogger()

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • #786: Connection Failed on Snapshot Rollback
  • #701: [ESF 6.0.0] Failed dependencies against EL 21.0.0 for BoltGATE-20-25
  • #624: [Serial] RXTX fails to set 38400 bauds
  • #602: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #510: [ESF 5.2.0 QA] .restoreDefaultConfig.sh can produce invalid /etc/network/interfaces
  • #509: [ESF 5.2.0 QA] Check message verification failed with diagnostics ping
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE also tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • #2414: Rock 960: cannot get client id
  • #2038: [Kura 3.2.0 QA] Package uninstallation log
  • #2013: Unsaved changes dialog triggers incorrectly
  • #1993: Search Domains Are Not Supported
  • #1932: SystemAdminService.getUptime() returns SystemAdminService#UNKNOWN on MacOS when locale is not English
  • #1663: Authentication Issue with Deploy V2
  • #1572: serial modbus has errors on some hardware
  • #1533: MqttDataTransport client-id illegal character
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1195: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Eurotech Everyware Software Framework ESF 6.0.0 (Eclipse Kura - 4.0.0) - November 2018

Description:
ESF 6.0.0, compatible with Java 9 and OSGi R6, introduces a new model that simplifies plugging new cloud connection implementations.
It brings up a restructuring of the networking part to make it more pluggable and expandable, new drivers and supported platforms, as well as
improvements to usability and bug fixes.
Being a major release, it also includes breaking changes and removes support for code and platforms no longer maintained by the original contributors.

New and Noteworthy:

  • APIs

    • Cloud Connections: New Cloud Connections APIs that simplify the integration of third party cloud providers, simplifying the development of
      user applications
    • Alerts: New Alerting model for special type of messages generated from the device
    • New Bluetooth LE APIs to leverage new TinyB features: updated the TinyB library and updated Kura APIs to leverage the new changes provided
      by the referenced libraryÂ
  • Features

    • Eclipse IoT WG Cloud Connection: A new Cloud Connection provider that leverages the new Cloud Connections APIs and enables Kura to connect
      with remote providers that support the new Eclipse IoT WG Namespace. E.g. this provider supports the integration with Eclipse Hono through
      the MQTT Adapter
    • Upload of Asset channels from CSV file: In the Asset view, the user can now download and upload channel descriptions as CSV files.
  • Enhancements

    • Non-blocking assets configuration updates
    • Wires Graph Blinking rate limit
    • Added fix validity, latitude and longitude hemisphere fields to GPS NMEA Position
    • Reduced CPU usage by Kura Wires
  • Refactor and Cleanup

    • Modular support of new platforms: Refactoring of framework structure to support, in a pluggable way, different operating systems and
      service managers (SysV, Systemd)
    • SSL Manager Service: Service refactoring and cleanup. By default, Kura uses for secure communications its own cacerts.ks keystore instead
      of the one provided by the Java VM. The default installation provides a cacerts.ks keystore that contains only the Eclipse leaf certificate.
      To connect to a different provider or broker, the user must install the corresponding certificate in the cacerts.ks keystore, for example
      using the Kura web UI.
    • New framework folder structure: The framework folder structure has been redesigned to simplify the user interaction.
    • Refactored Diagnostic Service: Restructured and optimised code
  • Drivers

    • New drivers available also in the Eclipse Kura Marketplace:
      • iBeacon Scanner
      • Eddystone Scanner
      • Dummy Driver
  • New Hardware Platforms and Distributions

    • AAEON AIOT-IGWS01
    • Windows for x86_64 systems
  • Target Platform Updates

    • Eclipse Equinox 3.12.50 (Oxygen)
    • Eclipse Milo 0.2.1
    • Apache Log4j2 2.8.2
    • SLF4J 1.7.25
    • RedHat A-MQ 720004-redhat-1
    • RedHat Fuse 710018-redhat-00001
    • Intel Tinyb 0.5.1
    • Eclipse Paho 1.2.0
    • GWT 1.8.2
  • Breaking Changes:

    • Removed APIs and implementation supporting HSQLDB
    • org.eclipse.kura.net package cleanup and removal of deprecated APIs
    • Removed deprecated newWireSupport as causing invocation loop
    • Removed SslManagerServiceOptions class and modified SSLManagerService APIs
    • Modified "verifySignature" method in Certificates APIs to accept, as first argument, KuraApplicationTopic instead of KuraTopic
    • Removed WireService API and references
  • Discontinued Hardware Platforms and Distributions:

    • ReliaGATE 10-05
    • ReliaGATE 20-26
  • Deprecated APIs

    • KuraTopic
    • CloudCallService
    • CloudClient
    • CloudClientListener
    • Cloudlet
    • CloudletTopic
    • CloudService
    • CloudServiceFactory

Compatibility:

  • ESF v6.0.0 introduces API breakage with previous releases.
  • Containing a folder restructuring, a cleanup of the destination filesystem is required before installing ESF
  • The Command Service is now disabled by default. To use it, the user needs to opt-in to this feature, enabling the service
    from configuration.

Target Environments:

  • ESF supports the following Devices:
    • ReliaGATE 10-11;
    • ReliaGATE 10-12;
    • ReliaGATE 10-20;
    • ReliaGATE 20-25;
      • Support for Bluetooth 2.1 is not available since Eurotech Linux version 22.0.0
    • ReliaGATE 20-26;
    • BoltGATE 20-25;
      • Support for Bluetooth 2.1 is not available
      • Only SystemD image is supported
    • BoltMAR 20-28;
      • Support for Bluetooth 2.1 is not available
    • Raspberry Pi 2;
    • Raspberry Pi 3;
  • ESF is also available as a pre-built Docker container based on:
    • Centos 7
    • RHEL 7

Bug Fixes (ESF):

  • Fixed github issues:
    • #683: [10-20] ESF slow shutdown not fixed yet...
    • #681: [20-25] /etc/release related messages in log file
    • #665: [ESF 6.0.0 QA] Issue with /etc/ppp/peers/pppX.esfsave files
    • #662: [ESF 6.0.0 QA] Diagnostic Service issues
    • #661: [ESF 6.0.0 QA] [Reliagate 10-20 EL11] Stopping ESF on system shutdown takes some time
    • #659: [PCN] The pcn2 bundle continuously reports errors on log
    • #655: [ESF 6.0.0 QA] Disable dnmasq.service in EL 21.0.0 on BoltGATE 20-25
    • #654: [ESF 6.0.0 QA] Updated startup scripts for framework change
    • #653: [10-12] Firewall configuration for wlan1
    • #651: User workspace name
    • #645: [ESF 6.0.0 QA] Bind configuration file mess in the ReliaGATE 10-12 with EL 25.3.0
    • #643: [ESF 6.0.0 QA] ReliaCELL gets assigned ppp1 on the ReliaGATE 20-25
    • #642: [VPN] Prepare to add support for OpenVPN 2.4
    • #641: [Platform] End of support for ReliaGATE 10-05
    • #636: Bind exits due to permission denied on /var/log/named.log
    • #631: com.eurotech.framework.linux.usb.x86_64 points to libudev.so.1 instead of so.0
    • #628: Add code to ESF installer to disable network-manager
    • #626: Update A-MQ 7
    • #625: Update Fuse
    • #622: Fixed rpm generation for 10-11s
    • #621: rpm installer failing on a 10-11 because of /opt dependency
    • #618: [Cellular] Support PDP authentication for Telit LE910-EU1 and LE910-V2 EU (and possibly NA versions)
    • #613: ESF docker RHEL build is not working
    • #608: [Security] Remote command injection via Socat
    • #600: [Bootstrap] Why OSGi is not started by the Equinox launcher?
    • #592: Software updates: how to manage remote patches?
    • #589: [RXTX] Opening a serial port that no longer exists causes the JVM to exit
    • #577: VpnClient with multiple CloudServices uses wrong account name
    • #569: [Security Manager] Wrong and Annoying Self-Consistency Check
    • #564: RPM installer should be a true RPM
    • #561: [ReliaIO] Update to support multiple input readings
    • #560: Support for AAEON AIOT-IGWS01 industrial gateway
    • #557: The start_kura_debug_foreground.sh for the BoltGATE 20-25 is wrong
    • #552: Port property in PositionService config needs to be updated in some platforms
    • #549: Modem GPS not really disabled
    • #548: Serial port not released by the PositionService
    • #536: [Diagnostics] Wireless signal level diagnostics support at most one interface
    • #490: [10-11] The ESF installation may fail for missing zip dependency
    • #466: [PositionService] Potential Telit modem GPS serial port contention
  • Merged no issue-related Pull Requests:
    • #692: Fix recovery and install scripts
    • #691: Fix reinstall on Windows
    • #690: Change appender in log4j.xml
    • #689: Renamed 10-20-el11 profiles to 10-20-el12
    • #686: Supported multiple publishers for PCN transportation app.
    • #684: Several fixes for BoltGate 20-25 and nn profiles
    • #674: Fixes for 10-20 EL11
    • #672: Rename boltgate 20 25 systemd
    • #670: Moved wireless-tools install from optional-rpms repo to epel.
    • #668: Fix for AIOT-IGWS01 installer
    • #660: Add Kura test dependencies to the target definition and user workspace
    • #646: Removed wrong reference to native libraries.
    • #640: Windows support
    • #633: Improved network related diagnostics
    • #632: Added dependency to eclipseiot mqtt provider.
    • #630: Update to equinox wireadmin 1.0.800
    • #617: Changes to move to the gateway_linux ant file all the linux-specific bundles.
    • #611: Fixed ESF patches
    • #606: Fixed rpm folder conflict; fixed rg10-12 arch
    • #605: Removed 20-26 profile, modified docker accordingly.
    • #604: Switched to RXTX version 2.2.100 from kura_addons
    • #603: Removed old zonemanager bundle
    • #599: Removed hsqldb and APIs.
    • #598: First changes to solve lint issues.
    • #596: First set of changes for ESF security manager.
    • #593: Fixed provisioning.
    • #582: Enh platform segregation
    • #581: Update TinyB library
    • #580: Enh cloud publishers
    • #579: Distrib build refactor; updated rpm installers
    • #578: Made Modbus Driver config update non-blocking
    • #576: Committed changes to integrate commons.csv in distribution.
    • #565: Update lora driver to make it compatible with ReliaLora
    • #559: Updated libEurotechLinuxUdev files

Bug Fixes (Kura):

  • Fixed github issues:

    • #2279: [Kura 4.0.0 QA] Service disappears from menu when reconfigured
    • #2278: Firewall, "Open port" dialog validation
    • #2272: Asset CSV upload/download issues if AD name and id differs
    • #2271: [Kura 4.0.0 QA] Adding wires components in IE/Edge
    • #2264: [Cellular] PDP Auth failed using context #1 in 4G network (Telit LE910-EU1 and LE910-V2 EU, possibly NA versions)
    • #2263: Cloud connections table refresh
    • #2262: Cloud connection PID validation
    • #2243: [Security] Possible XML External Entity (XXE) attack
    • #2239: WireAsset Configuration UI check box status can not be saved
    • #2233: Create CloudServiceFromFactory and Delete CloudServiceFromFactory cause null reference
    • #2232: Linker issue with tinyb
    • #2224: Wire Publisher can't initialize properly at kura start
    • #2219: Update Jetty to version 9.4.12
    • #2215: NPE during package installation via cloud
    • #2213: Update TinyB and Bluetooth API
    • #2210: Remove HSQL db support from code and implementation
    • #2205: [OPC-UA Driver] Authentication not working
    • #2202: [DhcpClientLeaseBlock] Failed to add a lease block due to an error parsing dhclient lease file
    • #2199: BLE iBeacon scanner configuration not synched with code
    • #2196: BLE provider logging failure
    • #2189: HTTPS redirects to HTTP
    • #2185: [Test] Cleanup tycho-surefire-plugin configurations a bit
    • #2184: [ConfigurationService] XML Marshaling Providers need to be started before
    • #2181: H2DB file fragmentation
    • #2169: H2DB file corruption
    • #2164: [Asset] Make configuration updates non-blocking
    • #2163: [Paho] WSS connection break silently after a few hours
    • #2162: [Wires] Implement rate limit in servlet for wires blinking
    • #2158: [GPS] Add missing fields in NMEA Position
    • #2153: [DEPLOY-V2] intallVerificationDir is never initialized
    • #2149: Cloud zip file upload
    • #2145: Remove libmatthew-java
    • #2143: Camel XML router service missing
    • #2138: Cloud service selection in examples
    • #2125: Impossible to upload device key pair
    • #2120: BeaconScanner example publishes with qos 2
    • #2117: Remove Windows bundles
    • #2115: Artemis 2.5.0 and dev-env
    • #2114: Review supported platforms
    • #2110: Add Dummy Driver
    • #2108: Create a new Cloud Stack for the new D2C Messaging
    • #2107: Integrate Device to Cloud (D2C) Interaction Type
    • #2102: emitAllReadChannels method doesn't handle Runtime exceptions
    • #2101: [Web UI | Driver and Assets]: Show the Asset Read Error Message
    • #2096: [NetAdmin] Issues using GPS if modem has never been enabled
    • #2091: version `GLIBCXX_3.4.20' not found
    • #2089: [NetAdmin] Some state of the logic that manages modems persists across resets
    • #2087: [NetAdmin] Race condition between NetAdmin and PositionService after modem reset
    • #2085: [NetAdmin] Fix AT escape sequence timings in TelitModem
    • #2079: Empty channel descriptor
    • #2078: Native Support for UP Development Kit
    • #2072: Weird behaviour on webUI when click on CloudServices
    • #2070: Icon not working for factory components
    • #2068: The duration of Beacon scan should be in seconds
    • #2067: DataService enable.recovery.on.connection.failure is causing a reboot systematic on first boot
    • #2065: [Web2] AlertDialog causes duplicate ids
    • #2057: Upgrade Camel version to 2.21.1
    • #2055: DefaultCloudServiceFactory manages all CloudServiceImpl instances
    • #2050: Modem monitor in Not connected state does not trigger reset
    • #2045: Add support for CloudConnectionStatus with inverted gpio LED
    • #2040: [Kura 3.2.0 QA] PositionService does not switch between GPS and static position
    • #2037: The interface number for usb tty devices should be retrieved by the native library
    • #1999: Connection refresh sometimes causes duplicate entries
    • #1957: [Wires] Allow using the component name as label
    • #1933: Support SCR/Declarative Services 1.3+
    • #1921: Consider using EquinoxLauncher instead of the EclipseStarter
    • #1911: [Artemis] Upgrade to version 2.5.0
    • #1849: SSL Configuration - Keystore path change doesn't work
    • #1644: [Artemis] MQTT clients fail to reconnect after the broker is restarted
    • #1358: [GPS] With a USB GPS device, the position service keeps reporting the old position
    • #1255: Switch away from log4j 1.x
    • #1186: Get ready for Java 9
    • #689: Upgrade to Camel 2.18.x
    • #673: CloudServiceFactory deleteConfiguration
    • #651: Call to "exit()" in native code
    • #520: [Net] PppFactory is not a factory and its design is wrong
    • #518: [Net] Modem monitor concurrency issue with multiple modems
    • #208: Include camel-amqp component jar in base distribution
    • #181: [GPS] position service: code review
  • Merged no issue-related Pull Requests:

    • #2288: Changes to prevent usage of the same db table between different cloud connections
    • #2285: Changes to the binary parser library
    • #2276: Changed validity checks for RMC strings
    • #2273: Fixed dev-env launch configs.
    • #2270: Updated Eclipse SSL cert to enable connection to Eclipse Mqtt broker.
    • #2269: Set the command service as disabled per default.
    • #2266: Disabled apparmor at framework installation.
    • #2260: Fixed modem monitor
    • #2259: Fix wrong reference to certificate servlet.
    • #2257: Update to equinox wireadmin 1.0.800
    • #2255: Added the interfaceName as argument in monitor listeners; fixed NPE
    • #2251: Fixed old wireService reference.
    • #2231: Avoid saving snapshot at shutdown
    • #2230: Fixed cloud connection status url linux path parsing
    • #2229: Add another type converter for Wires/Camel integration
    • #2228: Fix a typo in the log message
    • #2221: Fixed notification publisher topic.
    • #2222: Fixed change in asset configuration property types
    • #2216: Implemented forcing endpoint URL in OPCUA driver
    • #2212: Improved subscription management in default CloudEndpoint
    • #2198: Synchronized BLE iBeacon scanner configuration with code
    • #2194: Updated configuration label in BLE example
    • #2192: Stop default H2 db service
    • #2191: Set payload timestamp in BLE scanner examples
    • #2188: Use log4j2 in emulator and tests
    • #2175: NMEAParser class cleanup
    • #2173: Implemented nonblocking config update for s7 driver
    • #2126: Updated wires devel components to use new API
    • #2112: Fix the creating of a random topic
    • #2099: Save two process forks when writing the config files
    • #2094: Sort interfaces alphabetically
    • #2083: Improve debug output of known wires
    • #2081: Fix Wire component labels
    • #2071: Simplify ifcfg config
    • #2063: Fix a NPE and provide proper cause of error
    • #2061: Fixed lint issues
    • #2053: Update to Eclipse Milo 0.2.1
    • #2041: Started fixing archetype
    • #1978: Modbus TCP incorrectly reads frame length
    • #1940: Solved some possible NPEs in web2 bundle.
    • #820: Upgrade to GWT 2.8.2

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • The reference JVMs are:
    • ReliaGATE 10-11: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-20: Oracle Java SE Embedded 8u51
    • ReliaGATE 20-25: Java SE Runtime Environment 8u162
    • BoltGATE 20-25: Java SE Runtime Environment 8u162
      In order to take advantage of all the Red Hat Fuse features, the Embedded 8u51 JVM needs to be updated with the
      Nashorn jar available in the ESF downloads site.
  • #624: [Serial] RXTX fails to set 38400 bauds
  • #602: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #510: [ESF 5.2.0 QA] .restoreDefaultConfig.sh can produce invalid /etc/network/interfaces
  • #509: [ESF 5.2.0 QA] Check message verification failed with diagnostics ping
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE also tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • #2069: Marketplace install when LAN-only
  • #2038: [Kura 3.2.0 QA] Package uninstallation log
  • #2013: Unsaved changes dialog triggers incorrectly
  • #1993: Search Domains Are Not Supported
  • #1932: SystemAdminService.getUptime() returns SystemAdminService#UNKNOWN on MacOS when locale is not English
  • #1663: Authentication Issue with Deploy V2
  • #1572: serial modbus has errors on some hardware
  • #1533: MqttDataTransport client-id illegal character
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1195: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #362: Uninstaller leaves most of the files
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Eurotech Everyware Software Framework ESF 5.2.0 (Eclipse Kura - 3.2.0) - April 2018

Added Features:

  • ReliaIO support: added support for Eurotech ReliaIO 10-12 extension module.
  • Gateway sensors reading in Diagnostic Service: integrated temperature sensors in gateway's
    Diagnostic Service (only for gateways that expose support at Linux level).
  • Docker support: provided a specific Docker image based on RHEL that runs ESF in no-network version.
  • BoltMAR 20-28 support.
  • Multiport Wires Components: Add Wires components with multiple input/output ports to allow
    for better routing of data through the Wire Graph. With the addition of new arithmetic and conditional
    Components, this will allow more flexibility and usability in creating logical flows through the Graph.
  • LoRa driver: added a new driver to support LoRa connectivity.
  • Wires Conditional Component: Add Wires component that facilitates if/then/else logic.
  • Wire Arithmetic Component: Add Wires component that facilitates basic arithmetic functions.
    This bundle is available as an example project.
  • Wires Statistical Component: Add Wires component that performs basic statistical analysis.
    This bundle is available as an example project.
  • Wires Join Component: Add Wires component that performs join operations.
  • Wire Publisher Position: Add support for device position in published messages. The user can decide
    whether or not having the position included in messages published to the cloud and also the verbosity
    of the position information included.
  • Wire Graph export: Add support, in the wire composer, to export only a working wire graph.
  • Assets: Add support for event driven Drivers
  • Assets: Channels can now be individually enabled and disabled.
  • Drivers: To further extend the usability of Kura, new Drivers for GPIO, Raspberry Pi SenseHAT,
    and Event Driven Drivers will be introduced.

Compatibility:

  • ESF v5.2.0 does not introduce API breakage with previous releases.
  • Since this version, the integrated ESF broker will be not provided as default in all the
    distributions. It is available as an add-on downloadable and separately installable.
  • Since this version, the ReliaGATE 20-26 distribution will not include Fuse by default.
    It can be downloaded and installed separately as a dp.

Target Environments:

  • ESF supports the following Devices:
    • ReliaGATE 10-05;
    • ReliaGATE 10-11;
    • ReliaGATE 10-12;
    • ReliaGATE 10-20;
    • ReliaGATE 20-25;
      • Support for Bluetooth 2.1 is not available since Eurotech Linux version 22.0.0
    • ReliaGATE 20-26;
    • BoltGATE 20-25;
      • Support for Bluetooth 2.1 is not available
    • BoltMAR 20-28;
      • Support for Bluetooth 2.1 is not available
    • Raspberry Pi 2;
    • Raspberry Pi 3;

Bug Fixes (ESF):

  • Fixed github issues:
    • #542: [Diagnostics] Ping messages are subject to rate limiting
    • #533: [Diagnostics] Wifi signal level can be published if interface is disabled
    • #532: [Diagnostics] Review priority of DIAG messages
    • #530: [Diagnostics] MQTT RTT ping messages are sent even if the CloudClient is disconnected
    • #522: [ESF 5.2.0 QA] [10-20] bind does not start
    • #517: [ESF 5.2.0 QA] [10-20] RPM installation fails on Linux 11.00.00
    • #514: [ESF 5.2.0 QA] libdio.so SIGSEGV kills the JVM in Reliagate-20-25 v22
    • #512: [ESF 5.2.0 QA] Channel names uploading an old Asset snapshot
    • #511: [ESF 5.2.0] Fuse and AMQ7 will only be distributed as addons
    • #495: Fix initial network configuration and modem reset on J18 USB connector for BoltMAR 20-28
    • #484: [10-20] [10-05] UsbService native lib cannot be loaded
    • #477: Add ESF profile for BoltMAR 20-28
    • #476: Change reboot cause message
    • #467: Support for ReliaIO 10-10
    • #465: ESF 5.1 Upgrader script output
    • #464: Potential issue in upgrader script
    • #461: AWS connection needs TLSv1.2
    • #460: [RG10-12] Serial ports for Telit LE910v2 can be mapped in unexpected way
    • #444: Modbus Driver does not support fragmentation for large requests
    • #437: Review ESF installation scripts
    • #436: Diagnostics Service processNonPersistentAlerts
    • #435: [Diagnostics] Persistent cycles should be allowed for each monitored resource
    • #433: [Diagnostics] Understand how CPU utilization is computed
    • #415: Sending successful install feedback to Eclipse Marketplace does not work
    • #405: [Diagnostics] Improve CloudService tracking
    • #390: ESF install script should not edit /var/spool/cron/root
    • #332: Review configuration files and scripts installed by ESF
    • #214: [DNS] Check bind/named configuration files
  • Merged no issue-related Pull Requests:
    • #547: Removed gps port from snapshot_0
    • #544: Added missing rpm plugin property for Boltmar-20-28.
    • #540: Modified docker files to support two images built at the same time.
    • #539: Removed watchdog switch script
    • #529: Fixed libudev.so.0 symlink
    • #527: Added gpio driver dp
    • #508: Fix RPM for the ReliaGATE 10-12 and Linux 20.2.0
    • #505: Add _binary_payload statement on rpm plugin for 10-11
    • #500: Solved DS issue with Reboot service.
    • #498: Fixed logrotate issue on 20-26
    • #494: Managed container stop and ESF execution modalities.
    • #493: Removed localisation
    • #491: Gateway Sensors integration
    • #489: Lora Driver implementation for Kura Asset-Driver Topology
    • #487: Changes that allow to view, select and add modem PDP profiles
    • #479: ESF docker image based on rhel
    • #456: Fix messaging process in Pcn2Transportation

Bug Fixes (Kura):

  • Fixed github issues:

    • #2042: Switching network interface status from 'L2Only' to 'Unmanaged' doesn't work.
    • #2022: Factories don't get removed from creation dialog
    • #2020: Wrong column content in assert/driver view
    • #2015: New Factory Component - drop-down-list item missing for a installed package
    • #2014: Deleting a component keeps tab open
    • #2012: DB-H2-012 fails
    • #2010: Exception when disabling watchdog
    • #2009: DATA-LIMIT-001 fails
    • #2007: Array validation doesn't work properly
    • #2002: DEN-DEPLOY-005 failed
    • #1997: Improve dhcpd shutdown logic
    • #1853: SensorTagDriver sometimes fails to connect to the SensorTag
    • #1975: [Kura 3.2.0 QA] Warning logged uploading and old Asset snapshot
    • #1973: [Kura 3.2.0 QA] Wire graph snapshot includes the Meta Type OCD
    • #1971: EthernetMonitor can't monitor more than two ethernet interfaces
    • #1970: [Kura 3.2.0 QA] Multiple handling of PositionLocked
    • #1959: [Web] Escaping doesn't seem to work properly
    • #1956: [Wires] Creating a component named ")" is possible
    • #1955: [Wires] New Wire Component name entry field is broken
    • #1941: [DbDataStore] Stale messages not purged with timezone other than UTC
    • #1936: [Driver] Improve the way Driver instances are shared between consumers
    • #1928: Removing and reinstalling the Script Filter dp causes a lot of components to be restarted
    • #1924: [Wires] Script Filter and Conditional use different syntax
    • #1914: User should be able to set PDP context number for setting APN.
    • #1907: [WireAsset] Implement Driver generated single timestamp
    • #1906: [Wires] Download graph as a (partial) configuration snapshot
    • #1905: [WirePublisher] Add option to publish the geographic position
    • #1902: Allow to enable/disable channels in asset configuration
    • #1894: Show Wire Component description in the Web Ui
    • #1892: Add SenseHat Driver
    • #1886: Package unistall error
    • #1878: Add support for "Unmanaged" mode for network interfaces.
    • #1876: Packages URL downloader does not use Kura's SSLContext
    • #1874: Change the reboot cause string
    • #1870: Develop a GPIO Driver for Kura Wires
    • #1863: IBeacon decoder index out of bounds
    • #1861: Implement a WireAsset reacting to channel changes
    • #1859: [Drivers and Assets] The channels names and labels in dropdown lists aren't sorted
    • #1856: DEPLOY-V2: download always uses the defalut java keystore
    • #1843: BaseChannelDescriptor contains some inconsistencies
    • #1840: [OPC-UA] Improve type conversions in OPC-UA driver
    • #1836: Jetty security issue
    • #1835: [Documentation] AWS connection needs TLSv1.2
    • #1834: [OPC-UA] The OPC-UA driver should not specify timestamps on write requests
    • #1826: LE910 V1 doesn't turn back on at modem reset.
    • #1823: Failure to submit Wifi configuration when wifi password (PSK) ends with the $.
    • #1822: [Wires] Faulty refresh in Chrome
    • #1821: [Wires] New Wires features don't work in IE
    • #1816: [Emulator] NumberFormatException while installing new packages
    • #1815: [Wires] Channel timestamp should be optional
    • #1813: Marketplace dp installation popup drop-zone
    • #1812: [PortFwd] Fields for internal and external ports mixed up
    • #1811: Wires: Multi-port components and graph execution model
    • #1809: [Wires] Drag and drop should respect canvas grid
    • #1808: Define the JSON WireService persistence form
    • #1807: [Wires] Add Component Multi Port support
    • #1802: [Wires Refactoring] Wires WebUi refactoring
    • #1801: Refactor Wires js code. GWT client should be the orchestrator.
    • #1800: Modify Client code so GWT client prepares wire component configuration from GwtWireGraphConfiguration
    • #1799: Modify code so GWT client calls jointjs to build graph from GwtWireGraph
    • #1798: Move Wires-related code out of the GWT Server part
    • #1797: [Wires Refactoring] Implement new Wires APIs
    • #1796: [Wires Refactoring] Review APIs
    • #1795: Refactor WireServiceImpl to also implement WireGraphService
    • #1793: Update ConfigurationService API with new methods to handle factory OCDs
    • #1792: Define WireGraphService and deprecate WireService
    • #1786: Wire publisher do not include a timestamp in the message
    • 1778: [Wires] Web Ui error when deleting a not saved component

      *Â #1777: [Wires] Drag and drop glitch
    • #1776: [Wires] Add a refresh button in Wire Composer
    • #1773: Kura DB Store Query
    • #1772: Remove the icons from the "new component" dialog
    • #1770: CloudService instance hint should be persistent while the user writes
    • #1761: NetworkAdminServiceImpl: submitFirewallConfiguration blocks for 30 seconds
    • #1758: [Web UI] Initial page view on a narrow screen
    • #1757: Remove GpsClockSyncProvider in Clock Service
    • #1753: Typo in Eddystone provider component definition
    • #1737: CloudClient subscribes to more topics than requested
    • #1734: Display of asset channel data in WebUI in case of failures
    • #1703: [Kura 3.1.0 QA] Wires page jumping up and down
    • #1700: [Kura 3.1.0 QA] Rollback doesn't restore deleted services
    • #1689: Instaling a dp can cause the WebUI to restart
    • #1657: Bluetooth notifications do not work
    • #1632: Cleanup old scripts in distrib/resources folder
    • #1268: [WebUI] Usability Improvements
    • #1213: [Wires] Should DB Filter clean the cache on empty result set?
    • #1193: [Wires] Component avoidance during initial placement
    • #1188: [Wires] Components can be hidden outside the graph area
    • #1092: Possible NPE and non-working check
    • #890: [Kura 2.1.0 QA] Snapshot management in web UI
    • #590: [Cloud] CloudConfigurationHandler casts to ComponentConfigurationImpl without type check
    • #520: [Net] PppFactory is not a factory and its design is wrong
  • Merged no issue-related Pull Requests:

    • #2044: Fixed dhclient issue after Raspbian fresh install
    • #2039: Fixed rotation issue in sensehat driver
    • #2036: Fix for modem serial ports detection and ppp
    • #2035: Fixed possible NPE in sensehat driver
    • #2034: Added stop watchdogd step to WatchdogService
    • #2028: Removed localisation from o.e.k.w.provider bundle
    • #2023: Removed 'Search Domains' field
    • #2016: Modified wrong reference to internal modem
    • #1996: Added dp for gpio driver
    • #1992: Re-enable plain Fedora installer in addition to RPMs
    • #1988: Backport maintenance fixes
    • #1985: DIO: fix unsafe casts in native code for 64 bits architectures
    • #1984: Changed gpio bundle defaults, removing the hardcoded gpio 1.
    • #1974: Fixed wrong pid reference in configuration upgrade class.
    • #1968: Fixed too strict package imports
    • #1966: Added missing since in APIs for modem management.
    • #1963: Prevent getters from creating new object instances
    • #1954: Fixed possible NPE in OPCUA driver
    • #1949: Added notifications on SensorTagDriver and fix several bugs in SensorTagExample
    • #1947: Fixed modem reset functionality.
    • #1944: Fix a possible NPE
    • #1943: o.e.k.w.c.provider: fix Import-Package version range
    • #1931: WireAsset: do not log errors if they are emitted
    • #1925: Changed exists plugin default. Now it's disabled.
    • #1917: Improve the description of a few settings
    • #1915: [H2] Updated service description
    • #1913: Wires composer robustness and usability improvements
    • #1891: Fixed potential malfunction of Eddystone-UID advertiser with some hcitool versions
    • #1888: Added tcp socket connection timeout
    • #1848: Disabled the kura.primary.network.interface property.
    • #1847: HTML IDs
    • #1829: URL.openStream() creates a new connection without SslContextFactory set
    • #1755: Modified the success notification in order to not being executed in a different thread.
    • #1738: Modified localization.resources fragment to reference the host with a version range.
    • #1432: Remove Intel Edison Profile

Known Issues (ESF):

  • ReliGATE 10-05 (All versions)
    • Rarely the Bind process can crash after client connection.
  • ReliGATE 10-05 (REGATE-10-05-34)
    • Modem: modem supports only SIMs that does not require authentication
    • Off-the-shelf instant activation/provisioning supported since Linux release WTL_20160809_1
    • Beacon scanner application supported since Linux release WTL_20160809_1
    • Modem: support limited to Ublox Lisa/Sara-U2
  • ReliGATE 10-05 (pre-production versions):
    • 256MB RAM option is totally unsupported
    • Modem: support limited to Ublox Lisa/Sara-U2
    • Modem: modem supports only SIMs that does not require authentication
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Beacon scanner application not supported (missing 'hcidump')
    • Wi-Fi WEP authentication is not reliable
  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • The TinyB library used by the Bluetooth LE API implementation sometimes cause a JVM crash.
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • The reference JVMs are:
    • ReliaGATE 10-05: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-11: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-20: Oracle Java SE Embedded 8u51
    • ReliaGATE 20-25: Java SE Runtime Environment 8u161
    • BoltGATE 20-25: Java SE Runtime Environment 8u161
      In order to take advantage of all the Red Hat Fuse features, the Embedded 8u51 JVM needs to be updated with the
      Nashorn jar available in the ESF downloads site.
  • #549: Modem GPS not really disabled
  • #548: Serial port not released by the PositionService
  • #510: [ESF 5.2.0 QA] .restoreDefaultConfig.sh can produce invalid /etc/network/interfaces
  • #509: [ESF 5.2.0 QA] Check message verification failed with diagnostics ping
  • #490: [10-11] The ESF installation may fail for missing zip dependency
  • #470: RPM broken on the ReliaGATE 20-25 and 10-12
  • #466: [PositionService] Potential Telit modem GPS serial port contention
  • #424: [Terminal Services] socat does not set tty parameters on the ReliaGATE 20-25
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #254: [20-26] No watchdog devices are exported on /dev
  • #224: [20-26] GPIOs and LEDs are not available on the system
  • #223: [20-26] Serial ports are not available
  • #167: [10-05] 2G modem option not supported by ESF
  • #160: [10-05] WiFi "device or resource busy" for a while after station mode reconfiguration
  • #134: [10-05] On Ginevra ESF 4.0.0 includes Bluetooth support
  • #131: [10-05] On Ginevra ESF 4.0.0 installer overrides network settings
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • The TinyB library used by the Bluetooth LE API implementation sometimes cause a JVM crash.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • Web UI may hang when configuration snapshot is uploaded. This happens because HTTP connection is lost due to toggling of the network
    interface which happened even if network configuration hasn't been modified.
  • #2050: Modem monitor in Not connected state does not trigger reset
  • #2040: [Kura 3.2.0 QA] PositionService does not switch between GPS and static position
  • #2013: Unsaved changes dialog triggers incorrectly
  • #1999: Connection refresh sometimes causes duplicate entries
  • #1995: Failed NET-WIFI-003 on Fedora
  • #1993: NET-ETH0-003 failed
  • #1932: SystemAdminService.getUptime() returns SystemAdminService#UNKNOWN on MacOS when locale is not English
  • #1788: Maven Archetype does not work - or can someone show me how to use it?
  • #1663: Authentication Issue with Deploy V2
  • #1644: [Artemis] MQTT clients fail to reconnect after the broker is restarted
  • #1572: serial modbus has errors on some hardware
  • #1533: MqttDataTransport client-id illegal character
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1414: SCR exception running Kura Wires in Karaf
  • #1373: [Kura 3.0.0 QA] Configuration service: mixing configurable services with factory components
  • #1358: [GPS] With a USB GPS device, the position service keeps reporting the old position
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #924: [Kura 2.1.0 QA enh] Non-trimmed values of configuration parameters
  • #923: [Kura 2.1.0 QA] eth0 search domain configuration and storage
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #651: Call to "exit()" in native code
  • #650: Possible bug in "LinuxUdev.c"
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #520: [Net] PppFactory is not a factory and its design is wrong
  • #518: [Net] Modem monitor concurrency issue with multiple modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #362: Uninstaller leaves most of the files
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Eurotech Everyware Software Framework ESF 5.1.0 (Eclipse Kura - 3.1.0)

Added Features (ESF):

  • Scheduled Reboot service: when configured, allows to reboot the gateway based on a
    temporal basis specified by a cron expression
  • RPMs: This release will provide RPM packaging for all the supported platforms.
  • Diagnostic bundle: included in all system distributions
  • H2 Databases: This release will see the switch from HSQLDB to H2. This migration will allow
    for a number of performance improvements as well the ability to maintain multiple database instances.
  • REST API for Kura Drivers and Assets: To allow more flexibility, REST endpoints will be
    added to Kura for interacting with the Kura Drivers and Assets instances.
  • Embedded Artemis Broker: The addition of the Apache Artemis Broker will extend Kura's
    messaging functionality.
  • BLE via TinyB: To improve the reliability of BLE, Kura will switch to the TinyB library
    to support BLE via Bluez.
  • Wires Functional Logic: To extend the usability of Wires, this release will
    include Functional Logic Wire Components. This will allow the use of plain JavaScript
    inside a Wire component.
  • Web UI Update: A new UI element will be added for managing and editing Drivers and Assets.
  • S7 Industrial Protocol: A new driver will be added to the Eclipse Marketplace to support S7.
  • BLE/SensorTag: A new driver will be added to the Eclipse Marketplace to support BLE on
    the TI SensorTag.
  • MQTT publish rate improvement: A limit parameter will be added to the MQTT transport service
    to allow throttling of MQTT messages to prevent unnecessary congestion on the MQTT broker.
  • Connection Monitor: A connection monitor will be introduced to the DataService to further
    improve connectivity reliability.
  • BoltGATE 20-25 support.
  • Terminal Services: Multiple instances, XON/XOFF support and extra low level options for socat.

Compatibility:

  • ESF v5.1.0 does not introduce API breakage with previous releases.
  • This release does introduce a new set of APIs for TinyB for interacting with BLE devices.
    Support for previous BLE APIs will still be present and functional.
  • In ESF v5.1.0 it is possible to instantiate a Driver instance from the Drivers and Assets
    section or from Wire Composer only if the following requirements are met:
    • the Driver implementation class must implement the following interfaces:
      • Driver
      • ConfigurableComponent or SelfConfigurableComponent
    • the Driver must provide a component definition xml file that advertises that
      the interfaces mentioned above are provided and that sets "required" as configuration policy.
      It is advisable to update the deployment packages of non compliant drivers if needed.
      It is still possible to instantiate non compliant drivers using the "+" button under "Services".

Target Environments:

  • ESF supports the following Devices:
    • ReliaGATE 10-05;
    • ReliaGATE 10-11;
    • ReliaGATE 10-20;
    • ReliaGATE 20-25;
      • Support for Bluetooth 2.1 is not available since Eurotech Linux version 22.0.0
    • ReliaGATE 20-26;
    • BoltGATE 20-25;
      • Support for Bluetooth 2.1 is not available
    • Raspberry Pi 2;
    • Raspberry Pi 3;

Bug Fixes (ESF):

  • Fixed github issues:

    • #438: Diagnostics publishes modem alert even if the modem is not configured
    • #414: Include Sensortag driver in ESF 5.1.0 dp files.
    • #411: REST API support is missing
    • #410: [RG10-05] Ppp connection fails with APN authentication
    • #400: [ReliaGATE 20-25, ReliaGATE 10-11] Resolv.conf file changes prevent DNS resolution
    • #399: [ReliaGATE 20-25] Wifi password verification fails
    • #387: Occasional RPM database corruption issue
    • #380: [Diagnostics] Send an alert with the last reboot cause
    • #376: Add support for MSW/LSW orderings to Modbus driver
    • #374: Add package dependencies to the RPM
    • #373: Add RPM build step that merely installs ESF on Yocto without checking dependencies
    • #359: [20-25] PinStatusListener does not work
    • #350: Wlan0 interface for RG 10-11 is not listed in the web ui.
    • #344: Create RPM installers
    • #343: Scheduled reboot service
    • #342: [Diagnostics] Remove dependencies from Configuration Admin
    • #340: Azure IoT documentation is missing certificate configuration
    • #338: Add SCM and CI information to kura.properties
    • #333: Add diagnostic bundle to distrib enabled with high thresholds
    • #328: [Web UI] Change the ESF logo in the upper left corner
    • #242: [10-05] PTC-BT-003 Exception switching from bluetooth discovery to spp server (won't fix)
    • #225: [20-26] Bluetooth 2.1 doesn't work on the device (won't fix)
    • #181: Unhelpful error when failing to connect to the broker
    • #142: ESF default iptables configuration has SSH port open
    • #126: [Terminal Server] The serial packets can be split in multiple tcp packets (won't fix)
  • Merged no issue-related Pull Requests:

    • #432: Fixed DiagnosticsService persist cycles handling
    • #429: Fix firewall
    • #428: Fixed selinux policy for 20-26
    • #427: Added workaround to allow using watchdog on 10-05
    • #425: Terminal Services: Multiple instances, XON/XOFF, low level socat options and raw mode
    • #422: Fixes bug in beacon example project.
    • #421: Upgrader: Set timeout to 50 mins, managed success using a file in tmp.
    • #420: Added wires script filter dp.
    • #419: Added commercial version of Artemis
    • #417: Added diagnostics bundle base config to all the distributions.
    • #413: Added Artemis, boltgate-20-25-nn, renamed h2.
    • #409: Fixed wrong property name in kura.properties file.
    • #408: Renamed BoltGATE profile.
    • #407: Added ccs led support for BoltGATE 20-25
    • #406: Removed the old prod profile.
    • #404: Added entry for /sys/class/led folder.
    • #403: Added RS485 bundle for BoltGATE 20-25
    • #401: Added support for the newest ReliaGATE 20-25 linux image.
    • #397: Added BoltGATE 20-25 profile.
    • #394: Updated startup scripts
    • #388: Included kura-custom.properties files in the start scripts.
    • #360: ESF TinyB integration
    • #352: Add PCN reboot method.
    • #346: Added H2 db integration
    • #336: Removed customizers

Bug Fixes (Kura):

  • Fixed github issues:

    • #1725: [Kura 3.1.0 QA] Cloud Services GUI crashes
    • #1724: [Kura 3.1.0 QA] WiFi DHCP: Gateway IP wrong in GUI
    • #1720: [Kura 3.1.0 QA] SensorTagDriver NPE if wrong address
    • #1707: [Kura 3.1.0 QA] BLE iBeacon* only react to company code 004c
    • #1702: [Kura 3.1.0 QA] Artemis in emulator
    • #1685: [WebUi] Security policy fingerprint UI does not expand
    • #1680: getKuraMarketplaceCompatibilityVersion() always returns kura.version
    • #1665: Create rpm installer for Fedora
    • #1661: The driver configuration is not applied
    • #1645: Development environment needs to be updated
    • #1641: Oomph installer needs to be updated
    • #1630: Wifi password check failing
    • #1590: [Assets and Drivers] Byte arrays are not displayed properly
    • #1588: Password arrays are not well managed by ConfigurationService
    • #1585: [Messaging] Share cloud connection with external applications
    • #1575: [Watchdog Service] Write the last reboot cause to a persistent file
    • #1564: [MqttDataTransport] wss connections without hostname verification do not work
    • #1558: CommandCloudApp doesn't use received working directory parameter
    • #1556: connect.retry-interval=0 causes DataService activation failure
    • #1541: Add support for polling to GPIO example
    • #1531: Create "Drivers and Assets" tab
    • #1530: Modify the wire composer to allow driver management
    • #1517: Verify compatibility of the old Bluetooth implementation with Bluez 5.43
    • #1513: H2 DB: Web app and TCP server are mutually exclusive
    • #1511: Add Artemis broker to Kura core
    • #1506: H2 DB: Changing the db user does not work
    • #1502: H2 DB: Default service can be deleted
    • #1501: H2 DB: invalid service configuration not indicated
    • #1471: [Wires] Deleting a Timer instance might stop all other Timers
    • #1462: Wire Components list has no scrollbar
    • #1455: Wiki page documenting H2 use cases
    • #1453: Remove unused lib directory from org.eclipse.kura.linux.usb
    • #1447: New BLE beacon/advertisement API
    • #1442: Add TinyB host and fragment bundles in target-platform
    • #1435: Snapshot problem on wires
    • #1429: Support arm 64 bits platform
    • #1421: Replace HSQLDB with H2
    • #1420: Promote Assets and Drivers like Cloud Services in the Web UI
    • #1417: Implement DataService connection monitor as a CriticalComponent
    • #1416: Limit the rate of messages published by the DataService
    • #1413: Implementation of a SensorTag Kura Driver
    • #1412: Beacon/advertisement implementation of the new BLE API
    • #1411: GATT Implementation of the new Bluetooth Low Energy API
    • #1409: New Bluetooth Low Energy API
    • #1405: Fix trivial Sonar Lint problems in the network bundles
    • #1396: [Beaglebone Black] Log4j log level set to DEBUG
    • #1391: [Wires] Fifo is really FIFO only while it's full
    • #1386: [Wires] Null properties in channel configuration are not properly handled
    • #1384: OPC UA Driver channel descriptor property ids shouldn't be localised
    • #1383: OPC UA Driver only supports string node ids
    • #1378: [Wires] DB store primary key
    • #1376: [Wires] Asset configuration is not updated after a ChannelDescriptor change.
    • #1369: WiFi password (PSK) can't contain '&'
    • #1363: [Documentation] Add tutorial on Eclipse Kapua connection
    • #1362: [Documentation] Kura documentation improvements
    • #1361: [Documentation] Improve Kura wires documentation
    • #1360: [Documentation] Add Administration section in Kura documentation
    • #1359: [Documentation] Add Configuration section in Kura documentation
    • #1354: Document default tracking of services registering Configurable/SelfConfiguringComponent
    • #1338: [Kura 3.0.0] camel.aggregation and camel.quickstart examples should be "normalized"
    • #1325: [Wires] Exception if an Channel Descriptor contains in Option of Integer type
    • #1321: 64bit Linux version broken
    • #1288: Clean up JavaDoc of KuraPayload
    • #1250: Drag and drop of Marketplace listing should send back a successful install count
    • #1243: Distribute publishing over time
    • #1207: [Driver] Contribute Siemens S7 Driver
    • #1196: [Net] PPP password is not a (MetaType) Password
    • #1032: Eclipse Drag and Drop Review
    • #864: [Web UI] Settings pages
    • #752: [DbDataStore] repair is very slow on big tables
    • #751: [DbDataStore] defrag and checkpoint are not per-table operations
    • #572: Unreadable errors in Web UI
    • #308: Add a BLE example for advertising as an Eddystone (Google) beacon
    • #307: CloudCallService overrides client ID
    • #153: Add JAX-RS to target platform
    • #108: CloudCallServiceImpl - call methods setting requester.client.id to #client-id sends response to local device
  • Merged no issue-related Pull Requests:

    • #1731: Swapped commands in modem initialization
    • #1729: Aligned dev-env kura.properties file to the one used in devices.
    • #1728: Fixed a bug in the parseDhclientLeaseBlock() method.
    • #1719: Changes to dp generation for examples and drivers.
    • #1718: Disabled h2 log file by default
    • #1717: Fixed firewall init script
    • #1716: Fixed "watchdog did not stop" messages in syslog
    • #1713: Refreshed kuraHome variable after loading from kura.properties file.
    • #1711: Fixed component definition for can example
    • #1699: Setting an higher value for the GPIO pins.
    • #1697: Fixes a possible NPE in cloud services when a dp is removed.
    • #1688: Added custom auth request command for Ublox modems
    • #1687: Updated mapping between services and Ui icons.
    • #1682: Reduced maximum size for custom icons to 14x14 to match the other build-in icons.
    • #1676: Removed Karaf dependency from examples.
    • #1675: Implemented DEPLOY-V2 hook support
    • #1673: Added fallback into status bundle.
    • #1671: Removed the dependency existing between examples and distrib.
    • #1659: Fixed Telit LE 910 v2 reset
    • #1640: Enhanced core.status bundle.
    • #1624: Added basic support for Telit 910 LE v2
    • #1599: Fixed startup scripts and WatchdogService
    • #1598: Enabled snaphsot dp builds
    • #1589: Added css to rotate the wires image properly.
    • #1496: Updated for Windows build
    • #1483: Added data transfer optimisation library for Drivers
    • #1480: Changes in Device tab.
    • #1460: [Testing][Refactoring] NetworkAdminServiceImpl tests, refactoring, fix
    • #1459: [Refactoring] Linux.position refactoring
    • #1458: [Testing][Refactoring] Added Camel unit tests
    • #1454: Cleanup org eclipse kura linux net wifi
    • #1450: Added exists-maven-plugin.
    • #1445: Added protection code to prevent null pointer in GwtWireServiceUtil.
    • #1443: Remove customizers
    • #1375: Fixed Karaf native libs loading.
    • #1371: Fixed regression in configuration service
    • #1370: Fixed connection status icon at page load.
    • #1368: Wires Web Ui fixes
    • #1318: Code Cleanups in Localization Bundle

Known Issues (ESF):

  • ReliGATE 10-05 (All versions)
    • Rarely the Bind process can crash after client connection.
  • ReliGATE 10-05 (REGATE-10-05-34)
    • Modem: modem supports only SIMs that does not require authentication
    • Off-the-shelf instant activation/provisioning supported since Linux release WTL_20160809_1
    • Beacon scanner application supported since Linux release WTL_20160809_1
    • Modem: support limited to Ublox Lisa/Sara-U2
  • ReliGATE 10-05 (pre-production versions):
    • 256MB RAM option is totally unsupported
    • Modem: support limited to Ublox Lisa/Sara-U2
    • Modem: modem supports only SIMs that does not require authentication
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Beacon scanner application not supported (missing 'hcidump')
    • Wi-Fi WEP authentication is not reliable
  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • The reference JVMs are:
    • ReliaGATE 10-05: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-11: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-20: Oracle Java SE Embedded 8u51
    • ReliaGATE 20-25: Java SE Runtime Environment 8u92
    • BoltGATE 20-25: Java SE Runtime Environment 8u92
      In order to take advantage of all the Red Hat Fuse features, the Embedded 8u51 JVM needs to be updated with the
      Nashorn jar available in the ESF downloads site.
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #415: Sending successful install feedback to Eclipse Marketplace does not work
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #278: [RG10-05] Failed to connect to OPC-UA server
  • #254: [20-26] No watchdog devices are exported on /dev
  • #224: [20-26] GPIOs and LEDs are not available on the system
  • #223: [20-26] Serial ports are not available
  • #214: DNS] Check bind/named configuration files
  • #180: Unit connects then fails to connect because wlan0 is enabled for LAN
  • #167: [10-05] 2G modem option not supported by ESF
  • #160: [10-05] WiFi "device or resource busy" for a while after station mode reconfiguration
  • #144: [10-20] LE910 modem is not always detected by ESF at startup
  • #134: [10-05] On Ginevra ESF 4.0.0 includes Bluetooth support
  • #131: [10-05] On Ginevra ESF 4.0.0 installer overrides network settings
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • Web UI may hang when configuration snapshot is uploaded. This happens because HTTP connection is lost due to toggling of the network
    interface which happened even if network configuration hasn't been modified.
  • #1703: [Kura 3.1.0 QA] Wires page jumping up and down
  • #1700: [Kura 3.1.0 QA] Rollback doesn't restore deleted services
  • #1689: Instaling a dp can cause the WebUI to restart
  • #1663: Authentication Issue with Deploy V2
  • #1657: Bluetooth notifications do not work
  • #1644: [Artemis] MQTT clients fail to reconnect after the broker is restarted
  • #1638: Kura does not support Consistent Network Device Naming
  • #1572: serial modbus has errors on some hardware
  • #1558: CommandCloudApp doesn't use received working directory parameter
  • #1533: MqttDataTransport client-id illegal character
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1451: PppAuthSecrets entry removal
  • #1414: SCR exception running Kura Wires in Karaf
  • #1373: [Kura 3.0.0 QA] Configuration service: mixing configurable services with factory components
  • #1358: [GPS] With a USB GPS device, the position service keeps reporting the old position
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1197: [Net] Network configuration cannot be restored purely from snapshot
  • #1195: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #1193: [Wires] Component avoidance during initial placement
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1092: Possible NPE and non-working check
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #924: [Kura 2.1.0 QA enh] Non-trimmed values of configuration parameters
  • #923: [Kura 2.1.0 QA] eth0 search domain configuration and storage
  • #890: [Kura 2.1.0 QA] Snapshot management in web UI
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #651: Call to "exit()" in native code
  • #650: Possible bug in "LinuxUdev.c"
  • #645: Clean up internal dependencies in Kura
  • #558: Update of DPs seems not to work
  • #547: [Configuration] Configuration Service may miss configuration-policy=optional components
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #520: [Net] PppFactory is not a factory and its design is wrong
  • #518: [Net] Modem monitor concurrency issue with multiple modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #362: Uninstaller leaves most of the files
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #311: [Multiple Cloud Connections] Spurious component reactivations upon configuration change
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Eurotech Everyware Software Framework ESF 5.0.0 (Eclipse Kura - 3.0.0)

Added Features (ESF):

  • Added Modbus driver compatible with Kura Wires

Compatibility Changes:

  • Terminal services: serial port always configured in raw mode. ts.serial.raw parameter is ignored
  • Switched to Equinox 3.11.1
  • Added support for Java 8. It is now the minimal JVM requirement to run ESF
  • The configuration service will only track so called "Relevant services" so the ones that, in their component
    description files, will provide the ConfigurableComponent interface. The old behavior can be restored by setting the
    "org.eclipse.kura.core.configuration.legacyServiceTracking" property to true.
  • Dropped generic Fedora profile for Raspberries
  • Removed unsupported platforms like 50-21, 15-10, 20-11, CPU-301

Added Features (Kura):

  • Eclipse Kura Wires
    https://github.com/eclipse/kura/wiki/Kura-Wires:-introduction-and-references
  • Eclipse Kura Drivers and Assets APIs and implementations
  • Contributed Eclipse Kura OPC UA driver based on Eclipse Milo
  • Improvements to local Web Console's usability and appearance
  • Added support for MQTT over Websockets
  • Added support for AWS IoT and Azure IoT platforms
  • Simple JSON is now a supported encoding option in Eclipse Kura Cloud Service
  • Introduced official support to Oomph installer
  • Added support for Fedora 25 ARM based systems

Bug Fixes (ESF):

  • Fixed github issues:

    • #316: [ESF 5.0.0 QA] installer installs junit's jar file into plugins/
    • #314: [ESF 5.0.0 QA] Selinux configuration is not applied on RG20-26
    • #310: Diagnostics bundle doesn't start
    • #309: ESF Diagnostics package mqtt_round_trip_time calculation
    • #295: [ProvisioningService] Catastrophic effect on canceling the provisioning task
    • #293: Reliagate 10-11-36 ReliaCell Bug
    • #285: [Native libs] Move ARMv5 fragments from Kura to ESF
    • #277: Bundles containing native libraries for multiple platforms/architectures no longer work
    • #276: MQTTDataTransport help is now displaying iot.eclipse.org
    • #271: /etc/monitrc should include all files in /etc/monit.d/*
    • #270: Equinox 3.11.1 breaks ESF security features
    • #269: Bad kura.logrotate file
    • #251: [Net] DHCP client is not killed when an interface is disabled
    • #121: [10-05] Add NN profile]
  • Merged no issue-related Pull Requests:

    • #319: Fixed MQtt round trip time calculation bug. Fixed SonarLint issues.
    • #318: Changes to have ESF 5.0.0 dev-env working.
    • #313: Solved wrong usb native library reference for rhel7 systems.
    • #312: Added RG 10-20 specific network.interfaces file that contains the 'pr…
    • #311: Splitted the diagnostics.dp.customizer native libs into fragments.
    • #308: Removed unwanted double build of kura web bundle.
    • #307: Solved other bunch of issues related to ConfigurableComps.
    • #306: Reenabled kura target platform build in ESF CI.
    • #305: Changes to follow Eclipse version numbering.
    • #304: Updated the driver implementation to meet the new Kura apis.
    • #303: Added missing reference to mvn options.
    • #302: Reduced build coupling with Kura.
    • #301: Added opcua dp generation step.
    • #300: Fix Wagon SCP download (Maven 3.3.x)
    • #299: Fixed commons fileupload reference.
    • #296: Fixed bluetooth import versionin bluetooth.impl bundle.
    • #291: Added mirror for Neon.1.
    • #289: Drop generic fedora profile.
    • #287: Moved native libs from Kura to ESF.
    • #284: Fix iptables-restore run in background
    • #283: Added linux.usb fragments for Eurotech devices.
    • #282: Added modbus driver to the code base.
    • #281: Removed old and unsupported profiles.
    • #280: Updated installer and upgrade for watchdog
    • #279: Splitting of bundles with native libraries into master and fragments
    • #263: Fixed iptables config for RG10-05

Bug Fixes (Kura):

  • Fixed github issues:

    • #1335: [Kura 3.0.0 QA] User workspace plugins BREE
    • #1329: Need to respect /etc/network/interfaces command options
    • #1295: [Wires] Wires DataType lacks the KuraPayload float type
    • #1294: [Wires] Remove ByteValue and ShortValue as they do not map to KuraPayload metric types
    • #1282: Apache FileUpload Upgrade
    • #1277: PR #1126 breaks changes to wire graph that were not saved
    • #1269: [Wires] Column names in DB Store
    • #1246: [Wires] MQTT namespace
    • #1241: Changes to the heater publisher
    • #1240: Add JSON/Protobuf encoding option in CloudService
    • #1239: Change wire publisher to remove the JSON/Kura payload serialization
    • #1222: Commit aa2913dc1031e783d09779dae503018da55889f6 breaks asset persistent storage
    • #1220: [Driver] DriverRecord and AssetRecord. Clean code vs efficiency
    • #1216: [Wires] Sub-second Timer
    • #1212: [Wires] DB WireComponent improvements
    • #1211: [Wires] Implement regex filter WireComponent
    • #1210: [Wires] Implement FIFO WireComponent
    • #1208: [Asset] Driver read method should return void
    • #1206: [Driver] Driver API optimizations
    • #1203: [Asset] Document ASSET-V1 topic namespace
    • #1202: [Asset] Drop channel ID and use unique name
    • #1176: Kura Wires: Inconsistent design of DbServiceHelper class
    • #1166: Wrong order of operations in WireAsset
    • #1160: ClockService should ignore updates with long 'getDelay'
    • #1139: Factory Components Configurations not deleted from the snapshot
    • #1131: ConfigurableComponentTracker calls bundleContext.getService(ref) when it shouldn't
    • #1125: [Kura 3.0.0 M1 QA] Wires: Unexpected component configuration is shown
    • #1123: [Kura 3.0.0 M1 QA] Bugs in camel example publisher
    • #1121: [Kura 3.0.0 M1 QA] Wires: cannot add component after deleting one
    • #1119: [Kura 3.0.0 M1 QA] Wires DB Store partial cleanup
    • #1118: [Kura 3.0.0 M1 QA] Wires: dirty Component instances warning
    • #1116: [Kura 3.0.0 M1 QA] Wires: wire components selection
    • #1113: [Kura 3.0.0 M1 QA] Kura Wires doesn't work on Internet Explorer
    • #1107: [Kura 3.0.0 M1 QA] Issue with modal confirmation dialog(s)
    • #1105: [Kura 3.0.0 M1 QA] Issue with binding services
    • #1104: [Kura 3.0.0 M1 QA] RPi 2/3 installation package contains unwanted files
    • #1100: Inconsistent use of installation status strings in deployment impl
    • #1091: Kura doesn't properly report "ALREADY_DONE" state to Kapua
    • #1069: Change Package Infos in API Bundle that contain @since annotation
    • #1057: Kura Wires BaseAsset write issue
    • #1056: Kura Wires severity level based filtering issue
    • #1053: dhclient is not being killed if interface is switched from DHCP to static
    • #1041: Restructure Wire Envelope to make compatible with Kura Payload
    • #1033: Rename org.eclipse.kura.asset.provider.default to org.eclipse.kura.asset.utility.provider
    • #1026: Dragging a wire component onto the wire graphs pops up the install dialog
    • #1024: PR #1007 broke distribution for assets
    • #1022: Move AssetComponent.xml to Asset Provider
    • #1015: Fix Fedora target to use libudev.so.1
    • #1013: Drop support for ARMv5 SF/soft float
    • #1003: Switch to Fedora 25
    • #1000: Memory leak and concurrency issue in 'EventHandlerServlet'
    • #999: Refactoring: PropertiesUi must extend AbstractServicesUi
    • #990: Script error in installer
    • #959: Replace Preconditions references with Objects
    • #954: Fix output of properties
    • #932: org.eclipse.kura.asset.provider provides API and service implementation
    • #918: [Kura 2.1.0 QA] DEN-POS-002 Position service keeps reporting old position
    • #916: DEN-CONF-005 Wrong range limit for "long"
    • #915: [Kura 2.1.0 QA] DEN-CONF-005: Internal message when a "too big" number is entered
    • #914: [Web UI] Fixed fields can be edited
    • #911: [Kura 2.1.0 QA] SSID selection not always shows all SSIDs
    • #908: Web UI shows its own WLAN for connecting
    • #889: [Kura 2.1.0 QA] Denali Configuration ExamplePublisher error descriptions
    • #861: Kura's WEB bundles detection
    • #846: Replace INTERNAL_ERROR with suitable error code in Kura Wires
    • #841: Add Discouraged Access in Javadoc for INTERNAL_ERROR error code
    • #824: SelfConfiguringComponent are not registered properly
    • #817: Fix Exception Javadoc
    • #786: Services Search throws Exception
    • #770: Following the Eclipse versioning schema for OSGi
    • #736: Kura installer continues despite errors occurred
    • #725: Serial receive timeout is not forwarded to javax.comm.CommPort
    • #721: Unnecessary toggles eth0 interface when wlan0 interface is disabled on Raspberry Pi.
    • #696: FileServlet fails with NPE when there is no MetaTypeInformation
    • #688: Modify Kura Wires Web Copyright Header
    • #664: Misconfiguration of eth0 (as dhcp server) filling /var/log directory and finally crashing kura
    • #657: No ability to set security level with Bluetooth API
    • #556: Add WebSocket as alternative mqtt transport
    • #555: CAN bus bundle only supports 11-bit identifiers
    • #553: [Modbus] Refactoring of Modbus example
    • #550: [Modbus] String evaluation returns false
    • #476: Kura makes use of system properties when filtering for native code libraries which is not supported
    • #460: Upgrade Equinox to 3.11 and use Java 8 a minimum requirement
    • #372: [BLE] BluetoothGattImpl.getCharacteristics(String startHandle, String endHandle) and getServices() methods return empty list
    • #352: [Semantic Versioning] Enable analysis through bnd-baseline-maven-plugin
    • #288: [Modbus] Implement the MBAP header for TCP/IP communication
    • #244: [Web UI] Alphabetical ordering of metatype labels option in ListBoxes
  • Merged no issue-related Pull Requests:

    • #1370: Fixed connection status icon at page load.
    • #1365: Fixed deleted factory components not always being removed from snapshot (see also #1371)
    • #1364: Fixed factory components not being created from uploaded snapshot
    • #1352: Minor Wires fixes
    • #1350: Set security level to low
    • #1349: Changes to the emulator launch profiles used when cloning directly the repo
    • #1347: Modified emulator position.
    • #1344: Minor fixes regarding emulator.position and osgi.annotation.
    • #1343: Hidden export to CSV buttons from Wires Web UI
    • #1341: Modified Asset Cloudlet protocol
    • #1340: Fixed selinux check in kura-install.sh file.
    • #1339: Changes to have dev-env working.
    • #1337: Fixed watchdog service deactivate method
    • #1331: Switched equinox mirror.
    • #1323: Fixed handling of special characters in Wires DB
    • #1319: Moved Asset configuration constants and documentation out of the APIs.
    • #1311: Set the wire publisher qos metatype value to 0.
    • #1307: Add Everyware Cloud broker URL
    • #1302: Added opcua dp build step.
    • #1300: Fix modem driver code
    • #1289: Cleanup the payload encoder a bit
    • #1276: Asset cloudlet now starts immediately.
    • #1273: Watchdog code refactor and improvements
    • #1272: Improved performance of WireSupportImpl.emit()
    • #1266: Fixed unnecessary allocations by WireAsset
    • #1264: Heater demo example using Maven/BND.
    • #1256: Make private method static
    • #1238: Remove registration of service implementation classes
    • #1234: [Developer workspace] Updated project setup
    • #1227: Relax null handling, fix possible NPE, improve javadoc
    • #1226: Allow providing an input stream for reading XML content
    • #1224: Make it a functional interface
    • #1200: Add feature for Camel API
    • #1198: Changed wires component selection.
    • #1194: Fix iptables-restore run in background
    • #1192: WireEmitter/Receiver are ConsumerTypeS
    • #1184: Partially revert net.wifi breaking change
    • #1182: Removed timeout based on magic number.
    • #1179: Drop support for "fedorapi"
    • #1174: Switch default behavior to only track relevant services
    • #1173: OPC-UA Driver: Minor Fixes and Cleanup
    • #1168: Modified emulator launch.
    • #1154: Use window.parent instead of top in wires js and GWT parts
    • #1148: Enable JMX by default, allow overriding using system properties
    • #1144: [Developer workspace] Added 2 plugins and worspaces
    • #1143: Added support for enabling serial rx timeout
    • #1140: Improve separation of concerns for camel java example
    • #1136: Implement Kapua's applicationFramework/applicationFrameworkVersion
    • #1127: Changes to prevent exception of wires panel refresh.
    • #1122: Implement new Cloud Client API
    • #1115: Few more fixes in wires:
    • #1103: Added drag and drop support to the Wire Composer.
    • #1102: Improved drag and drop for Eclipse Marketplace.
    • #1099: Set of changes in EventHandlerServlet to prevent memory leak.
    • #1097: Check modem up in resetModem method
    • #1094: Modified jvm dependency.
    • #1090: Modified interval check in GwtNetworkServiceImpl.java.
    • #1088: Fixed Web Ui services search bar
    • #1086: OPC-UA Driver
    • #1085: Wires refactor 2
    • #1084: Wire Service Implementation and Wire Configuration Refactoring
    • #1083: Removing ThrowableUtil Reference
    • #1076: Wire publisher can publish control messages.
    • #1075: Fixed a few cases in Configuration Service where NPE could be thrown
    • #1074: Minor Code Fixes in PropertiesUi for Wires
    • #1073: Renamed asset cloudlet APP_ID to ASSET-V1.
    • #1070: Modified log message in ConfigurationServiceImpl.java
    • #1058: Wires related Web2 enhancements
    • #1047: Extracted WireHelperService and WireSupport together to a new bundle
    • #1043: Modified certificates policy in Cloud Service.
    • #1036: Solved graphical glitch in Assets' channel definition.
    • #1034: Fix a bunch of C code issues
    • #1031: Fix wire component provider
    • #1029: Fix a possible NPE in the Web UI
    • #1028: Work around Kura sending empty string instead of null for Camel deps
    • #1019: Fix private members
    • #1010: Updates and fixes for Karaf
    • #1005: Fix possible exception and service leak
    • #1002: Fix M2E errors when directly importing Karaf projects
    • #998: Fix wires nulls
    • #988: Removed references to windows bundles in 2.1.0.
    • #987: Modified web2 bundle packaging.
    • #986: Add Eclipse Kura Nexus repository in order to fix the build
    • #985: Switch version of SODA Comm to 1.2.4-SNAPSHOT
    • #982: Activate maven batch mode by default and reduce console log
    • #978: Uniformed build steps, corrected some typos.
    • #976: Changed deb dependency requiring java 8.
    • #953: Convert P2 repository to Maven 2 repository
    • #869: Clean up and document IOUtil
    • #868: Fix concurrency issue in command service
    • #803: add pcengine-nn profile

Known Issues (ESF):

  • ReliGATE 10-05 (All versions)
    • Rarely the Bind process can crash after client connection.
  • ReliGATE 10-05 (REGATE-10-05-34)
    • Modem: modem supports only SIMs that does not require authentication
    • Off-the-shelf instant activation/provisioning supported since Linux release WTL_20160809_1
    • Beacon scanner application supported since Linux release WTL_20160809_1
    • Modem: support limited to Ublox Lisa/Sara-U2
  • ReliGATE 10-05 (pre-production versions):
    • 256MB RAM option is totally unsupported
    • Modem: support limited to Ublox Lisa/Sara-U2
    • Modem: modem supports only SIMs that does not require authentication
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Beacon scanner application not supported (missing 'hcidump')
    • Wi-Fi WEP authentication is not reliable
  • ReliaGATE 10-10: Bluetooth Low Energy and WiFi in access point mode are mutually exclusive
  • ReliaGATE 10-10: Bluetooth Low Energy: the maximum number of concurrent connections is one
  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-10 (minigateway) and Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • The reference JVMs are:
    • ReliaGATE 10-05: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-11: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-20: Oracle Java SE Embedded 8u51
    • ReliaGATE 50-21: Oracle Java SE Embedded 7u40
    • ReliaGATE 20-25: Java SE Runtime Environment 8u92
      In order to take advantage of all the Red Hat Fuse features, the Embedded 8u51 JVM needs to be updated with the
      Nashorn jar available in the ESF downloads site.
  • #424: [Terminal Services] socat does not set tty parameters on the ReliaGATE 20-25
  • 423: [Terminal Services] socat resets the tty configuration on TCP client disconnect

    Workaround: set ts.net.allow.multiple.connections=false in TerminalServer(Service) configuration.
  • #278: [RG10-05] Failed to connect to OPC-UA server
  • #254: [20-26] No watchdog devices are exported on /dev
  • #251: [Net] DHCP client is not killed when an interface is disabled
  • #225: [20-26] Bluetooth 2.1 doesn't work on the device
  • #224: [20-26] GPIOs and LEDs are not available on the system
  • #223: [20-26] Serial ports are not available
  • #180: Unit connects then fails to connect because wlan0 is enabled for LAN
  • #167: [10-05] 2G modem option not supported by ESF
  • #160: [10-05] WiFi "device or resource busy" for a while after station mode reconfiguration
  • #144: [10-20] LE910 modem is not always detected by ESF at startup
  • #134: [10-05] On Ginevra ESF 4.0.0 includes Bluetooth support
  • #131: [10-05] On Ginevra ESF 4.0.0 installer overrides network settings
  • #126: [Terminal Server] The serial packets can be split in multiple tcp packets
  • #84: The PcnReportPublisher doesn't publish position info
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection failes.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • Web UI may hang when configuration snapshot is uploaded. This happens because HTTP connection is lost due to toggling of the network
    interface which happened even if network configuration hasn't been modified.
  • #1338: [Kura 3.0.0] camel.aggregation and camel.quickstart examples should be normalized
  • #1325: [Wires] Exception if an Channel Descriptor contains in Option of Integer type
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1197: [Net] Network configuration cannot be restored purely from snapshot
  • #1196: [Net] PPP password is not a (MetaType) Password
  • #1195: [Net] Firewall IP Forwarding rules entered in the Web UI lost on reboot
  • #1193: [Wires] Component avoidance during initial placement
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1092: Possible NPE and non-working check
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #948: [Kura 2.1.0 QA] NET-ETH0-014 Wrong lease time in DHCP mode
  • #923: [Kura 2.1.0 QA] eth0 search domain configuration and storage
  • #910: [Kura 2.1.0 QA] Unable to use WLAN as WAN interface
  • #890: [Kura 2.1.0 QA] Snapshot management in web UI
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #752: [DbDataStore] repair is very slow on big tables
  • #751: [DbDataStore] defrag and checkpoint are not per-table operations
  • #654: Clean up static initialization around "modem" functionality
  • #651: Call to "exit()" in native code
  • #650: Possible bug in "LinuxUdev.c"
  • #645: Clean up internal dependencies in Kura
  • #572: Unreadable errors in Web UI
  • #558: Update of DPs seems not to work
  • #547: [Configuration] Configuration Service may miss configuration-policy=optional components
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #520: [Net] PppFactory is not a factory and its design is wrong
  • #518: [Net] Modem monitor concurrency issue with multiple modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #362: Uninstaller leaves most of the files
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #311: [Multiple Cloud Connections] Spurious component reactivations upon configuration change
  • #307: CloudCallService overrides client ID
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation
  • #108: CloudCallServiceImpl - call methods setting requester.client.id to #client-id sends response to local device

Eurotech Everyware Software Framework ESF 4.1.0 (Eclipse Kura - 2.1.0)

Added Features (ESF):

  • RedHat Fuse integration
  • Logrotate feature integrated with Linux cron
  • Modified ESF specific monit scripts to include /etc/monit.d/ folder and configuration files
  • Added 20-26 support
  • Terminal client and server bundle is now included by default in all the distributions
  • Modbus protocol implementation is now included by default in all the distributions

Added Features (Kura):

  • Apache Camel Integration
  • New UI for Cloud Services
  • Support for Raspbian on Raspberry Pi 3
  • Support for Fedora on Raspberry Pi 2 and 3

Bug Fixes (ESF):

  • Fixed github issues:

    • #248: [Sec] ESF firewall rules bypassed with IPv6
    • #244: [10-05] Network interfaces file is wrong after recovering default configuration
    • #243: [ESF 4.1.0] Replace Apache Camel branding with Fuse
    • #237: [10-05]/[ALL] Minor typos on network interfaces when mouse hovers over "configure field"
    • #236: Enabling rx timeout from javax.comm.SerialPort crashes the JVM
    • #222: [20-26] The clock service is disabled, but the date is updated
    • #215: The com.eurotech.framework.terminal.client.server bundle is in the STARTING state.
    • #210: [20-26] Document ESF limitations due to legacy hardware not supported by RHEL 7.3
    • #209: [20-26] Create an ESF basic distribution for the 20-26 to establish a baseline
    • #208: [20-26] Install ESF dependencies on RHEL 7.3 on the ReliaGATE 20-25
    • #207: [20-26] Install RHEL 7.3 on the ReliaGATE 20-25 eMMC
    • #204: Add org.json back to ESF distribution
    • #202: Add bluetooth support for ESF on Fedora based distributions
    • #197: ESF overwrites /etc/sysctl.conf
    • #185: Add Terminal Client/Server and Modbus bundles to the distrib
    • #182: Broken dependencies on NN distributions
    • #179: [ProvisioningService] The service receives an un-merged configuration
    • #178: [10-05] WiFi driver crashes on switch between AP and Station mode
    • #177: [10-05] bind/named exits due to permission denied on /var/log/named.log
    • #175: [10-20] RS485 service activation confusing
    • #174: [10-11 Devkit] Provisioning Service still enabled after successful Instant Activation
    • #171: [10-05] Variable intermediate results when retrieving snapshots from ESF4.0.1
    • #170: ESF web console fails to refresh service panels after snapshot load
    • #169: Network configuration issue on RG 10-11
    • #161: [10-05] WiFi switch to Station mode tricky as network scanning is not supported in Access Point mode
    • #159: [10-05] WiFi switching between Station and Access Point is unreliable
    • #125: [Terminal Server] The serial packets are not passed unchanged to the tcp connection
    • #109: [QA] ESF 4.0 Test DEN-CLOCK-001, Clock service not turning off when directed
    • #100: [QA] ESF 4.0 test DEN-CONF-042, cannot cancel out of changes
    • #96: [QA] ESF 4.0 test CLD-SNAP-003, download xml not working
    • #90: Problem adding Open Port entry with unpermitted interface name
    • #88: [10-11 - Others?] HE910-DG - PPP link disconnects and never recovers (GPS is enabled)
    • #83: ESF Installer purges monitrc used by Linux for other purposes
    • #50: [20-25] Bluetooth 2.1 switching between modalies fails
    • #46: [Red Hat] Do we need a custom ESF 20-25 distribution for Red Hat?
    • #43: [Camel] Replace Kura Camel target platform bundles with commercially supported ones
    • #42: [50-21] logrotate improvement support
    • #41: [10-20] logrotate improvement support
    • #40: [10-11] logrotate improvement support
    • #39: [20-25] logrotate improvement support
    • #19: [20-25] Create distribution of ESF for RedHat Enterprise Linux
    • #14: [10-05] logrotate improvement support
  • Merged no issue-related Pull Requests:

    • #259: Modified firewall configuration opening avahi port 5353.
    • #258: Changes to have Fuse as dp for ETH gateways
    • #257: Enabled jcl over slf4j in dev-env
    • #249: Prevented cleanup of /tmp/.kura
    • #247: Provided RG 10-11 specific /etc/network/if-down.d/ifdown-local script to reset wireless interfaces
    • #246: Added code in decrypt aes.
    • #241: Fix target platform version
    • #238: Solved incompatibility with os x. Updated launch scripts.
    • #235: Fixed eth0 config for RG10-05 devkit
    • #233: Check oldlogs folder
    • #220: Fixed wrong jcl version reference.
    • #219: Added jcl.over.slf4j dependency
    • #217: Modified cloud service property device.display-name in snapshots
    • #216: Solved intermittent network availability.
    • #201: Modified codeminders.hidapi groupid reference.
    • #200: Fix PCN reset count
    • #196: Fix versioning of position service in Manifest.
    • #195: Publish position information
    • #194: [pcn] Fix bad return on CRC16 error.
    • #192: Bluetooth Example fixes and code cleanup
    • #191: Added dependency on commons-exec
    • #190: Updated ESF to remove JSON dependency
    • #184: Updated build to work with new slf4j version and fetching from maven central
    • #183: Fixed runnable stop in ProvisioningService
    • #138: Added protection code to prevent errors if gwt 0.2 bundle is not available

Bug Fixes (Kura):

  • Fixed github issues:

    • #958: [Kura 2.1.0 QA] Wrong labels in UI's DHCP&NAT configuration
    • #956: [Sec] Kura firewall rules bypassed with IPv6
    • #941: [Kura 2.1.0 QA] Raspberry Pi 3 no-net installer
    • #930: [Kura 2.1.0 QA] Problems with installation of Kura on BeagleBone Black
    • #917: [Kura 2.1.0 QA] Wrong range messages
    • #912: [Kura 2.1.0 QA] Exceptions while deploying example service
    • #909: [Kura 2.1.0 QA] SSID selection dialog too small
    • #903: [Kura 2.1.0 QA] Impossible to enter multiple DNS servers
    • #901: [Kura 2.1.0 QA] changing username/password locks out admin access
    • #900: [Kura 2.1.0 QA] usbutils missing in fedberry README
    • #895: [Kura 2.1.0 QA] Refreshing configuration in web UI
    • #893: [Kura 2.1.0 QA] GPIO example bundle configuration
    • #883: Invalid field validation state when switching from WAN to LAN
    • #879: [Kura 2.1.0 QA] Raspberry Pi 3 nameserver
    • #877: [Kura 2.1.0 QA] eth0 netmask configuration
    • #876: [Kura 2.1.0 QA] Disabling eth0 interface doesn't work properly
    • #874: [Kura 2.1.0 QA] eth0 DNS server configuration
    • #867: [Kura 2.1.0 QA] Ethernet interface gateway configuration on Raspberry Pi 3
    • #860: [Kura 2.1.0 QA] JUnit in Raspberry Pi 3's installation package
    • #859: [Kura 2.1.0 QA] Installation warnings/errors on Raspberry Pi 3
    • #851: [Web-UI] Label is sent instead of value for metatype parameters with options
    • #835: [Kura 2.1.0] Bind/Named service doesn't work properly on Fedora
    • #793: [Kura 2.1.0] QA for the User Workspace
    • #776: Serialization issue in cloud window
    • #767: Change Housekeeping schedule from scheduleAtFixedRate to scheduleWithFixedDelay
    • #753: libhidapi not correctly compiled for armv5
    • #743: WLAN not detected as WLAN on Fedberry
    • #742: Unable to establish stable network connection on Fedberry
    • #732: Unable to configure CloudService instance when component gets unregistered
    • #724: [Release 2.1.0] Check API packages
    • #716: Create a simple Camel Java DSL based example publisher
    • #692: Drop default to 255 characters on data entry
    • #691: NPE when CloudService isn't configured
    • #683: Control Prefix in Request/Response
    • #660: [kura-build] jdk.dio deployment fails in Hudson
    • #649: Missing copyright headers
    • #642: Raspbian Pi3
    • #641: [Camel] KuraCloudConsumer - Failed to subscribe exception
    • #640: [Modem] NoClassDefFoundError: Could not initialize class org.eclipse.kura.linux.net.modem.SupportedUsbModems
    • #635: ExecCommand in org.eclipse.kura.linux.bluetooth.BluetoothAdapterImpl Index Out Of Bounds
    • #627: Fix Bundle-Vendor to "Eclipse Kura"
    • #619: Duplicate version of maven-antrun-plugin
    • #618: Recent CR/LF fix causes 182 file modification pending
    • #613: Recent addition of checkstyle fails the build
    • #603: Can "json 20090211" be removed?
    • #599: WebUI fails completely is PositionService is not registered
    • #596: Replace all calls to ConfigurationAdmin.getConfiguration(String)
    • #595: ComponentMetaTypeBundleTracker is processing every bundle twice on startup
    • #592: Again Java 7 code in BREE 6 bundle
    • #589: [Camel] Camel related exceptions on Kura startup
    • #581: Missing Package Info in few packages in API Bundle
    • #573: Commit 41c3180 breaks data entry
    • #571: Convert files from dos 2 unix format
    • #564: [Configuration] ConfigurationService doesn't set properly the kura.service.pid
    • #562: Services UI not getting updated with new properties
    • #557: Add SLF4J jcl-over-slf4j
    • #548: Kura 2 Webui on BeagleboneBlack Problem
    • #544: Web UI shows red-connector although state is CONNECTED
    • #540: [Web UI] Empty Integer field in a configuration (not required) is causing a NumberFormatException
    • #539: [Cloud] Required changes in CloudServiceFactory
    • #521: Device -> Threads shows empty list
    • #515: [Web UI] Implement Cloud Services UI
    • #511: Upgrade SLF4J to 1.7.21
    • #509: [Web 2] ServicesUi validation
    • #497: SystemServiceImpl uses method from Java 7 but declares a BREE of Java 6
    • #496: mToolkit Eclipse Plugin does not work under Eclipse Neon
    • #488: Command cloud App Null Pointer Exception
    • #485: Change b02bc9a7615ca559349f2b05485ea84fd80d6e77 breaks deployment of "sun.misc" bundles
    • #473: org.eclipse.kura.linux.net.modem.ModemDriver uses Java 7 API but has BREE of Java 6
    • #467: Web UI cannot handle Integer with cardinality 0/optional
    • #465: CloudService.isConnected not shown in Web UI
    • #461: Registering a component which has a PID without dot crashes the Web UI 2
    • #451: setting a payload metric to null should throw an exception immediately
    • #444: Multiple Cloud Support - Web UI does not allow to select new installed cloud service
    • #419: Migrate ASF camel-kura code to Eclipse
    • #403: Fix javadoc for the getKuraVersion() method of the SystemService.
    • #396: iwScanTool fails to parse scan results
    • #343: [Web2]: Setting the "name" property to anything different than the "id" sets an empty value
    • #342: [Configuration] Support multiple configurations for SelfConfiguringComponentS
    • #339: [Web UI] The Disconnect button in the Status menu disconnects all connections
    • #337: [Web2]: Field validation errors not shown
    • #326: org.eclipse.kura.web2 is missing about.html
    • #321: No support for systemd based systems
    • #318: There should be Oomph based setups for Kura
    • #315: The Kura documentation should mention the default login credentials admin/admin
    • #314: The Camel Quickstart example is not working
    • #281: Add XML routes configuration per Camel CloudService
    • #265: Camel Examples: review
    • #262: Maven failure when dev-env isn't built
    • #257: KuraComponent can't resolve its collaborators
    • #234: [Web UI] web2 network configuration glitch
    • #231: Create Maven plugin capable of wrapping regular bundles in DP packages
    • #221: [Camel] Do we need a Camel API in the org.eclipse.kura.api bundle?
    • #216: [Test] Test Kura on RaspberryPi 3
    • #205: All languages from Camel Core should be loaded by CamelRouter
    • #204: All data formats from Camel Core should be loaded by CamelRouter
    • #189: [Camel] Camel integration in the Kura CloudService
    • #119: [Camel] Migrate CamelRouter tests from Rhiot to Kura
  • Merged no issue-related Pull Requests:

    • #962: Added libudev for rhel based devices
    • #928: [Web-Ui] Fixed typo in the network config section
    • #898: Solved modem reset failure.
    • #855: Modified wrong entry in snapshot 0s
    • #816: Set the 'kura.ui.service.hide' property
    • #810: Remaining changes to Camel Web UI
    • #805: Prepend kura- to modem log files.
    • #802: Try a fix for the startup exception, missing "kura-cloud"
    • #798: Add Fedora 24 based ARM7 native library
    • #765: Reverts change in commit 7704d180296551b0acb68044f7cd6b4c3e77f56a
    • #761: Allow camel component to be initialized
    • #756: Allow Camel modules to gracefully handle missing dependencies
    • #755: Allow automatic conversion from Map to KuraPayload
    • #745: Solved possible IllegalArgumentException due to null pid
    • #744: Fixed wifi scan in AP mode
    • #739: Solved possible 404 error when downloading snapshot
    • #730: WiFi switching between Station and Access Point is unreliable
    • #720: Fix wifi issues 2.1.0
    • #717: Lower camel imports to 2.17.0
    • #700: Fix Watchdog disabling bug in WatchdogService.
    • #699: Add DependencyManagement to Camel Examples
    • #698: Fix ble process leak
    • #697: Export ConfigurableComponent in service xml
    • #694: Fix Camel imports
    • #662: Implement a workaround for issue #590
    • #643: Clean up imports for Camel
    • #630: Minor cleanups to the Linux ClockServiceImpl
    • #625: Kura should not publish modified artifacts under "org.eclipse" namespace
    • #624: Let example services export ConfigurableComponent
    • #607: Start the Web UI component immediately
    • #605: Fix a few resource leaks
    • #602: Initial support for building a version for PC Engines APU / Debian 8
    • #594: Implement missing method 'unsetSystemService'
    • #578: Cleanup dead code
    • #563: clean up some source code issues
    • #560: Fixed bug on ConfigurationService about kura.service.pid
    • #552: Support for RPi running Fedora via Fedberry, Pidora, etc.
    • #546: Minor fixes for the startup scripts
    • #542: Re-use existing code to parse kura.properties
    • #530: Fix service leak in ComponentUtil
    • #528: Fix the lookup of the default value, now done by id.
    • #513: Follow Eclipse trademark guidelines
    • #508: Refactor Camel router
    • #501: Enh build deploy

Known Issues (ESF):

  • ReliGATE 10-05 (All versions)
    • Rarely the Bind process can crash after client connection.
  • ReliGATE 10-05 (REGATE-10-05-34)
    • Modem: modem supports only SIMs that does not require authentication
    • Off-the-shelf instant activation/provisioning supported since Linux release WTL_20160809_1
    • Beacon scanner application supported since Linux release WTL_20160809_1
    • Modem: support limited to Ublox Lisa/Sara-U2
  • ReliGATE 10-05 (pre-production versions):
    • 256MB RAM option is totally unsupported
    • Modem: support limited to Ublox Lisa/Sara-U2
    • Modem: modem supports only SIMs that does not require authentication
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Beacon scanner application not supported (missing 'hcidump')
    • Wi-Fi WEP authentication is not reliable
  • ReliaGATE 10-10: Bluetooth Low Energy and WiFi in access point mode are mutually exclusive
  • ReliaGATE 10-10: Bluetooth Low Energy: the maximum number of concurrent connections is one
  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-10 (minigateway) and Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • The reference JVMs are:
    • ReliaGATE 10-05: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-11: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-20: Oracle Java SE Embedded 8u51
    • ReliaGATE 50-21: Oracle Java SE Embedded 7u40
    • ReliaGATE 20-25: Java SE Runtime Environment 8u92
      In order to take advantage of all the Red Hat Fuse features, the Embedded 8u51 JVM needs to be updated with the
      Nashorn jar available in the ESF downloads site.
  • #254:[20-26] No watchdog devices are exported on /dev
  • #251:[Net] DHCP client is not killed when an interface is disabled
  • #225:[20-26] Bluetooth 2.1 doesn't work on the device
  • #224:[20-26] GPIOs and LEDs are not available on the system
  • #223:[20-26] Serial ports are not available
  • #180:Unit connects then fails to connect because wlan0 is enabled for LAN
  • #177:[10-05] bind/named exits due to permission denied on /var/log/named.log
  • #167:[10-05] 2G modem option not supported by ESF
  • #160:[10-05] WiFi "device or resource busy" for a while after station mode reconfiguration
  • #144:[10-20] LE910 modem is not always detected by ESF at startup
  • #134:[10-05] On Ginevra ESF 4.0.0 includes Bluetooth support
  • #131:[10-05] On Ginevra ESF 4.0.0 installer overrides network settings
  • #126:[Terminal Server] The serial packets can be split in multiple tcp packets
  • #84: The PcnReportPublisher doesn't publish position info
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles

Know Issues (Kura):

  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Kura can be run in a Java 8 VM, but current OSGi container does not support bundles with manifests that specify
    a "Bundle-RequiredExecutionEnvironment" equal to "JavaSE-1.8".
  • The old GPS position will continue to be shown in the status overview even after the disabling of the static position reporting.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection failes.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • Web UI may hang when configuration snapshot is uploaded. This happens because HTTP connection is lost due to toggling of the network
    interface which happened even if network configuration hasn't been modified.
  • #948: [Kura 2.1.0 QA] NET-ETH0-014 Wrong lease time in DHCP mode
  • #923: [Kura 2.1.0 QA] eth0 search domain configuration and storage
  • #918: [Kura 2.1.0 QA] DEN-POS-002 Position service keeps reporting old position
  • #916: [Kura 2.1.0 QA] DEN-CONF-005 Wrong range limit for "long"
  • #915: [Kura 2.1.0 QA] DEN-CONF-005: Internal message when a "too big" number is entered
  • #914: [Web UI] Fixed fields can be edited
  • #911: [Kura 2.1.0 QA] SSID selection not always shows all SSIDs
  • #910: [Kura 2.1.0 QA] Unable to use WLAN as WAN interface
  • #908: [Kura 2.1.0 QA] Web UI shows its own WLAN for connecting
  • #890: [Kura 2.1.0 QA] Snapshot management in web UI
  • #889: [Kura 2.1.0 QA] Denali Configuration ExamplePublisher error descriptions
  • #778: [Net] Refactor needed in org.eclipse.kura.core.net
  • #752: [DbDataStore] repair is very slow on big tables
  • #751: [DbDataStore] defrag and checkpoint are not per-table operations
  • #737: Fedora distribution fails to start up
  • #736: Kura installer continues despite errors occurred
  • #725: Serial receive timeout is not forwarded to javax.comm.CommPort
  • #721: Unnecessary toggles eth0 interface when wlan0 interface is disabled on Raspberry Pi.
  • #696: FileServlet fails with NPE when there is no MetaTypeInformation
  • #664: Misconfiguration of eth0 (as dhcp server) filling /var/log directory and finally crashing kura
  • #654: Clean up static initialization around "modem" functionality
  • #651: Call to "exit()" in native code
  • #650: Possible bug in "LinuxUdev.c"
  • #645: Clean up internal dependencies in Kura
  • #572: Unreadable errors in Web UI
  • #558: Update of DPs seems not to work
  • #553: [Modbus] Refactoring of Modbus example
  • #550: [Modbus] String evaluation returns false
  • #547: [Configuration] Configuration Service may miss configuration-policy=optional components
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #520: [Net] PppFactory is not a factory and its design is wrong
  • #518: [Net] Modem monitor concurrency issue with multiple modems
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #362: Uninstaller leaves most of the files
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #311: [Multiple Cloud Connections] Spurious component reactivations upon configuration change
  • #307: CloudCallService overrides client ID
  • #297: [Status led] What connection instance controls the status led?
  • #288: [Modbus] Implement the MBAP header for TCP/IP communication
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #235: LinuxNetworkUtil#toolExists() should check for tool's existence in PATH
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation
  • #172: Modem: manually killing pppd with Kura running never triggers a modem reset
  • #108: CloudCallServiceImpl - call methods setting requester.client.id to #client-id sends response to local device
  • #104: org.eclipse.kura.linux.net.ConnectionInfoImpl is IPv4 only

Eurotech Everyware Software Framework ESF 4.0.2 (Eclipse Kura - 2.0.2)


Bug Fixes (ESF):
Merged no issue-related Pull Requests:
#189: Provided RG 10-11 specific /etc/network/if-down.d/ifdown-local script to reset wireless interfaces

Bug Fixes (Kura):
Merged no issue-related Pull Requests:
#653: Hotfixes for WiFi for the 2.0.2 service release. This addresses
Kura not restarting hostapd if the service has stopped for some reason.
* #652: This is a hotfix for a process leak in Bluetooth LE when calling hcidump.

Known Issues (ESF):
ReliGATE 10-05 (REGATE-10-05-34)
Modem: modem supports only SIMs that does not require authentication
Off-the-shelf instant activation/provisioning supported since Linux release WTL_20160809_1
Beacon scanner application supported since Linux release WTL_20160809_1
Modem: support limited to Ublox Lisa/Sara-U2
ReliGATE 10-05 (pre-production versions):
256MB RAM option is totally unsupported
Modem: support limited to Ublox Lisa/Sara-U2
Modem: modem supports only SIMs that does not require authentication
High CPU usage if SD card is not inserted
Off-the-shelf instant activation/provisioning not supported
Beacon scanner application not supported (missing 'hcidump')
Wi-Fi WEP authentication is not reliable
ReliaGATE 10-10: Bluetooth Low Energy and WiFi in access point mode are mutually exclusive
ReliaGATE 10-10: Bluetooth Low Energy: the maximum number of concurrent connections is one
Release only validated against the HE910 version of the ReliaCELL
ReliaCELL Dual SIM option not supported
Hardware watchdog: not implemented on all platforms
Reliagate 50-21: Using eth1 and Windows 7 to access the webui
does not work over some network topologies - OSX or Linux are recommended
to access the webui in this rare case
When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
Network Administration panel on the WebUI
Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
On Reliagate 10-10 (minigateway) and Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
The reference JVMs are:
ReliaGATE 10-05: Oracle Java SE Embedded 8u51
ReliaGATE 10-11: Oracle Java SE Embedded 8u51
ReliaGATE 10-20: Oracle Java SE Embedded 8u51
ReliaGATE 50-21: Oracle Java SE Embedded 7u40
ReliaGATE 20-25: Java SE Runtime Environment 8u92
#167: [10-05] 2G modem option not supported by ESF
#161: [10-05] WiFi switch to Station mode tricky as network scanning is not supported in Access Point mode
#160: [10-05] WiFi "device or resource busy" for a while after station mode reconfiguration
#159: [10-05] WiFi switching between Station and Access Point is unreliable
#144: [10-20] LE910 modem is not always detected by ESF at startup
#134: [10-05] On Ginevra ESF 4.0.0 includes Bluetooth support
#131: [10-05] On Ginevra ESF 4.0.0 installer overrides network settings
#126: [Terminal Server] The serial packets can be split in multiple tcp packets
#125: [Terminal Server] The serial packets are not passed unchanged to the tcp connection
#88: [10-11 - Others?] HE910-DG - PPP link disconnects and never recovers (GPS is enabled)
#84: The PcnReportPublisher doesn't publish position info
#81: [Security - Message Signing] ESF verifies the signature of every control message
#64: Message signature propagated to application bundles
#50: [20-25] Bluetooth 2.1 switching between modalies fails

Know Issues (Kura):
Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
"Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
(crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
gatttool and the BLE connection failes.
WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
AccessPoint WiFi mode not working for Broadcom chipset.
Hardware watchdog: not implemented on all platforms
Only one WAN interface is currently supported. A warning in displayed
in the WEB UI if the user attempts to enable more than one WAN interface
Web UI may hang when configuration snapshot is uploaded. This happens because HTTP connection is lost due to toggling of the network
interface which happened even if network configuration hasn't been modified.
#467: Web UI cannot handle Integer with cardinality 0/optional
#465: CloudService.isConnected not shown in Web UI
#462: ConfigurationServiceImpl cannot handle cardinality >1 for SelfConfiguringComponent
#461: Registering a component which has a PID without dot crashes the Web UI 2
#444: Multiple Cloud Support - Web UI does not allow to select new installed cloud service
#396: iwScanTool fails to parse scan results
#362: Uninstaller leaves most of the files
#355: [Semantic Versioning] org.eclipse.kura.net.wifi version should be increased from 1.2.0 to 1.3.0
#343: [Web2]: Setting the "name" property to anything different than the "id" sets an empty value
#339: [Web UI] The Disconnect button in the Status menu disconnects all connections
#337: [Web2]: Field validation errors not shown
#329: [DEPLOY-V2] Review/refactoring needed
#314: The Camel Quickstart example is not working
#311: [Multiple Cloud Connections] Spurious component reactivations upon configuration change
#307: CloudCallService overrides client ID
#299: On Red Hat Fedora, network-scripts can contain double quotes
#297: [Status led] What connection instance controls the status led?
#288: [Modbus] Implement the MBAP header for TCP/IP communication
#262: Maven failure when dev-env isn't built
#257: KuraComponent can't resolve its collaborators
#253: Check if bundle contexes correctly unget services after invoking getService
#235: LinuxNetworkUtil#toolExists() should check for tool's existence in PATH
#234: [Web UI] web2 network configuration glitch
#224: Fixed modem reset and kura restart issues for gps
#222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation
#174: Networking: check why sometimes eth0 is toggled on wlan0 reconfiguration
#172: Modem: manually killing pppd with Kura running never triggers a modem reset
#108: CloudCallServiceImpl - call methods setting requester.client.id to #client-id sends response to local device
#104: org.eclipse.kura.linux.net.ConnectionInfoImpl is IPv4 only
#77: Data Service will not connect for other locale than an english one

Eurotech Everyware Software Framework ESF 4.0.1 (Eclipse Kura - 2.0.1)

Bug Fixes (ESF):

  • Fixed github issues:

    • #143: [10-05] [Clarizen B-24502] NullPointerException in the findNetInterfaceConfigurations() method of the GwtNetworkServiceImpl class.
    • #129: [10-05] Verbose logging enabled in JDK DIO
    • #119: [20-25] Base GPIO value changed with latest Linux image
    • #113: [20-25] Missing serial port names in RX-TX config file
    • #110: [QA] ESF 4.0 test CLD-COMMAND-001 - command results not properly in scrollable window
    • #108: [QA] ESF 4.0 test DEN-SNAP-002, roll back not working
    • #107: [QA] ESF 4.0 Field Validation for broker URL under MQTTDataTransport doesn't update after putting accurate value
    • #104: ESF not able to boot due to empty snapshot file
    • #103: [QA] ESF 4.0 test DEN-SNAP-001, clicking Apply makes System tabs fail to display their window
    • #93: [JVM] -Xss128k may be too low
    • #87: [MqttDataTransport] Set the Paho persistence in memory by default for all the supported platforms
    • #86: [HSQLDB] Set DB in-memory by default for all supported platforms
    • #85: The jdk.dio.properties file for the RG 10-20 is not user friendly.
    • #82: ESF Installer potentially purges Linux packages incorrectly
    • #80: [10-20] Add missing gpios on jdk.dio.properties file
  • Merged no issue-related Pull Requests:

    • #166: Force update of API and bluetooth bundles on 10-11.
    • #164: Update version on org.eclipse.kura.bluetooth version.
    • #162: Modified watchdog reference to meet new Linux requirements.
    • #137: All ESF supported platforms now will use javax.comm. Implemented a better management of replace.dkcomm flag. Camel bundles will be not part of next ESF release.
    • #133: Changed GPIO reference in kura.properties file to meet new firmware requirements.
    • #120: Modified the status_led gpio. Added check to skip ESF install when Linux kernel version is older than 3.14.62ltsi-yocto-standard

Bug Fixes (Kura):

  • Fixed github issues:

    • #473: org.eclipse.kura.linux.net.modem.ModemDriver uses Java 7 API but has BREE of Java 6
    • #468: [Web] NPE in GwtNetworkServiceImpl
    • #464: Beaglebone install script not creating /etc/sysconfig
    • #393: [NN] NN profiles are broken in Kura 2.0.0
    • #373: Kura 2.0.0 distribution for Raspberry-Pi includes emulator.gpio instead of linux.gpio
    • #340: [Configuration] Metatype not updated in the Web UI
    • #338: [Web2]: String input forced to a maximum length of 255
    • #316: Debian package should declare dependency on java
    • #296: [Web UI] Status | Connection: if the connection username is not set, "null" is shown
    • #290: [Web UI] Refresh button in network configuration deselects the currently selected interface
    • #289: [Web UI] Wireless Password disappears after verification
    • #275: [Dev Env] Add org.eclipse.kura.linux.bluetooth to the target-platform.
    • #242: [Web UI] Help is not always visible in the new web ui
  • Merged no issue-related Pull Requests:

    • #489: Modified check for crypto value in isDefaultPassword.
    • 484: Modified wrong references in some snapshots, modified sslManager service to perform a

        different check for the default password and the password change.
      
    • #483: Modified launch configurations.
    • #480: Fix firewall issues
    • #475: Hotfix ble fixes
    • #441: JDK DIO: disable verbose logging from armv5_sf and x86_64 libraries.
    • #440: Modified the configuration service to prevent the generation of empty snapshots.
    • #439: Refactored code, modified behavior with gpio calculation from base address + offset.
    • #438: Added more checks in ServicesUI to prevent possible exception. Removed servicesUi refresh at every click in status section.
    • #431: Fix missing license headers
    • #428: Fix missing camel bundle in dev workspace
    • #417: Fix logging of exceptions and clean up other logging calls
    • #404: Fix a possible NPE followed by a NCDFE when system property is missing
    • #402: Fix two NullPointerExceptions and improve the error output
    • #400: Fix build warnings
    • #395: Remove dependency on slf4j-log4j12
    • #388: Modified snapshot_0s in order to have memory persistance for in-flight messages.
    • #382: Use a copy-on-write list in order to support concurrent modifications
    • #361: Use Import-Package in preference of Require-Bundle
    • #351: Pom cleanup
    • #347: Reset the original state of the accessible flag
    • #346: Clean up the error output to actually print out stack traces
    • #336: Corrected jacoco version due to build failure in JDK8
    • #328: Fix output of executed commands
    • #325: Fix a possible Context Class Loader leak
    • #320: Provide Oomph setup and clean up build issue

Known Issues (ESF):

  • ReliGATE 10-05 (REGATE-10-05-34)
    • Modem: modem supports only SIMs that does not require authentication
    • Off-the-shelf instant activation/provisioning supported since Linux release WTL_20160809_1
    • Beacon scanner application supported since Linux release WTL_20160809_1
    • Modem: support limited to Ublox Lisa/Sara-U2
  • ReliGATE 10-05 (pre-production versions):
    • 256MB RAM option is totally unsupported
    • Modem: support limited to Ublox Lisa/Sara-U2
    • Modem: modem supports only SIMs that does not require authentication
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Beacon scanner application not supported (missing 'hcidump')
    • Wi-Fi WEP authentication is not reliable
  • ReliaGATE 10-10: Bluetooth Low Energy and WiFi in access point mode are mutually exclusive
  • ReliaGATE 10-10: Bluetooth Low Energy: the maximum number of concurrent connections is one
  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-10 (minigateway) and Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • The reference JVMs are:
    • ReliaGATE 10-05: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-11: Oracle Java SE Embedded 8u51
    • ReliaGATE 10-20: Oracle Java SE Embedded 8u51
    • ReliaGATE 50-21: Oracle Java SE Embedded 7u40
    • ReliaGATE 20-25: Java SE Runtime Environment 8u92
  • #167: [10-05] 2G modem option not supported by ESF
  • #161: [10-05] WiFi switch to Station mode tricky as network scanning is not supported in Access Point mode
  • #160: [10-05] WiFi "device or resource busy" for a while after station mode reconfiguration
  • #159: [10-05] WiFi switching between Station and Access Point is unreliable
  • #144: [10-20] LE910 modem is not always detected by ESF at startup
  • #134: [10-05] On Ginevra ESF 4.0.0 includes Bluetooth support
  • #131: [10-05] On Ginevra ESF 4.0.0 installer overrides network settings
  • #126: [Terminal Server] The serial packets can be split in multiple tcp packets
  • #125: [Terminal Server] The serial packets are not passed unchanged to the tcp connection
  • #88: [10-11 - Others?] HE910-DG - PPP link disconnects and never recovers (GPS is enabled)
  • #84: The PcnReportPublisher doesn't publish position info
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles
  • #50: [20-25] Bluetooth 2.1 switching between modalies fails

Know Issues (Kura):

  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection failes.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • Web UI may hang when configuration snapshot is uploaded. This happens because HTTP connection is lost due to toggling of the network
    interface which happened even if network configuration hasn't been modified.
  • #467: Web UI cannot handle Integer with cardinality 0/optional
  • #465: CloudService.isConnected not shown in Web UI
  • #462: ConfigurationServiceImpl cannot handle cardinality >1 for SelfConfiguringComponent
  • #461: Registering a component which has a PID without dot crashes the Web UI 2
  • #444: Multiple Cloud Support - Web UI does not allow to select new installed cloud service
  • #396: iwScanTool fails to parse scan results
  • #362: Uninstaller leaves most of the files
  • #355: [Semantic Versioning] org.eclipse.kura.net.wifi version should be increased from 1.2.0 to 1.3.0
  • #343: [Web2]: Setting the "name" property to anything different than the "id" sets an empty value
  • #339: [Web UI] The Disconnect button in the Status menu disconnects all connections
  • #337: [Web2]: Field validation errors not shown
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #314: The Camel Quickstart example is not working
  • #311: [Multiple Cloud Connections] Spurious component reactivations upon configuration change
  • #307: CloudCallService overrides client ID
  • #299: On Red Hat Fedora, network-scripts can contain double quotes
  • #297: [Status led] What connection instance controls the status led?
  • #288: [Modbus] Implement the MBAP header for TCP/IP communication
  • #262: Maven failure when dev-env isn't built
  • #257: KuraComponent can't resolve its collaborators
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #235: LinuxNetworkUtil#toolExists() should check for tool's existence in PATH
  • #234: [Web UI] web2 network configuration glitch
  • #224: Fixed modem reset and kura restart issues for gps
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation
  • #174: Networking: check why sometimes eth0 is toggled on wlan0 reconfiguration
  • #172: Modem: manually killing pppd with Kura running never triggers a modem reset
  • #108: CloudCallServiceImpl - call methods setting requester.client.id to #client-id sends response to local device
  • #104: org.eclipse.kura.linux.net.ConnectionInfoImpl is IPv4 only
  • #77: Data Service will not connect for other locale than an english one

Eurotech Everyware Software Framework ESF 4.0.0 (Eclipse Kura - 2.0.0)

Added Features (ESF):

  • Added complete 10-05 support, only for 512 MB boards
  • Added complete support for 20-25 gateways
  • Added Dev-Kit configuration support
  • Recompiled native libraries to support x86_64 platforms

Added Features (Kura):

  • Added support for multiple connections
  • Added support for Wi-Fi Multi Mode
  • Created a new web UI bundle named org.eclipse.kura.web2 that integrates GWT 2.7 and GwtBootstrap 3 technologies
  • Updated bluetooth APIs and added support for Bluez 5.x
  • Initial integration of RedHat's Camel stack
  • Created a Kura applications section inside the Eclipse marketplace and added support in the local web UI for the application
    install via drag-and-drop
  • Created SenseHat example project
  • Updated the SensorTag Example project exposing buzzer and leds
  • Created the beacon.scanner project
  • Native libraries now support x86_64
  • Reviewed/refactored the GPS position service

Bug Fixes (ESF):

  • Fixed github issues #15, #16, #18, #21, #37, #44, #48, #51, #52, #54, #58, #61, #66

Bug Fixes (Kura):

  • Fixed github issues #78, #82, #96, #98, #112, #113, #114, #116, #120, #121, #127, #128, #129, #131,
    #134, #138, #139, #141, #143, #167, #169, #177, #179, #182, #184, #187, #188, #193, #198, #199, #201,
    #202, #203, #209, #212, #214, #215, #218, #227, #228, #229, #230, #233, #238, #241, #250, #252, #254,
    #255, #256, #258, #260, #267, #270, #271, #272, #279, #284

Known Issues (ESF):

  • ReliGATE 10-05:
    • Modem: support limited to Ublox Lisa/Sara-U2
    • Modem: modem supports only SIMs that does not require authentication
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Beacon scanner application not supported
    • Wi-Fi WEP authentication is not reliable
  • ReliGATE 20-25:
    • Bluetooth 2.1 is not fully supported
  • ReliaGATE 10-10: Bluetooth Low Energy and WiFi in access point mode are mutually exclusive
  • ReliaGATE 10-10: Bluetooth Low Energy: the maximum number of concurrent connections is one.
  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-10 (minigateway) and Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")

Known Issues (Kura):

  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux". Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on gatttool and the BLE connection fails.
    The only working version of BlueZ is 4.101. The deb package is not available from Raspbian so it
    must be compiled from sources.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • The reference JVMs are Oracle Java SE Embedded version 7 Update 40 and Java SE Embedded version 8 Update 65.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • Web UI may hang when configuration snapshot is uploaded. This happens because HTTP connection is lost due to toggling of the network interface which happened even if network configuration hasn't been modified.

Eurotech Everyware Software Framework ESF 3.3.1 (Eclipse Kura - 1.4.0)

Bug Fixes (ESF):

  • Security-related fixes and improvements
  • Fixed missing RS485 bundle in Reliagate 10-11.

Known Issues (ESF):

  • ReliGATE 10-05:
    • Modem: support limited to Ublox SARA-U2
    • Modem: modem reset might fail
    • WiFi: switching between Access Point and Infrastructure mode not reliable
    • WiFi: poor performance in Infrastructure (Station) mode
    • Web UI is sluggish due to the above WiFi issues
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Login password not set
    • Bluetooth firmware programming unreliable
  • ReliaGATE 10-10: Bluetooth Low Energy and WiFi in access point mode are mutually exclusive
  • ReliaGATE 10-10: Bluetooth Low Energy: the maximum number of concurrent connections is one.
  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-10 (minigateway) and Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")

Known Issues (Kura):

  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux". Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on gatttool and the BLE connection failes.
    The only working version of BlueZ is 4.101. The deb package is not available from Raspbian so it
    must be compiled from sources.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipest.
  • The reference JVMs are Oracle Java SE Embedded version 7 Update 40 and Java SE Embedded version 8 Update 65.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • Web UI may hang when configuration snapshot is apploaded. This happens because HTTP connection is lost due to toggling of the network interface which happened even if network configuration hasn't been modified.

Eurotech Everyware Software Framework ESF 3.3.0 (Eclipse Kura - 1.4.0)

Added Features (ESF):

  • Added support for the ReliaGATE 10-11
  • Added initial support for the ReliaGATE 10-05 (early-access, see the 'Known Issues' section below)
  • Smaller incremental upgrades using 'jardiff'. Granularity changed from OSGi bundle to Java class
  • Improvements to the Development Environment
  • Enabled Eurotech Cloud device instant activation for ReliaGATE 10-20 and ReliaGATE 10-11

Added Features (Kura):

  • Grouped Web UI SSL configuration in a single place under 'Settings'
  • Modified the Web UI adding a check in order to block SSIDs longer than 32 characters
  • Rolled-back Web UI filtering of SSID
  • Added some security headers to the Web UI
  • Refactored security related tabs in the Web UI
  • Added property to the WatchdogService to specify the watchdog device
  • Modified build in order to include checks for Java 8 compact 2 compliance
  • Introduced new deployment application (named DEPLOY-V2) that improves updates download from the cloud platform
  • New firewall management, now based on iptables-save and iptables-restore
  • Firewall: allowed open port entries for tcp and udp on the same port
  • Firewall: enabled the support for port ranges when defining open port entries
  • Added support for Ublox SARA-U2 modem
  • Added support to switch between AP and station mode on radios supported by the 'bcmdhd' kernel module
  • Emulator bundle split into 6 separate bundles, one for each function
  • Reviewed no-network profiles: removed net.admin bundle and linux.net. Now those bundles are replaced by emulator.net
  • Linux build date/version is now published in the birth certificate as part of the os.version metric
  • Improvements to the Development Environment
  • ConfigurationService: treat an OSGi ManagedService as a ConfigurableComponent
  • Updated documentation

Bug Fixes (ESF):

  • Fixed permissions for scripts and executables installed by ESF
  • Several fixes to the PCN bundle configuration update
  • Security-related fixes and improvements

Bug Fixes (Kura):

  • Fixed github issue #80
  • Fixed github issue #84
  • Fixed github issue #85
  • Fixed github issue #87
  • Fixed configuration rollback to snapshot 0
  • Fixed toggling WiFi interface when Ethernet interface is reconfigured
  • Better Web UI exception handling when manually (dis)connecting to the Cloud
  • Added various null pointer checks
  • Started work to fix warnings emitted by Sonar
  • Fixed JUnit tests
  • Fixed GPIO example
  • Fixed bug when image in metatype has no size
  • Fixed and improved the BLE TI SensorTag example

Known Issues (ESF):

  • ReliGATE 10-05:
    • Modem: support limited to Ublox SARA-U2
    • Modem: modem reset might fail
    • WiFi: switching between Access Point and Infrastructure mode not reliable
    • WiFi: poor performance in Infrastructure (Station) mode
    • Web UI is sluggish due to the above WiFi issues
    • High CPU usage if SD card is not inserted
    • Off-the-shelf instant activation/provisioning not supported
    • Login password not set
    • Bluetooth firmware programming unreliable
  • ReliaGATE 10-10: Bluetooth Low Energy and WiFi in access point mode are mutually exclusive
  • ReliaGATE 10-10: Bluetooth Low Energy: the maximum number of concurrent connections is one.
  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.
  • On Reliagate 10-10 (minigateway) and Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")

Known Issues (Kura):

  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux". Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on gatttool and the BLE connection failes.
    The only working version of BlueZ is 4.101. The deb package is not available from Raspbian so it
    must be compiled from sources.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipest.
  • The reference JVMs are Oracle Java SE Embedded version 7 Update 40 and Java SE Embedded version 8 Update 65.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.
  • Web UI may hang when configuration snapshot is apploaded. This happens because HTTP connection is lost due to toogling of the network interface which happened even if network configuration hasn't been mo dified.

Eurotech Everyware Software Framework ESF 3.2.0 (Eclipse Kura - 1.3.0)

Added Features (ESF):

  • Added support for external custom policy file.
  • Signed all the target platform and ESF bundles
  • Defined two functioning modalities: development where the security checks are reduced and the developer can freely create and test their bundles; production, where the security checks are fully enabled in order to prevent malicious attacks
  • Added implementation for the new Security APIs
  • Added Security-related tabs in Web-UI
  • General fixes and minor improvements
  • Improvements to Development Environment

Added Features (Kura):

  • API updates (Security, GPIOService)
  • Enhanced web UI security, which includes:
    • XSRF protection in all servlets
    • Different management of user sessions
    • Arbitrary file writes protection in file servlet for zip uploads
    • XSS on wireless SSID in network servlet
    • Command injection on network servlet
    • Password protection in client UI, in order to prevent access to secrets by unauthorized users
    • Sanitization of user and system strings in order to prevent malicious attacks
  • Ability to configure pairwise ciphers in AP mode in web UI.
  • Ability to stop/start bundles from web UI.
  • Ability to embed ConfigurableComponent icon within bundle, instead for requiring https location.
  • Added support for Telit LE910 modems.
  • Added test code for XML marshalling/unmarshalling.
  • Removed Xss option from start scripts. This JVM option has a know bug in OpenJDK.
  • Improvements to usability of Emulator.
  • Improvements to the Development Environment.

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.

Known Issues :

  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag.
    The only working version of BlueZ is 4.101. The deb package is not available from Raspbian so it
    must be compiled from sources.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • The reference JVM is Oracle Java SE Embedded version 7 Update 40.
    Later versions (including Oracle Java SE Embedded version 8 Update 33)
    may be affected by a ProcessBuilder memory leak [1]
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.

[1] https://bugs.openjdk.java.net/browse/JDK-8054841

Eurotech Everyware Software Framework ESF 3.1.2 (Eclipse Kura - 1.2.2)

Added Features (ESF):

  • Added support for Ubuntu 14.04 running on Reliagate 50-21.

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.

Known Issues :

  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag.
    The only working version of BlueZ is 4.101. The deb package is not available from Raspbian so it
    must be compiled from sources.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • The reference JVM is Oracle Java SE Embedded version 7 Update 40.
    Later versions (including Oracle Java SE Embedded version 8 Update 33)
    may be affected by a ProcessBuilder memory leak [1]
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.

[1] https://bugs.openjdk.java.net/browse/JDK-8054841

Eurotech Everyware Software Framework ESF 3.1.1 (Eclipse Kura - 1.2.1)

Added Features (ESF):

  • Added bundle for SekuPlate A1
  • Added bundle for ReliaSENS
  • Added support for Intel Edison without network manager
  • Provisioning: enable the possibility of provisioning with a CA not in local keystore
  • New SecurityManager
    • Refactor to meet the new 1.2 CryptoService Kura API
    • Added the possibility to specity a custom SecurityManager protected keystore
  • Add javax.bluetooth bundle to ESF user workspace

Added Features (Kura):

  • Added Bluetooth LE Beacon Service
    • Example: org.eclipse.kura.example.beacon
  • Reduced number of dependencies for Bluetooth LE bundle
  • Added support for non cfg80211 wifi modules
  • Added support for wifi on Raspberry Pi
  • Added support for Oracle Java 8 SE Compact 2 Profile runtime
  • Replaced IBM javax.usb implementation with usb4java
  • Refactor and optimization of SSL Manager
    • Improved security during keystore loading in SSL Manager
  • Refactor of ConfigurationService
  • Replace JAXB XML Parser with a custom one
  • Startup time improvements due to various code optimizations and uncompressed jars
  • Web UI: added the possibility to specify a custom web interface user
  • Web UI: split certificate management in two separate tabs

Bug Fixes (ESF):

  • ReliaGate 15-10: fixed bug on startup scripts not added to /etc/rc.x
  • ReliaGate 15-10: fixed bug on named not starting
  • ReliaGate 15-10: fixed eth1 not detected after ESF update
  • ReliaGate 10-20: fixed bug on hostapd restarting IP address is not assigned
  • Raspberry Pi: fixed exception on rollback to snapshot_0 for wlan0
  • Fixed wrong serial port for RS485 service

Bug Fixes (Kura):

  • Web UI: fixed wrong units for memory

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.
  • Bluetooth 2.1 was only tested with Cirago BTA3310 usb dongle and CSR BC04 chipset.

Known Issues :

  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag.
    The only working version of BlueZ is 4.101. The deb package is not available from Raspbian so it
    must be compiled from sources.
  • WiFi on Raspberry Pi only tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • The reference JVM is Oracle Java SE Embedded version 7 Update 40.
    Later versions (including Oracle Java SE Embedded version 8 Update 33)
    may be affected by a ProcessBuilder memory leak [1]
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.

[1] https://bugs.openjdk.java.net/browse/JDK-8054841

Eurotech Everyware Software Framework ESF 3.1.0 (Eclipse Kura - 1.2.0)

Added Features (ESF):

  • Added support for securing ESF.
    • Strong implementation of the org.eclipse.kura.crypto API.
    • Secrets managed by ESF can be only decrypted by signed bundles.
    • Validation of MQTT requests from EC through message signing.
  • RS485 support for the ReliaGATE 10-20 (see [2]).
  • GPIO support for the ReliaGATE 10-20 (see [2]).
  • Bluetooth support through Bluecove.
  • Added ESF support for the Raspberry Pi B+ and the Raspberry Pi 2.

Added Features (Kura):

  • Added support for securing Kura
    • Revised org.eclipse.kura.crypto API.
    • New org.eclipse.kura.certificate API to enable validation of
      signed requests from the cloud.
    • Minimal implementation of the org.eclipse.kura.crypto API.
    • Implementation of the org.eclipse.kura.certificate API.
    • Encryption of passwords in snapshot files.
    • Snapshot encryption.
    • Improved management and security of the keystore used for the MQTT
      SSL connection.
  • Added support for the Raspberry Pi B+ and the Raspberry Pi 2.
  • Added support for Bluetooth Low Energy (see Known Issues section below).
    • API: org.eclipse.kura.bluetooth
    • Example: org.eclipse.kura.example.bluetooth
  • Added OSGi console commands (get/setkuraloglevel) to control the Kura logger.

Bug Fixes (Kura):

  • Web UI: fixed wrong time units in the DHCP lease interval.
  • Web UI: filter 5GHz channels when displaying WiFi scan results.
  • Upgrade Deployment Package: remove the old Kura installation directory.
  • MqttDataTransport configuration: changed default MQTT protocol version to 3.1.1.
  • CloudService: even if gzip compression is enabled, publish the uncompressed
    MQtt payload if its size is less than the compressed payload size.
  • Network: Reduced executions of external ifconfig processes.
  • Network: Fixed WiFi background scan configuration.

Known Issues (ESF):

  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.

Known Issues (Kura):

  • BLE only tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag.
    The only working version of BlueZ is 4.101. The deb package is not available from Raspbian so it
    must be compiled from sources.
  • The Intel Edison platform is still a work in progress.
  • The reference JVM is Oracle Java SE Embedded version 7 Update 40.
    Later versions (including Oracle Java SE Embedded version 8 Update 33)
    may be affected by a ProcessBuilder memory leak [1]
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.
  • On the Reliagate 10-20, ESF keeps restarting the hostapd if IP address is not set for the wlan0 interface while wlan0 is administratively up.
    This condition can be triggered by resetting WiFi radio.
  • On the Reliagate 15-10, the /usr/sbin/named is not starting on system level, but the LinuxNamed.java needs to be fixed as well to reflect that the named.conf is
    expected to reside in the /etc/named directory.

[1] https://bugs.openjdk.java.net/browse/JDK-8054841
[2] At the time of writing the latest utiliboot for the ReliaGATE 10-20 is available at:
http://eurotechcloud.transfer.eurotech-inc.com/~publicaccess/cho/700050-4e10k_cpu-3xx_yocto-20150506020245/
Note that release date in the URL can be updated. Please browse the parent directory and use the latest
available image.

Eurotech Everyware Software Framework ESF 3.0.2

Added Features:

  • Added support for Reliagate 15-10 IDP allocating 192MB of memory and http.port to 8080

Bug Fixes:

  • Fixed JVM memory leak by making sure all stream are closed and
    the streams associated to the stdout and stderr of external processes
    are consumed asynchronously
  • Overall optimization of the network related bundles by removing
    unnecessary executions of external processes
  • Fixed MANIFESTs removing unused imports and fixing Import-Package version
    ranges to comply with OSGi Semantic Versioning
  • Ppp0 connection not starting after a fresh install
  • Modem did not recover the connection when the antenna is unplugged
  • Avoid starting two Kura instances
  • Rolling back to snapshot 0 does not change the modem configuration on the Minigateway
  • Don't allow to set the gateway on LAN interfaces
  • When reconfiguring Wifi from Station to Access Point, DHCP&NAT tab gets enabled only
    after clicking on the 'Wireless' tab
  • Since we don't support 802.11a, do not allow this in configuration
  • Poweroff command fails at 'Stopping Kura'
  • Disable snmpd to avoid excessive flash writes on raw-flash devices
  • Fixed Web Admin /esf vs /kura redirect
  • Fixed VpnService username@accountName

Known Issues:

  • The reference JVM is Oracle Java SE Embedded version 7 Update 40.
    Later versions (including Oracle Java SE Embedded version 8 Update 33)
    may be affected by a ProcessBuilder memory leak [1]
  • GPIOs not supported by JDK DIO on the ReliaGATE 10-20
  • RS485 not supported on the ReliaGATE 10-20
  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui
    does not work over some network topologies - OSX or Linux are recommended
    to access the webui in this rare case
  • Only one WAN interface is currently supported.
    A warning in displayed in the WEB UI if the user attempts
    to enable more than one WAN interface
  • When first modem configuration is submitted, unconfigured cellular interface for serial modem (e.g. HE910) is not being replaced by
    ppp0 interface. Both ppp0 and HE910 interfaces are shown in the Web Admin.
  • When a ReliaCELL is connected to the ReliaGATE 10-10 the log will show several exceptions when accessing the
    Network Administration panel on the WebUI
  • Gateway needs to be rebooted for static GPS coordinates to be published to the cloud.

[1] https://bugs.openjdk.java.net/browse/JDK-8054841

Eurotech Everyware Software Framework ESF 3.0.1

Added Features:

  • Added configurable CommandService to password-protect command execution
  • Added support to reset WiFi if it cannot be enabled
  • Added selection of the MQTT protocol version to the MqttDataTransport configuration

Bug Fixes:

  • Fixed ppp0 interface disappeared from Web UI
  • Improved tips in the cellular modem advanced options and changed default values
  • Fixed bug 452499: Kura Debian package name should be lower case
  • Fixed org.eclipse.kura.linux.position not setting the track heading parameter
  • Fixed org.eclipse.kura.linux.position to correctly select the GPS receiver
  • Fixed org.eclipse.kura.linux.usb to better handle removal of USB devices
  • Fixed org.eclipse.kura.linux.net to properly track USB add/remove events and stale devices
  • Fixed org.eclipse.kura.net.admin to properly track modems
  • Fixed org.eclipse.kura.net.admin to keep resetting the modem if PPP link cannot be established
  • Fixed missing ESF branding in the Web UI
  • Fixed missing icon for the ProvisioningService
  • Fixed missing install of openvpn executable on the ReliaGATE 50-21
  • Fixed Wi-Fi lost while testing modem GPS while connecting via WiFi
  • Security fixes to the the VpnService
  • Fixes to CAN bus support
  • Fixed minor issues

Known Issues:

  • Cellular modem configuration cannot be rolled back to factory defaults
  • GPIOs not supported by JDK DIO on the ReliaGATE 10-20
  • RS485 not supported on the ReliaGATE 10-20
  • Release only validated against ReliaGATE 10-20 RevB
  • Release only validated against the HE910 version of the ReliaCELL.
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui does not work over some network topologies - OSX or Linux are recommended to access the webui in this rare case
  • Only one WAN interface is currently supported. A warning in displayed in the WEB UI if the user attempts to enable more than one WAN interface

Eurotech Everyware Software Framework ESF 3.0.0

Added Features:

  • OpenJDK Device I/O integration
  • Added org.eclipse.kura.example.gpio example using OpenJDK Device I/O
  • Added RPI B+ distribution
  • Display warning in the WEB UI if the user attempts to enable more than one WAN interface
  • Modem IMEI and SIM IMSI/ICCID published in the birth certificate
  • Improved documentation on the Eclipse Kura Wiki
  • Upgraded to Google Protocol Buffers 2.6.0 (adding union types)
  • Display client ID in the WEB UI Status page

Bug Fixes:

  • Upticked API package versions to 1.0.0
  • Fixed DNS issue when DNS servers are provided in the configuration
  • Fixed 'iw' scan problem (IBSS capability)
  • Fixed a MetaTypeBundleTracker issue slowing down the Kura startup
  • Added a minimum value of two minutes for the modem reset interval
  • Improved robustness of the Kura upgrade scripts
  • Upgraded to Paho 1.0.1 (many bug fixes)
  • Fixed uncaught exception preventing network interfaces being displayed in the WEB UI
  • Set Paho client callback to null before terminating the client
  • Removed 'old' native library directories
  • Fixed WEB UI username/password lost for the in-memory configuration of HSQLDB
  • Fixed HIDAPI bundle
  • Fixed HSQLDB exception due to large system time adjustments
  • Merged pull requests and contributions sent in the form o diff files to the mailing list
  • Added 'telnet' to the list of 'apt' dependencies

Known Issues:

  • Hardware watchdog: not implemented on all platforms
  • Reliagate 50-21: Using eth1 and Windows 7 to access the webui does not work over some network topologies - OSX or Linux are recommended to access the webui in this rare case
  • Only one WAN interface is currently supported. A warning in displayed in the WEB UI if the user attempts to enable more than one WAN interface