Issues Resolved
- Last Updated: February 5, 2025
- LoadMaster
- LoadMaster LTSF
- Documentation
| LM-7034 | L7 Kernel: A timing issue in the L7 kernel has been identified that could cause a crash and a system reboot. Essentially, a client connection closes unexpectedly and the corresponding destination socket is in an undefined state. This issue has been fixed. |
| LM-6721 | QoS: Fixed an issue observed starting in 7.2.60.0 where logging for limited connections did not always occur as expected. |
| LM-6620 LM-6630 | System Console: Fixed issues seen starting with 7.2.60.1 that caused spurious messages to appear on the system console on booting into non-FIPS and FIPS modes. |
| LM-6618 | ACME Application Programming Interface (API): Fixed an issue that caused the API command for registering a DigiCert account to fail. |
| LM-6591 | Web Application Firewall (WAF) API: Fixed an issue where rapid custom rule uploads could remove previously applied rules. |
| LM-6589 | ACME: The certificate repository appears as blank for a read only user. This issue has been fixed. |
| LM-6584 | ACME API: Fixed an issue where an invalid JSON format response is returned when retrieving a certificate using getacmecert. |
| LM-6581 | ACME: Fixed an issue with certificate deletion observed in High Availability (HA) mode. |
| LM-6520 | APIv2: Fixed an issue where a plus sign (+) included in an APIv2 (JSON) format call is replaced with a space. |
| LM-6366 | GEO: Fixed an issue observed in 7.2.59 where only a subset of the defined GEO custom locations is displayed under FQDN location based scheduling. |
| LM-6191 | Interface Settings: Fixed an issue where MTU changes for bonded interfaces and VLANs did not take effect. |
| LM-6190 | GEO: In previous releases, if the zone name is not set, a serverfail error is returned when querying the (Source of Authority) SOA record. This issue has been fixed. |
| LM-6184 | Single Sign On (SSO): Authentication using reCaptcha fails when the size of the token is above 800 bytes. The maximum number of bytes supported for a token has been increased to 4K. |
| LM-5923 | APIv2: Corrected format errors in the JSON output of the "stats" command for QoS/Limited client IP addresses. |
| LM-5709 | QoS / Limiting: Fixed an issue that caused spurious "Client x.x.x.x no longer limited" messages to appear in the system log. |
| LM-5698 | GEO: Fixed an issue first seen in 7.2.59 where the "Disabled Clusters Unavailable" setting is turned on, but disabled clusters are still reported as available. |
| LM-5627 | GEO Debug Info: Fixed an issue that caused the Config Version / SOA serial number to no longer match between GEO partners. |
| LM-5383 | GEO: Fixed an issue where deleting a custom location on one partner does not take effect on the other partner. |
| LM-5182 | Single Sign On (SSO): Fixed an NTLM authentication issue that caused user access check control errors when the username is in UPN format and the domain specified is a domain other than the SSO domain. |
| LM-4957 | GEO Logging: In previous releases, logs showing IP addresses as "administratively disabled" are printed to the log whenever any administrative change is made to GEO. This issue has been fixed. |
| LM-2744 | SAML Authentication: Fixed an issue that could cause a logout loop. |
| LM-2739 | Idle Connection Timeout: In previous releases, the default idle connection timeout setting was not working properly until it was explicitly re-set. This issue has been fixed. |
| LM-2404 | WAF: Fixed issues that caused the WAF engine to become temporarily unresponsive when being scanned by tenable.io. |
| LM-1007 | GEO: In previous releases, IP addresses shown in the IP Remote VS selection menu that apply to multiple ports have no ports listed. The display has been modified to include a list of all ports that apply to the IP address (for example, 10.10.10.10:[80, 90]). |
| LM-570 | GEO: In previous releases, it was possible to delete an IP Address Range that is configured for use by an FQDN. With this release, you cannot delete an IP address range that is in use. |
| LM-126 | GEO: Fixed an issue causing a spurious message to be displayed on the system console (disp_addrr_elements is not defined). |