mLinux Changelog

4.0.1 (2018-08-01)

Changes since 3.3.24

  • mLinux 4 is based on Yocto 2.2. mLinux 3 was based on Yocto 1.6
  • OpenJDK was removed from the image. Still available from feeds or build your own image
  • The new kernel fixes write hangs when doing high volume writes to jffs2 file system or SD card
  • Enhanced security. Root user logins are removed. New admin is mtadm, and is not root. Root privilege is accessed via sudo
  • Default login on MT provided images is mtadm/root
  • Support for LoRa 2.1
  • Support for address ranges in firewall settings
  • Bluez5 replaces Bluez4
  • ifplugd to bring up connections and restart DHCP
  • kernel support for Cat M Cellular radios
  • U-Boot password protection
  • php-fpm replaces fastcgi on the images
  • eudev replaces udev
  • Upgraded packages

Known Issues

  • sms does not work with LNA3 Cellular Modem on Verizon with MTCAP
  • Radio reset does not work with LNA3 and MTCAP with firmware 20.00.522 (AT&T) or 20.00.12 (Verizon). The solution is to upgrade
    the firmware to 20.00.524/20.00.14.
  • Upgrading Telit firmware
  • In mLinux 3, libcurl4 was mistakenly called libcurl5. This was a bug in Yocto 1.6. This bug has since been corrected, and libcurl4 is now called libcurl4 as it should be. However, old programs linked by the toolchain for mLInux 3 will not be able to find libcurl4. This can probably be fixed with a symlink, but this solution needs testing.
  • libcurl5 issue

3.3.24 (2018-04-09)

Changes since 3.3.22

  • Lora Network Server 2.0.19
  • Add kernel revision to revision of vizzini and mts-io pacakges
  • Correct revision of kernel-module-bluetooth
  • Fix gpsd scripts used by ntpd to prevent possible boot hangs

3.3.22 (2018-03-05)

Changes since 3.3.15

  • dnsmasq security fixes:
  • CVE-2017-13704
  • CVE-2017-14491
  • CVE-2017-14492
  • CVE-2017-14493
  • CVE-2017-14494
  • CVE-2017-14495
  • CVE-2017-14496
    Fixed package:
  • dnsmasq_2.78-r0.0
  • Bluetooth Blueborne security fixes
  • CVE-2017-1000250
  • CVE-2017-1000251
    Fixed packages:
  • kernel-module-bluetooth-3.12.27-r14.m1.1
Requires kernel 3.12.27r15
  • bluez4-4.101-r10.m1.0
  • WiFi (hostapd and wpa_supplicant)
  • CERT case ID: VU#228519
  • CVE-2017-13077
  • CVE-2017-13078
  • CVE-2017-13079
  • CVE-2017-13080
  • CVE-2017-13081
  • CVE-2017-13082
  • CVE-2017-13086
  • CVE-2017-13087
  • CVE-2017-13088
    Fixed packages:
  • hostap-daemon-2.6-r0.0
  • wpa-supplicant-2.6-r0.0
  • wpa-supplicant-cli-2.6-r0.0
  • wpa-supplicant-passphrase-2.6-r0.0
  • RS9113 driver 1.5.6 update for new revision RS9113 part. New devices are not compatible with older versions of this driver.
    Old devices are compatible with the new driver.
    Package upgrade:
  • rs9113-1.5.6-r0.3.12.27r15.0
  • Failure to complete boot in certain newer devices:
  • gpsd-3.16-m5.0
  • mts-io-1.5.16-r10.0-3.12.27r15.0
  • Do not do Radio Reset of Cellular modem when the modem is not on the device.
    mts-io-1.5.16-r10.0-3.12.27r15.0
  • Build the /run/config directory during boot for Lora software to make it easier to discover
    devices. This does not include cellular radio information.
    get-eeprom-device-config – 1.1.0-r1.0
  • Preserve hostapd and dnsmasq (if installed) files across installations.
    config-2.1-r1.0
  • Allow radio reset of cellular modem despite backoff timer restrictions.
    mts-io-1.5.16-r10.0-3.12.27r15.0
  • Support for LDC3 radio (Japan)
    libmts-io0-1.0.3-r0.0
  • Support for network bonding
  • kernel-3.12.27r15
  • kernel-module-bonding-3.12.27-r15.1
  • Netfilter additional support:
  • kernel-3.12.27r15
  • kernel-module-xt-tproxy-3.12.27-r15.1
  • kernel-module-xt-hashlimit-3.12.27-r15.1
  • kernel-module-xt-tee-3.12.27-r15.1
  • mts-fpga-loader for Lora firmware updates.
    mts-id-eeprom-0.3.3-r1.0.0
  • Support for IP67:
  • mts-io-1.5.16-r10.0-3.12.27r15.0
  • allow upgrades for IP67 (no downgrades to prior levels of mLinux)
  • LNS 2.0.16
    See additional LoRa notes below
  • Don’t allow AEP version to be overwritten by mLinux version.
    Lora Query 1.0.4
  • New channel plans
    LPF 3.1.0-r11
  • NodeJS 0.10.48-r1.7
  • Allow for an install script in an upgrade package.
    config-2.1-r1

Additional LoRa Notes

    LoRa Network Server v2.0.16
    Class C scheduling up to 5 seconds out, instead of failing schedule call multiple times
    Set default join delay to 5 seconds, if null was provided OTA join was not possible
    Fix sample config file JSON error comma at end of list
    Add app port to application MQTT topic for up and packet_sent events
    Allows for application specific filtering such as Multicast or Multipart
    mosquitto_sub -v -t lora/+/+/+/+
    mosquitto_sub -v -t lora/<APP-EUI>/<DEV-EUI>/<APP-PORT>/<EVENT>
    Add some time randomization for class C downlink rescheduling
    Fix for US/AU private mode Rx2, frequency was not correct
    Emit queue_full message if no room left, check of queue size was added before making a call to add the packet
    Add timeout if packet forwarder is not seen in 10 minutes the network server will restart all lora services (network-server, lens-server and packet-forwarder)
    Add support for Network Modes: 0:Private MTS, 1:Public LoRaWAN and 2:Private LoRaWAN
    Private MTS is the previous default to work with Dots with AT+PN=0
    Public LoRaWAN is the new default for LoRaWAN 1.0.2 compatible end-devices, Dots AT+PN=1
    Private LoRaWAN is a new mode for LoRaWAN 1.0.2 compatible end-devices in a private network, Dots AT+PN=2
    Join Delay defaults to 5 seconds
    Add “lora” > “joinDelay” setting to adjust to 1 second for Private MTS mode.
    Affects only mLinux, AEP has UI/API controlling the configuration.

3.3.15 (2017-10-30)

Changes since 3.3.13

      • Lora Network Server 1.0.43-r1.0.
      • Lora Packet Forwarder 3.1.0-r10.0.
  • adjust the MTAC_LORA_1_0 default min/max US915 frequencies
  • update 1.0 MTAC-LORA default global_conf.json file for consistency sake
  • MTAC_LORA 1.5 US915. Default frequency offset for DR4 channel was misconfigured
  • update global_conf.json file for +13dBm output according to Japan certification testing
      • Bluez4 Blueborne fix 4.101-r10.m1.0
      • Bluetooth kernel module Blueborne fix, kernel-module-bluetooth 3.12.27-r14.2, srcversion: A663C5831F3BBA8C48735E5
      • gpsd script could cause hang in ntpd start-up, gpsd-conf 3.16-m4.0
      • /etc/init.d/umountfs allows for package updates rather than just image replacement, mlinux-scripts 1.1-r3.0
      • Lora eprom burning tool, mts-fpga-loader, for mtcdt, mts-id-eeprom 0.3.3-r1.0.0

3.3.13 (2017-09-27, revised 2017-10-23)

Features since 3.3.9

      • Remove radio reset from MTCAP units with no cellular radio.
      • Support for MTCDTID harware version
      • Support for LNA3 radio option
      • Support for Netfilter TEE available in kernel module xt_TEE.ko.
      • ppp waits for SIM registration before starting. See

        http://www.multitech.net/developer/software/mlinux/using-mlinux/start-cell-connection-on-boot/

      • International dialing support in sms-utils
      • When umountfs attempts an upgrade, first clean up /var/volatile of unneeded files
      • New Lora calibration data in /opt/lora/global_conf.json.MTCAP_LORA_1_5.US915.

Known Issues

When building an upgrade file for MTCDTIP, you must update the model file after the build.

cd /tmp
mkdir mlinux-3.3.13
cd mlinux-3.3.13
tar -xf ~/Downloads/mlinux-base-image-mtcdt-upgrade-withboot.bin
sed -i 's/mtcdt/mtcdt|mtcdtip/' model
tar -cf /tmp/mlinux-base-image-mtcdt-upgrade-withboot.bin *

3.3.9 (2017-08-10)

Features since 3.3.7

      • gethostbyname memory leak fix — libc6_2.19-r0.m1.0
      • MTCAP had an unusual password in 3.3.7. Set to root in 3.3.9
      • New Lora software related to support for Japan
        • Lora-gateway from 4.0.1-r9.0 to 4.1.3-r10.0
        • Lora-network-server from 1.0.26-r1.0 to 1.0.36-r1.0
        • Lora-packet-forwarder from 3.0.0-r9.0 to 3.1.0-r9.0

3.3.7 (2017-06-26)

Features

      • Support for LJP1 (LE866) Radio (Japan)
      • Support for LJP1 (LE910-JN1) (Japan)
      • Support for LNA3 (LE910-NA1)

Fixes

      • OPEN SSL Version 3 Support added for Python. New SSL package is openssl – 1.0.2k-bpo8.1m2.0
      • GPSD no longer will start if the GPS capability flag is not set by the MTS-IO driver.
      • When starting GPSD, a maximum of 20 seconds is allowed for changing the baud rate of the GPS. This will allow the boot to proceed if a baud rate change is not possible.
      • Eliminated setserial command invocation from udev which was producing error messages and not needed.
      • Bootstrap patch borrowed from MTR to lessen the likelihood of the Real Time Clock preventing boot when operating with a battery.
      • Build change: source control for 3.x.y above 3.3.6 was moved to git 3 branch from master. This was to prepare for mLinux release 4.0

See also

Using mLinux

3.3.6 (2017-04-21)

Changes

      • lora-network-server is at level 1.0.26.
      • Upgraded to openssl 1.0.2k-1~bpo8+1 from Debian backports to be compatible with mLinux 3.1 and 3.2 and provides security enhancements.
      • GPSD support for leap second on Conduits with GPS receiver feature.
      • NTPD starts by default if the GPS has a position fix. NTPD adjusts the system clock and sets the hardware clock.
      • To disable GPSD, set parameter /etc/default/gpsd: ENABLED="no". Reboot.
      • To disable NTPD, set parameter /etc/default/ntpd: ENABLED="no". Reboot.
      • To disable GPS requirement for NTP, set /etc/default/ntpd: GPSD_REQUIRED=0.
      • To check GPSD when it is running, type gpsmon.
      • Ethernet Bonding feature added.

Known Issues

      • Lora only supports 915MHz, 868MHz, and AU915MHz channel plans.

See also

Using mLinux

3.2.0 (2016-05-18)

Changes

      • Updated openembedded-core with latest security fixes from Yocto 1.6
      • Fixed monit building issue with 3.1.0
      • lora-network-server 1.0.8
      • Added support for LTE radio models: LVW2, LEU1, LAT1
      • mts-io 1.1.4 — fix possible kernel crash in driver
      • node.js 0.10.44
      • Added strongswan to images
      • Fix sms bugs where some characters wouldn’t be sent or received correctly

Known Issues

      • Will not build on Ubuntu 14.04/16.04 with kernel 4+

3.1.0 (2015-05-27)

    • First official release!