Barracuda NAC 5.3 for Windows
System Requirements
Operating Systems |
|
---|
Version 5.3.6
Barracuda Network Access Client version 5.3.6 contains all improvements and features delivered with version 5.3.5.
Updating to Barracuda Network Access Client 5.3.6 is possible for any prior version.
Improvements Included with Barracuda Network Access Client 5.3.6
VPN throughput performance with high data-transfer rates has been improved. (BNNGF-94632)
An Installer issue causing the installation to abort has been resolved. (BNNGF-94897)
A UI display issue with VPN Always On mode has been fixed. (BNNGF-94412)
Version 5.3.5
Barracuda Network Access Client version 5.3.5 contains all improvements and features delivered with version 5.3.4.
Updating to Barracuda Network Access Client 5.3.5 is possible for any prior version.
What's New with Barracuda Network Access Client 5.3.5
Single Sign-on for SAML authentication with WebView2 Plugin is now supported. (BNNGF-93320)
Improvements Included with Barracuda Network Access Client 5.3.5
VPN Server and Alternate Port Probing performance has been improved. (BNNGF-94327)
VPN service is now reconnecting properly when using Direct Access. (BNNGF-94099)
An issue with the VPN Always On feature during initial connect after system startup has been fixed. (BNNGF-94100)
An issue with application time frame firewall rules has been fixed. (BNNGF-94148)
A UI issue with VPN profile configuration has been fixed. (BNNGF-94411)
Version 5.3.4
Barracuda Network Access Client version 5.3.4 contains all improvements and features delivered with version 5.3.3.
Updating to Barracuda Network Access Client 5.3.4 is possible for any prior version.
What's New with Barracuda Network Access Client 5.3.4
AD probing can now be restricted to a configurable port and uses only LDAPS by default. (BNNGF-90949)
A new troubleshooting menu option for clearing browser cookies (SAML authentication) has been added. (BNNGF-92109)
Improvements Included with Barracuda Network Access Client 5.3.4
AD probing is now working properly when no DNS server is reachable. (BNNGF-75204)
An issue with packet loss on the virtual adapter under high traffic load has been fixed. (BNNGF-88191)
Network route is now introduced properly when using an access control service. (BNNGF-90202)
Credential provider installation status on ARM64 is now detected properly. (BNNGF-90345)
Version 5.3.3
Barracuda Network Access Client version 5.3.3 contains all improvements and features delivered with version 5.3.2.
Updating to Barracuda Network Access Client 5.3.3 is possible for any prior version.
Improvements Included with Barracuda Network Access Client 5.3.3
VPN service no longer crashes when disconnected from VPN. (BNNGF-87586, BNNGF-86895)
Network routes are now introduced correctly if Automatic Private IP Addressing (APIPA) is disabled. (BNNGF-87284)
Network routes are now introduced appropriately if prior VPN connection was not terminated correctly. (BNNGF-89196)
Installation of Credential Provider on ARM64 is now working correctly. (BNNGF-89565)
Packets with incomplete/malformed IP header are no longer sent through VPN tunnel. (BNNGF-89555)
Version 5.3.2
Barracuda Network Access Client version 5.3.2 contains all improvements and features delivered with version 5.3.1.
Updating to Barracuda Network Access Client 5.3.2 is possible for any prior version.
What's New with Barracuda Network Access Client 5.3.2
Barracuda Network Access Client is now available from the Microsoft App Store. (BNNGF-84784)
Improvements Included with Barracuda Network Access Client 5.3.2
Version 5.3.2 only contains a small change that was needed for publishing the client on the Microsoft Store.
Version 5.3.1
Barracuda Network Access Client version 5.3.1 contains all improvements and features delivered with version 5.3.0.
Updating to Barracuda Network Access Client 5.3.1 is possible for any prior version.
What's New with Barracuda Network Access Client 5.3.1
VPN reconnect process no longer gets stuck when using SAML authentication. (BNNGF-81657)
VPN profiles created on older NAC versions are now migrated properly. (BNNGF-83236)
Version 5.3.0
Barracuda Network Access Client version 5.3.0 contains all improvements and features delivered with version 5.2.x.
Updating to Barracuda Network Access Client 5.3.0 is possible for any prior version.
What's New with Barracuda Network Access Client 5.3.0
As of Barracuda Network Access Client version 5.3.0, administrators can limit the number of VPN connection attempts.
VPN client now supports DNS-resolved VPN routes. (BNNGF-76270) *)
Support for additional encryption algorithms and key agreement protocols has been added. (BNNGF-75860) *)
Support for “Optimized” tunnel mode has been added. (BNNGF-75941) *)
Client can now use a server-configured certificate chain with the VPN server certificate. (BNNGF-76773) *)
NAC Light now supports disk encryption checks. (BNNGF-72949) *)
VPN client can now use a server-configured MTU size for the virtual adapter. (BNNGF-76494) *)
*) requires Barracuda CloudGen Firewall 8.3.0 or higher
Barracuda Network Access Client 5.3.0 supports Barracuda CloudGen WAN Personal Access for point-to-site connections from the VPN client to the VPN service of Barracuda CloudGen WAN. For more information, see How to Enable Personal Access Using the Authentication Client and Barracuda CloudGen WAN / User Connectivity & Personal Security.
Barracuda Network Access Client 5.3.0 supports ARM64 hardware platform. (BNNGF-64759)
Improvements Included with Barracuda Network Access Client 5.3.0
OS version reporting for VPN clients has been improved. (BNNGF-80163)
UI behavior when displaying welcome messages has been improved. (BNNGF-75559)
Users can now delete associated Windows Credential Manager entries when removing a VPN profile. (BNNGF-67295)
Client no longer crashes when tunnel compression is processing certain non-IP packets. (BNNGF-81389)
AD probing behavior has been improved. (BNNGF-81359, BNNGF-81286)
A displaying issue in the Authentication Client has been fixed. (BNNGF-81137)
Personal Firewall: Display of IGMP packets has been improved. (BNNGF-58210)
Alternate port is now used properly during VPN reconnection attempts. (BNNGF-81507)
VPN connect process no longer loops when using fallback profiles. (BNNGF-81129)