Fortinet black logo

Version:

7.2.3
7.2.2
7.2.1

Version:

7.2.0
7.0.9
7.0.8

Version:

7.0.7
7.0.6
7.0.5

Version:

7.0.4
7.0.3
7.0.2

Version:

7.0.1
7.0.0
6.4.11

Version:

6.4.10
6.4.9
6.4.8

Version:

6.4.7
6.4.6
6.4.5

Version:

6.4.4
6.4.3
6.4.2

Version:

6.4.1
6.4.0
6.2.12

Version:

6.2.11
6.2.10
6.2.9

Version:

6.2.8
6.2.7
6.2.6

Version:

6.2.5
6.2.4
6.2.3

Version:

6.2.2
6.2.1
6.2.0

Version:

6.0.16
6.0.15
6.0.14

Version:

6.0.13
6.0.12
6.0.11

Version:

6.0.10
6.0.9
6.0.8

Version:

6.0.7
6.0.6
6.0.5

Version:

6.0.4
6.0.3
6.0.2

Version:

6.0.1
6.0.0
5.6.14

Version:

5.6.13
5.6.12
5.6.11

Version:

5.6.10
5.6.9
5.6.8

Version:

5.6.7
5.6.6
5.6.5

Version:

5.6.4
5.6.3
5.6.2

Version:

5.6.1
5.6.0
5.4.13

Version:

5.4.12
5.4.11
5.4.10

Version:

5.4.9
5.4.8
5.4.7

Version:

5.4.6
5.4.5
5.4.4

Version:

5.4.3
5.4.2
5.4.1

Version:

5.4.0
5.2.15
5.2.14

Version:

5.2.13
5.2.12
5.2.11

Version:

5.2.10
5.2.9
5.2.8

Version:

5.2.7
5.2.6
5.2.5

Version:

5.2.4
5.2.3
5.2.2

Version:

5.2.1
5.2.0
5.0.14

Version:

5.0.13
5.0.12
5.0.11

Version:

5.0.10
5.0.9
5.0.8

Version:

5.0.7
5.0.6
5.0.5

Version:

5.0.4
5.0.3
5.0.2

Table of Contents

FortiOS Release Notes

6.4.10
7.2.3
7.2.2
7.2.1
7.2.0
7.0.9
7.0.8
7.0.7
7.0.6
7.0.5
7.0.4
7.0.3
7.0.2
7.0.1
7.0.0
6.4.11
6.4.10
6.4.9
6.4.8
6.4.7
6.4.6
6.4.5
6.4.4
6.4.3
6.4.2
6.4.1
6.4.0
6.2.12
6.2.11
6.2.10
6.2.9
6.2.8
6.2.7
6.2.6
6.2.5
6.2.4
6.2.3
6.2.2
6.2.1
6.2.0
6.0.16
6.0.15
6.0.14
6.0.13
6.0.12
6.0.11
6.0.10
6.0.9
6.0.8
6.0.7
6.0.6
6.0.5
6.0.4
6.0.3
6.0.2
6.0.1
6.0.0
5.6.14
5.6.13
5.6.12
5.6.11
5.6.10
5.6.9
5.6.8
5.6.7
5.6.6
5.6.5
5.6.4
5.6.3
5.6.2
5.6.1
5.6.0
5.4.13
5.4.12
5.4.11
5.4.10
5.4.9
5.4.8
5.4.7
5.4.6
5.4.5
5.4.4
5.4.3
5.4.2
5.4.1
5.4.0
5.2.15
5.2.14
5.2.13
5.2.12
5.2.11
5.2.10
5.2.9
5.2.8
5.2.7
5.2.6
5.2.5
5.2.4
5.2.3
5.2.2
5.2.1
5.2.0
5.0.14
5.0.13
5.0.12
5.0.11
5.0.10
5.0.9
5.0.8
5.0.7
5.0.6
5.0.5
5.0.4
5.0.3
5.0.2
Download PDF
Copy Link

New features or enhancements

More detailed information is available in the New Features Guide.

Bug ID

Description

718332

In previous DARRP implementation, channel bandwidth was not considered. Now, DARRP will also consider the radio bandwidth in its channel selection, adding support for 40, 80, and 160 MHz channel bandwidth.

745135

The FortiGate will default to one of the internet service databases depending on its platform, and this database cannot be changed.

753368

Add support for 802.1X under the hardware switch interface on NP6 platforms: FG-30xE, FG-40xE, and FG-110xE.

759344

NP7 CAPWAP offloading for WiFi traffic now supports VLAN-related features such as dynamic VLANs and VLAN stacking (also called QinQ or inner VLANs).

787477

Ensure that session synchronization happens correctly in the FGCP over FGSP topology.

  1. When the session synchronization filter is applied on FGSP, the filter will only affect sessions synchronized between the FGSP peers.
  2. When virtual clustering is used, sessions synchronized between each virtual cluster can also be synchronized to FGSP peers. The peers' syncvd must all be in the same HA vcluster.

New features or enhancements

More detailed information is available in the New Features Guide.

Bug ID

Description

718332

In previous DARRP implementation, channel bandwidth was not considered. Now, DARRP will also consider the radio bandwidth in its channel selection, adding support for 40, 80, and 160 MHz channel bandwidth.

745135

The FortiGate will default to one of the internet service databases depending on its platform, and this database cannot be changed.

753368

Add support for 802.1X under the hardware switch interface on NP6 platforms: FG-30xE, FG-40xE, and FG-110xE.

759344

NP7 CAPWAP offloading for WiFi traffic now supports VLAN-related features such as dynamic VLANs and VLAN stacking (also called QinQ or inner VLANs).

787477

Ensure that session synchronization happens correctly in the FGCP over FGSP topology.

  1. When the session synchronization filter is applied on FGSP, the filter will only affect sessions synchronized between the FGSP peers.
  2. When virtual clustering is used, sessions synchronized between each virtual cluster can also be synchronized to FGSP peers. The peers' syncvd must all be in the same HA vcluster.