Lighthouse 2020.Q1.0 is Generally Available.
Fixes and Features:
20.Q1.0 (February, 2020) - NOTE: The minimum required RAM for Lighthouse is now 8GB from this release. - Add support for IPv6 - Add support for different remote authentication methods (eg. RadiusLocal, RadiusDownLocal, LocalRadius, etc.) - Improved security - limit web server information exposure, and add cross-site scripting protection - Improved UI look and feel (including Ember 3.12 upgrade) - Improved REST API performance and scalability - Updated base operating system distribution (new versions of many opensource packages, security fixes, etc.) - Defects fixed since 19.Q3.3 - Fixed two-factor authentication with SSH - Fixed issue booting on ESXi (older hardware without DRNG random number entropy support) - Fixed support for node cell health status and IP address display - Fixed serial console gateway using delimiters and SSH pubkey together - Fixed issue where promoted secondary Lighthouse instances can't enroll future secondary Lighthouses - Fixed permissions issue when administrators try to delete syslog server configuration from Lighthouse - Fixed various UI bugs (display, input field validation, etc.) - Fixed issue with web terminal session remaining when UI logs out - Fixed intermittent config server sync error when using many secondary lighthouses (causing failed web logins) - Fixed issue with node backups not being visible between different version installs
Opengear are aware of the following product specific issues with this release: - The number of nodes connected to a secondary Lighthouse will be listed as unknown if the connection between the two Lighthouses is broken. - If a remote authentication server is configured, but it is down, there may be a delay or a failure in authenticating local users via the web UI. - When applying configuration templates, ensure the set of nodes you are pushing to is a small number (<50), large pushes can take a long time to complete. - Due to improvements in the network validation routines, please check the correctness of network settings before upgrading. Specifically if a device is being assigned the same address both statically and via DHCP, this will now cause validation failures which may result in an upgrade rollback. - Virtual Machines with less than 8GB of RAM may exhibit some instability, and may fail loading a firmware upgrade file via the web interface. We recommend at least 8GB of RAM for Lighthouse. - If the Lighthouse VM is configured with IPv6, but the network it is attached to does not support/provide IPv6 addresses, the web interface may show the IPv6 address as "undefined/undefined".
If you have a previous version of Lighthouse installed, it is advised that you take a VM snapshot of your installation.
It is suggested that you clear your browser cache - as some browsers will not auto-update the firmware revision information listed in Lighthouse.