GEO 2.3.37.1 Release Notes
Refer to the sections below for details about firmware version 2.3.37.1. This was released on 7th February 2017.
New Features
The following features were added to the 2.3.37.1/7.2.37.1 release:
- Domain Name System Security Extensions (DNSSEC) support.
Issues Resolved
PD-8397 |
GEO clusters checking a Virtual Service that uses enhanced health checks reports a down status correctly. |
PD-8772 |
“Everywhere” shows up twice in location selection. |
PD-8725 |
Proximity and Location Based scheduling does not work with IPv6 source addresses. |
PD-8014 |
A remote LoadMaster cluster does not respond unless the remote LoadMaster has a Virtual Service. |
PD-7909 |
Improved error handling for the Set-GeoFQDN PowerShell API command. |
PD-8515 |
Fixed an issue which caused an error when using the FQDN for the LoadBalancer parameter on certain PowerShell API commands. |
PD-8009 |
The listcluster API command returns a status. |
PD-7338 |
The listclusters API command returns the correct health check port value. |
PD-8038 |
The showcluster API command returns the correct status value. |
Known Issues
PD-10980 |
A critical vulnerability (CVE-2018-9091) in the Multi-Tenant LoadMaster Operating System (MT-LMOS) related to Session Management could allow an unauthorized, remote attacker to bypass security protections, gain system privileges, and execute elevated commands such as ls, ps, cat, and so on, thereby compromising the system. Through this remote execution, in certain cases, exposure of sensitive system data such as certificates, private keys, and other information may be possible. Further information can be found here: Mitigation For Remote Access Execution Vulnerability. |
PD-8725 |
Proximity and Location Based scheduling do no work with IPv6 source addresses. |
PD-10155 |
Issue with configuration corruption causes some GEO features not to function. |
PD-8357 |
Minor issue with error handling when adding a new cluster using the API. |
PD-8118 |
The GEO Update Interface cannot be set using the API. |