10.5.1 Release Notes
What's New in Version 10.5.1
SecureEdge version 10.5.1 is a major release. It contains several important fixes.
Resolved Bugs and Improvements in Release 10.5.1
The firmware update status reporting for SecureEdge Integrated Firewalls no longer attempts to use deprecated endpoint, and therefore no longer causes HTTP 404 errors. [BNNGF-100475]
DHCP interfaces in standby/on-demand mode now come up correctly after a configuration sync, so SecureEdge firewalls keep their internet connectivity and continue receiving configuration updates. [BNNGF-100531]
Support for configuring the TS Agent authentication has been implemented. [BNNGF-100817]
A redirect rule for one of the following management IPs, which are 169.254.128.1 or 169.254.128.2, has been added for traffic coming from allowed IPs of the TS Agent configuration on TCP port 5050 to a LAN IP of the SE appliance. [BNNGF-100819]
Adding a Secure Connector box to a SecureEdge Edge Service now updates BGP routing gracefully, without restarting the routing service, so existing routes and traffic are no longer briefly interrupted. [BNNGF-100838]
SecureEdge firewalls now synchronize their configuration through the WAN hub reliably, without occasionally getting stuck and missing configuration updates. [BNNGF-100975]
SecureEdge firewalls now continue to synchronize their configuration successfully, including when a tunnel-disabling condition such as an invalid license occurs. [BNNGF-100979]
Standalone SecureEdge appliances now recover automatically and resume regular configuration synchronization after a restart or a temporary failure, without requiring manual intervention. [BNNGF-101088]
SecureEdge configuration updates no longer cause duplicate statis routes with identical metrics, and configuration activation now works as expected. [BNNGF-101154]
The BCMC rule has been refined so that multicast traffic will not be dropped anymore and rather will be cloned to all WSG bridge members. [BNNGF-101542]
On SecureEdge‑managed CloudGen Firewalls, Zero Trust Network Access (ZTNA) rules are now enforced exactly as configured, so users can reach only the applications their ZTNA policy explicitly permits. [BNNGF-101674]
Known Issues 10.5.1
General Known Issues
ACL Rule – Setting up the source or destination criteria to all Sites and Private Edge services results in the same networks configured on the box. [SWCS-3988]
Dashboards – For SecureEdge appliances running version < 9.0.3, adding more than one filter can keep the other filter(s) from being applied or might return no results.
Identity Management – The Barracuda SecureEdge Identity app for Google Workspace is currently awaiting official approval from Google.
SIP – The use of a SIP proxy with SecureEdge might still require manual adjustments in the configuration files depending on the SIP setup. [BNNGF-95603]
Proxy Connect – Proxy Connect block pages are not visible to the end user. [BNNGF-96048]
Proxy Connect – Proxy Connect fails when the Action is set to Alert/Warn in Web Filter policies. [BNNGF-96138]
Firewall – A client using SecureEdge Access Agent and ZTNA policy rules can unauthorizedly access internal resources, if the resource is not HTTP/HTTPS and the access is done via the IP address of the resource and not using the FQDN. [BNNGF-102226]
Known Issues Related to Azure Log Analytics (OMS)
On boxes with Azure Log Analytics (OMS) activated, the phibs service does not restart automatically after update. To get the service running, a reboot is required.