Built-in IPS engine
Resolved engine issues
|
Bug ID |
Description |
|---|---|
|
644638 |
Policy with a Tor exit node as the source is not blocking traffic coming from Tor. |
|
713508 |
Low download performance occurs when SSL deep inspection is enabled on aggregate and VLAN interfaces when nTurbo is enabled. |
|
718503 |
High memory usage by IPS. |
|
754579 |
Application performance is ten times worse when IPS is applied in flow mode. |
|
757314 |
IPS engine crashes after upgrading to 6.4.7 and is affecting traffic. |
|
759194 |
FortiGate seems to have inserted wrong the timestamp into the PCAP data. |
|
765859 |
Repeated IPS engine signal 11 and signal 7 crashes occur. |
|
770685 |
Traffic does not match the security policy with SD-WAN zone (PPPoE interface) in NGFW mode. |
|
774957 |
Web filter URL static filter is blocking all traffic. |
|
777464 |
The |
|
779278 |
FortiGate is responding on TLS 1.0, TLS 1.1, and SSLv3 on TCP port 8015. |
|
781894 |
When using a web filter in NGFW mode, websites do not open according to the correct matching policy. |
|
781898 |
FortiGate cannot be upgraded from 7.0.3. |
|
790490 |
Shared memory is not released and causes the device to enter into conserve mode. |
|
792312 |
HTTPS traffic cannot pass ESXi FortiGate VM when IPS and deep inspection are enabled. |
|
794872 |
FG-5001E blade IPS engine application crashed during the traffic testing. |
|
811213 |
High CPU usage on IPS engine (7.00124 and 7.00126) when CP is enabled. |
