Resolved issues
The following issues have been resolved in FortiAP-U version 6.2.2. For more details about a particular bug, visit the Fortinet Customer Service & Support website.
|
Bug ID |
Description |
|---|---|
| 616096, 666613 | Implement WPA3-Enterprise 192-bit encryption (using AES-GCM-256), WPA3-Enterprise only and WPA3-Enterprise Transition. |
| 649153 | FAP-U incorrectly reported interfering AP with RSSI of -12dBm. |
| 659638 | When FAP-U24JEV LAN port is configured as "bridge-to-ssid", multicast traffic over the LAN port was getting dropped. |
| 662313 | When WAN-LAN mode is enabled and the LAN port is bridged to a local-standalone SSID with NAT enabled, the NAT configuration could not work. |
| 665798 | When background scan is enabled, clients could experience ping loss when AP executes scan. |
| 684349 | FAPs were not failing over between primary and secondary FGTs when inter-controller-mode is in "1+1" fast failover mode. |
| 707932 | Low TCP throughput was observed for mesh link on 5GHz radio of FAP-U422E. |
| 708745 | Fixed an issue that some wireless clients were disconnected at midnight due to daily automatic channel selection (ACS) scanning. |
|
723584 |
Supports a new Bluetooth low energy (BLE) chipset in FAP-U231F. |
|
727279 |
FAP-U units got disconnected from FortiLAN Cloud with the reason "received unexpected discovery". |
Common vulnerabilities and exposures
FortiAP-U 6.2.2 is no longer vulnerable to the following CVE-References:
|
Bug ID |
CVE References |
|---|---|
| 719019 |
FRAG attack
|
Visit https://fortiguard.com for more information.