Resolved issues
The following issues have been resolved in FortiAP-S and FortiAP-W2 version 6.4.3. For inquiries about a particular bug, visit the Fortinet Support website.
|
Bug ID |
Description |
|---|---|
| 637609 | Adds 5GHz DFS channel 144 for region “K” (Korea). |
|
643738 |
During FAP firmware upgrading process, FAP-221E/223E units were reset (power cycled) by the peer HPE PoE Switch for the LLDP timeout. As a result, FAP upgrade failed and couldn’t boot up. |
| 654244 | FAP SNMP function and Fortinet-FortiAP-MIB need fapModel Object ID and support sysObjectID query. |
|
658235 |
FAP-421E and FAP-423E in region “A” capped transmit power on channel 36-48 at 12dBm. |
|
661863 |
FAP-221E Radio-1 suffered poor performance due to spectral-analysis scan. |
|
667391 |
WiFi clients couldn't re-connect to FAP every morning for DARRP caused a channel mismatch. |
|
667700 |
WiFi clients couldn't ping each when having connected to the same FAP and the same bridge SSID with tagged VLAN ID. |
|
669674 |
DNS IP was shown in reverse manner in wireless event logs. |