Resolved issues
The following issues have been resolved in FortiAP version 7.2.1. For inquiries about a particular bug, visit the Fortinet Support website.
|
Bug ID |
Description |
|---|---|
|
790245 |
Sometimes,
FortiAP could not reconnect to FortiLAN Cloud and received error message:
" |
|
796778 |
FortiAP should be able to clear RADIUS-based MPSK cache per MAC address and shorten the cache timeout (300 ~ 864000 sec, 0 to disable caching). |
|
797019 |
FortiAP should generate DNS process success logs for wireless stations. Note: FortiGate won't generate such logs due to the high volume. |
|
798677 |
A notice-level wireless event log should be generated when Probe Request is dropped due to low RSSI. |
|
801972 |
Wireless event logs should be generated when wireless clients get deauthenticated or disassociated. |
|
817235 |
FAP-431F would randomly change DFS channel to 0 after detecting a radar signal. |
|
820997 |
FortiAP units were sending an excessive amount of CPU and memory statistics to FortiLANCloud. |
|
821831 |
PoE Mode Configured value and Operating value were shown inconsistently on FortiAP GUI. |
Common vulnerabilities and exposures
FortiAP 7.2.1 is no longer vulnerable to the following common vulnerabilities and exposures (CVE) references:
|
Bug ID |
Description |
|---|---|
|
786638 |
CVE-2022-29058 (Command injection in CLI). |
Visit https://fortiguard.com for more information.