*****************************************************
* AEP Firmware 5.0.0 Release Notes                  *
*****************************************************
Contents:
1) Models Covered By This Firmware.
2) Firmware Upgrade Procedure.
3) Engineering Release Notes for Customer.
4) Support Information.

****************************************************
*    Models Covered By This Firmware               *
****************************************************
- MTCDT-H5
- MTCDT-L4E1
- MTCDT-LAP3
- MTCDT-LAT1
- MTCDT-LDC3
- MTCDT-LEU1
- MTCDT-LSB3
- MTCDT-LVW2
- MTCDTIP-L4E1
- MTCDTIP-LAP3
- MTCDTIP-LAT1
- MTCDTIP-LDC3
- MTCDTIP-LEU1
- MTCDTIP-LVW2

****************************************************
*    Firmware Upgrade Procedure                    *
****************************************************
Upgrading to 5.0.0.

Note: Backup your configuration before performing this upgrade. If the firmware
upgrade fails, or it does not show the login page again, wait an additional 10
minutes. Power off and on the device and web in to check the version. If the
version does not show the latest, then the upgrade was not successful. Try to
perform the firmware upgrade again by repeating all the steps.

NOTE:
To upgrade using the Web UI to the latest AEP 5.0.0, you must be running at
least 1.6.4 firmware.
If older than 1.6.4, you must be running at least 1.4.x to upgrade to 1.6.4.
With older firmware, it is necessary to be at 1.4.x before upgrading to
version 1.6.4 or 1.7.4.

1) Save the firmware binary file to a directory on your workstation.
2) Using the workstation browser, enter the IP address of the device
   (i.e. http://192.168.2.1).
3) Login with admin user and enter the admin password.
4) Click "Administration" tab on left side menu bar.
5) Click "Save/Restore".
6) Click "Save Configuration to File" to save a backup file. A popup window will
   appear.
7) Select "Save File" and click "OK" button.
8) Now click "Firmware Upgrade" tab on left side menu.
9) This version of firmware has a Firmware Validation option. Review the Firmware
   Upgrade Help for further information.
10) Click the Browse button and select the latest version of BIN file,
    conduit_5.0.0-AEP_upgrade.bin.
    Use the respective -signed upgrade file based on Firmware Validation option.
11) Click the "Start Upgrade" button. Confirm the 10 minute "OK" button.
12) Wait for the unit to upgrade and reboot automatically.
13) Again, browse to the IP address, login and verify the Home Page indicates the
    correct version, 5.0.0.

****************************************************
*    Engineering Release Notes for Customer        *
****************************************************
-----------------------------------------------------
AEP firmware 5.0.0 - June 2019
-----------------------------------------------------
Changes made since release 1.7.4:
- Migration of Web UI to vueJS. Look and Layout has changed.
- Added RADIUS support.
- DHCP Lease Time displays expiration date and time.
- Firewall display/layout aligns more with Linux layout.
- Implement X.509 Certificate support.
- Eliminate Default Username and Password. User prompted to set up a Username and
  secure Password upon Factory Default/Hard Reset, Commissioning Mode.
- The Logout option has changed to Door Exit icon.
- The browser tab name references page name.
- Changed LogIn screen to sign-in.
- Page links have removed the .html extension.
- Add IPSec certificate based authentication support.
- Updated supported ciphers in multiple features (SSH, HTTPS, etc...).
- Implement Trusted IP feature.
- Implement Self-Diagnostics beta feature to check Resource Overuse and
  Security Violations.
- Incorporated Signed Firmware support.
- SNMPv3 advanced security settings enhancements and support for multiple trap
  destinations. Extended SNMP read parameters.
- Usage Policy implementation in the Web UI.
- Display Notifications sent via Email, SMS, or SNMP.
- RADIUS Message Authenticator Attribute was added to all PAP requests.
- Implement tunnel features.
- Implementation of more Network Interface capabilities under
  Setup > Network Interfaces.
- Updated Global DNS Configuration under Setup > Global DNS.
- Added Bootloader password configuration to the Initial Setup Wizard.
- LoRa Network Server updated to v2.2.27.
- LoRa Packet Forwarder: Added duplicate packet filter, fix for GPS lock and time
  synchronization and increased radio lead time for better downlink success.

Bug Fixes since release 1.7.4:
- Add Statistics page for OpenVPN tunnel.
- Populated leading 0's in SMS #cellular Command, Uptime now reads 00:00:00
  not 0:0:0.
- Fixed "Invalid Date" issue when viewing Remote Management with Firefox 47.
- Fixed SMS Command #cellular eliminating Uptime leading 0's.
- Fixed device position on GPS page map to not depend on NMEA configuration settings.
- Fixed Generate Certificate so that the City value is not lost and set to empty
  when generating a new Web server certificate.
- SMS Commands should work again for International numbers.
- Updated Help Content.

Known Differences since 1.7.4:
- A hard reset/factory default of the 5.0.0 will force Commissioning mode.
- Security modifications may require "sudo" usage if using SSH or debug console.
- Security modifications require a "sudo su" to log into root and adding the
  following "--unix-socket /var/run/api/http.sock" to existing curl commands.
- Although not recommended, downgrading from 5.0.0 to a previous version will
  require a hard reset back to default settings. Very important to not
  downgrade when remote to the device or when using DeviceHQ (Remote Management)
  because access will be lost.
- On WiFi models, the Dashboard WiFi MAC address now matches the WiFi hardware instead
  of matching the Ethernet MAC Address. This was improper reporting on the Dashboard
  only, the WiFi hardware was correct.
- Because of additional GPS options, GPS may take longer to acquire satellites.
- IP Defense options, DoS Prevention, Ping Limit and Brute Force Prevention
  are Enabled by default.
- Under Adminstration > Access Configuration, SSH via LAN is disabled by
  default.
- For security, Telnet Radio Access and Telnet have been removed.
- The Clear History buttons have moved from Administration > Debug Options to the
  Ethernet, WiFi and Cellular tabs under Status & Logs > Statistics.
- GPS NMEA options default with GGA, GSA, GSV and RMC enabled and GLL and VTG are
  disabled.
- The code version has been removed from the log in screen, it is replaced with
  the new mPower Edge branding.
- Dashboard banner and Firmware version includes "-AEP", i.e. 5.0.0-AEP.

Known Behavior in 5.0.0:
- User must be at version 1.6.4 (or newer) before upgrading to 5.0.0.
- Although not recommended, downgrading to a version before 5.0.0 will require a
  hard reset back to factory default settings.
- A Hard Reset (or Factory Default) will force 5.0.0 firmware into Commissioning
  Mode to create a new Administrative Username and Password.
- On LVW2, certain newer Verizon SIM’s do not support SMS. Contact Verizon.
- On LVW2, received SMS’s greater than 140 characters may be truncated to 140.
- Command AT+WS46 reverts to default after a power cycle which may affect a user
  that sets a non-default value.
- SMS Command API ignores 6 character password limit, does not fail if SMS is
  longer than 160 characters, has issues depending on location of spaces and can
  not view view/delete inbox/outbox.
- Nofications API can delete existing alerts, add new alerts, modify with
  non-existing group, add two groups with same name and generate email with
  bad characters.
- DHCP API can set invalid Gateway.
- With SMS Commands, the Whitelisted numbers may need to be updated to include a +,
  a 1, or full phone number. Send a test SMS to the device to confirm.
- Version 1 API call (/api/v1/whoami) does not respond.
- Connecting OpenVPN Tunnels, user is unable to open WebUI of remote device.
- Firmware upgrade may revert LoRa Network settings to default. Network Mode set to
  Private LoRAWAN may change to Public LoRaWAN. Rx2 Datarate to 8 for 915 cards and
  0 for 868 cards. Rx1 Delay to 1. Join Delay to 1 for Private MTS or 5 for Public
  LoRaWAN. Additional Channels setting for KR920 and AS923 to 922.9 or 922.6,
  respectively. MaxEIRP and DwellTime Up/Down for AS923 to 0.
  WorkAround is to modify /var/config/db.json "__v": 1 setting in "loraNetwork"
  collection to "__v": 18 before the upgrade to avoid reverting. Otherwise modify
  the above settings after the upgrade.
- If using Remote Management and you perform a manual check in to Device HQ, your
  device may show two check in's based on your Check In Interval.
- For Conduit devices: A regression exists where support for OpenVPN tunnels over 
  Ethernet as WAN and WiFi as WAN no longer work.

****************************************************
*      Support Information                         *
****************************************************
Multi-Tech provides free technical support for your product. To obtain this
support, we suggest you create a support case on our Support Portal at:
https://support.multitech.com

If internet is not available, try one of our numbers:
U.S. & Canada number: 763-717-5863
Answered Monday - Friday
8:00 am to 5:00 pm Central Time (Daylight savings observed when in effect)

International number: +763-717-5863
Answered Monday - Friday
8:00 am to 5:00 pm Central Time (Daylight savings observed when in effect)

EMEA    support@multitech.co.uk         +(44) 118 959 7774
U.S.    support@multitech.com           800-972-2439 or
(and Rest of World)                     +763-717-5863

Replacement Parts and Accessories
For replacement parts and accessories, contact Multi-Tech at:
(888) 288-5470, option 3 or +1 (763) 785-3500

US Mail Address:
  Multi-Tech Systems, Inc.
  2205 Woodale Drive
  Mounds View, MN 55112
  USA

::Form Version R2014-03-27::