Take 163 - Ongoing

In a rare scenario, the FWM process will utilize 100% CPU, and connections to SmartConsole may fail.

In some scenarios, an upgrade from R7x secondary Multi-Domain Server with active Domains may fail.

Global policy reassignment may fail after a rulebase is deleted in the Global Domain.

In a rare scenario, all users connected to the Management Server get disconnected and new logins fail until the Management Server is restarted.

In some scenarios, policy installation fails when the installation target is Check Point Host.

In some scenarios, HA synchronization in the Global Domain fails with the "Failed to sync peer - Global Domain is incompatible with the Domains." error.

If the database contains an internal user object with the same account name as an administrator object, then after the user publishes any change to the internal user object, the login in SmartConsole with the administrator account may fail.

The Administrator and Trusted Clients pop-up editors at the Multi-Domain Server level show all domain names linked to these objects. Domain Managers with partial permissions, may see the names of domains that they are not permitted to see.

NEW: LDAP advanced query now supports ANR filtering.

In some scenarios, on a Global domain, when the user sets a logging option of an IPS protection whose activation is Detect or Prevent, the activation of the protection is set to "Inactive" on the local domain after an Assign Global Policy operation.

After an upgrade of R80.10 Management, cloned Multi-Domain super user permission profiles (Read/Write permission profiles) may be missing the "Global VPN Management" permission.

The API command 'show-api-versions' may return version 1.6 instead of 1.5. Refer to sk163942.

Improved the ICAP client connectivity when using Trickling mode 3 in settings.

In a rare scenario, ROUTED process unexpectedly exits under high load.

Global connections may not be freed correctly when the Gateway acts as a Proxy.

Improved scalability of DOS/Rate limiting rules.

In some scenarios, connectivity problems may appear due to proxy arp table that is not updated after policy installation.

Policy installation on Cluster may fail if the Cluster member name is longer than 64 characters.

In some scenarios, there is no SIC after applying the ICA certificate replacement procedure.

In some scenarios, there is no SIC after applying the ICA certificate replacement procedure.

In a rare scenario, Security gateway may crash due to NULL pointer reference.

• Fix is relevant for Gaia 2.6.18 only

In rare scenarios, files fail to download when the Threat Extraction Blade is active.

Identity Awareness performance improvements in large scale environments.

In a rare scenario, memory leak may appear in ICAP client when HTTPS Inspection is enabled.

NEW: Added support for proxy configuration when downloading CRL from a VSX device. Refer to sk151115.

SmartEvent may not correlate certain Anti-Virus logs.

In some scenarios, exporting a large number of logs to Excel may fail and cause SmartView to restart.

In a rare scenario in a ClusterXL environment, SYN Defender may incorrectly drop a valid traffic.

Some traffic may not pass when Policy Based Routing (PBR) and SecureXL are enabled. Refer to sk163252.

In some scenarios, SecureXL drops the TCP traffic for the particular connection for invalid state reasons. Refer to sk147093.

When NAT-T packets pass through a standalone gateway, this traffic may be dropped if SecureXL is enabled.

• Fix is relevant for Gaia 3.10 only.

In some scenarios, SecureXL causes an issue in the routing of multicast traffic.

In some scenarios, DOS/Rate Limiting configuration is not applied after reboot if no fw samp policy is configured.

16000 and 26000 Appliances with CPAC-4-1/10F-C NICs (using i40e driver) connected to some specific Cisco switches are flopping. Refer to sk163267.

In some scenarios, the iDRAC (LOM) interface is not pingable.

When MaaS tunnels are added, the routed process may unexpectedly exit.

In some scenarios, subnet objects may not contain all the relevant IP addresses for VMSS VMs.

Some messages in the self-help portal are not properly localized in Japanese.

In some scenarios, Endpoint Management does not start after an upgrade to R80.30 in the environment that manages both Endpoints and Gateways. Refer to sk163537.