Resolved issues
The following issues have been resolved in FortiAP-U version 7.0.2. For more details about a particular bug, visit the Fortinet Customer Service & Support website.
Bug ID |
Description |
---|---|
825539 |
Some
SSIDs from the managed FAP-U units were detected as ' |
863798 |
Wi-Fi 6 FAP-U models sometimes would not operate on the channel as configured from the FortiGate. |
897778 |
Fixed multiple kernel crash issues in FAP-U431F and FAP-U433F. |
912996 |
Fixed
a |
937983 |
When FAP-U432F is in dual-5G mode and the channel list is empty in radio-2, the operating channel should be set as NULL. |
942034 |
WAN port 802.1X authentication failed when the peer switch port also enabled MAC-based authentication. |
944427 |
Fixed
a kernel panic issue |
945799 |
FAP-U would sometimes become stuck when managed by a cluster of HA FortiGate units. |
947713 |
FAP-U could not assign dynamic VLAN ID to clients on SSID with RADIUS-based MAC authentication. |
948575 |
Ekahau tag blink-mode packets were dropped due to a channel mismatch error. |
950659 |
FAP-U radio configuration should update the EIRP value and also send the update to the FortiGate. |
953018 |
Fixed
a kernel panic issue |
958777 |
Fixed
a kernel panic issue |
965249 |
Fixed a Tx-Power display issue when the power-level is set to 0%. |
965318 |
FAP-U422E Mesh-Ethernet bridge dropped VLAN packets. |
982617 |
Some Android-based devices could not connect as FAP-U sent de-authentication frames. |
Resolved UTM issues
Bug ID |
Description |
---|---|
813972 | FAP-U should upgrade the embedded IPS engine to the new version. |