16.2 Changelog: Difference between revisions
No edit summary |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
= | = 16.2 = | ||
16.2 | 16.2 brings the ability to use WPA-2 Enterprise for wireless network authentication. With this release, NG Firewall can be set up as a [[RADIUS Server]] to authenticate local or Active Directory users when joining the wireless network. | ||
For more information, see | For more information, see the [[RADIUS Server]] and [[RADIUS Proxy]] documentation. | ||
= Bug Fixes & Updates = | == Bug Fixes & Updates == | ||
* Fix: WireGuard licensing issues on startup | * Fix: WireGuard licensing issues on startup | ||
* Fix: QoS & IPsec issues on Lanner NCA-4210B hardware | * Fix: QoS & IPsec issues on Lanner NCA-4210B hardware | ||
* Fix: Port forwards on 443/80 not working after 16.0.1 upgrade without changing service ports | * Fix: Port forwards on 443/80 not working after 16.0.1 upgrade without changing service ports | ||
* Fix: TLS v1.3 causing website loading issues | * Fix: TLS v1.3 causing website loading issues | ||
* IPS signatures updated | * IPS signatures updated | ||
* Updates for applications list for Application Control app | * Updates for applications list for Application Control app | ||
== Note on upgrades == | |||
The RADIUS Server requires UDP ports 1812 and 1813 to be accessible from your access points if you intend to use the WPA2-Enterprise authentication feature added to this release. Access rules are added by default for new installations, but not for upgrades. Refer to the Access Rules section of the [[RADIUS Server]] documentation for details. | |||
= 16.2.1 = | |||
16.2.1 is a minor release that resolves bugs in the [[RADIUS Server]] introduced by version 16.2.0. | |||
== Bug Fixes == | |||
* Fixed RADIUS rules not added during upgrade | |||
* Fixed RADIUS name mapping not working due to incorrect script permissions | |||
* Fixed login names by RADIUS truncated at 10 characters | |||
* Fixed Winbind service not starting after enabling RADIUS Proxy | |||
* Fixed Freeradius server failing to start on upgrades | |||
= 16.2.2 = | |||
16.2.2 is a minor release that resolves an upgrade issue introduced in the 16.2.1 release. | |||
Latest revision as of 15:38, 3 May 2022
16.2
16.2 brings the ability to use WPA-2 Enterprise for wireless network authentication. With this release, NG Firewall can be set up as a RADIUS Server to authenticate local or Active Directory users when joining the wireless network.
For more information, see the RADIUS Server and RADIUS Proxy documentation.
Bug Fixes & Updates
- Fix: WireGuard licensing issues on startup
- Fix: QoS & IPsec issues on Lanner NCA-4210B hardware
- Fix: Port forwards on 443/80 not working after 16.0.1 upgrade without changing service ports
- Fix: TLS v1.3 causing website loading issues
- IPS signatures updated
- Updates for applications list for Application Control app
Note on upgrades
The RADIUS Server requires UDP ports 1812 and 1813 to be accessible from your access points if you intend to use the WPA2-Enterprise authentication feature added to this release. Access rules are added by default for new installations, but not for upgrades. Refer to the Access Rules section of the RADIUS Server documentation for details.
16.2.1
16.2.1 is a minor release that resolves bugs in the RADIUS Server introduced by version 16.2.0.
Bug Fixes
- Fixed RADIUS rules not added during upgrade
- Fixed RADIUS name mapping not working due to incorrect script permissions
- Fixed login names by RADIUS truncated at 10 characters
- Fixed Winbind service not starting after enabling RADIUS Proxy
- Fixed Freeradius server failing to start on upgrades
16.2.2
16.2.2 is a minor release that resolves an upgrade issue introduced in the 16.2.1 release.
