Built-in IPS engine
Resolved engine issues
Bug ID |
Description |
---|---|
695464 |
IPS engine has high CPU utilization due to recursive function call. |
698247 |
Flow mode web filter |
713508 |
Low download performance occurs when SSL deep Inspection is enabled on aggregate and VLAN interfaces when nTurbo is enabled. |
752466 |
Deep inspection is causing downloads to fail in an ADVPN environment. |
752559 |
IPS engine 6.00410 has signal 11 crash when upgrading. |
754579 |
Application performance is ten times worse when IPS is applied in flow mode. |
755223 |
There is no detection trigger packet in the PCAP. |
755294 |
Firefox gives |
756398 |
An invalid character string is inserted in the IPS log sent to the TCP Syslog server. |
757314 |
IPS engine crashes after upgrading and is affecting traffic. |
759194 |
FortiGate seems to have inserted wrong the timestamp into the PCAP data. |
760555 |
Web filter UTM logged unexpected URLs, such as |
765859 |
Repeated IPS engine signal 11 and signal 7 crashes occur. |
774826 |
IPS processes consume high CPU usage. |
775566 |
Some websites do not load with flow-based and deep SSL inspection. |
777464 |
The |
780194 |
IPS engine 7.00105 has |
786479 |
Traffic log does not work in NGFW mode, but a reboot can solve the issue on an FG-101E. |
787151 |
FortiGate inserts the epoch time into the PCAP when detected by some signatures. |
792312 |
HTTPS traffic cannot pass ESXi FortiGate VM when IPS and deep inspection are enabled. |
797229 |
DDoS exploit occurs due to TCP asymmetrical routing being enabled. |
801575 |
IEC 61850 and MMS signatures do not work. |
802465 |
|