The first maintenance release of the 5.2 series of NAV is now out!
This release fixes a particularly nasty regression bug in pping, which
would prevent you from being alerted about boxDown events. If you are
already running 5.2.0, we recommend that you upgrade as soon as
possible.
The source code is available for download at GitHub [1].
A new package for Debian 10 (Buster) is available in our APT repository
[2] as usual. Packages for Debian 11 (Bullseye) have not been built yet.
Please be extra aware of config file changes. Look out for `*.dpkg-dist`
files in /etc/nav and make sure to update your running config.
The virtual appliance has been updated.
Changes
=======
* #2304 (Display alert severity values in the event/alert details
page)
* #2306 ([BUG] pping is unable to report unreachable devices in NAV
5.2.0)
* #2308 ([BUG] Alert Profile severity filters that ship with NAV are
outdated)
Please see the release notes [3] for more details. Happy NAVing
everyone!
Links
=====
[1] https://github.com/Uninett/nav/releases
[2] https://nav.uninett.no/install-instructions/#debian
[3] https://nav.readthedocs.io/en/latest/release-notes.html#nav-5-2
--
Sincerely,
Morten Brekkevold
Uninett
The initial feature release of the 5.2 series of NAV is now out!
The source code is available for download at GitHub [1].
A new package for Debian 10 (Buster) is available in our APT repository
[2] as usual. Packages for Debian 11 (Bullseye) have not been built yet.
Please be extra aware of config file changes. Look out for `*.dpkg-dist`
files in /etc/nav and make sure to update your running config.
The virtual appliance has been updated.
Changes
=======
User-visible features and improvements:
* #1928 (Document 802.1X support of PortAdmin for end users)
* #2289 (Add config option to disallow editing of uplinks and
downlinks in PortAdmin)
* #2295 (Redefine alert severity levels and make them configurable)
* #2297 (Document the event and alert type hierarchy)
Fixed GitHub issues in this release:
* #2296 ([BUG] Portadmin save API incorrectly returns 500 error where
400 is appropriate)
* #2298 ([BUG] PortAdmin RpcError on JunOS 20 and newer)
Please see the release notes [3] for more details. Happy NAVing
everyone!
Links
=====
[1] https://github.com/Uninett/nav/releases
[2] https://nav.uninett.no/install-instructions/#debian
[3] https://nav.readthedocs.io/en/latest/release-notes.html#nav-5-2
--
Sincerely,
Morten Brekkevold
Uninett
Hi,
I deployed NAV 5.14 on a debian 10 VM and configured LDAP authentication as from https://nav.readthedocs.io/en/latest/reference/ldap.html?highlight=ldap - however if using LDAP the login works randomly (need to try 2 to 5/6 time to login) while LDAPS never works. I did a test with ldapsearch on the same VM using both LDAP and LDAPS and both works so no issues with basedn or manager credentials nor with certificates. Is anyone else experiencing the same issue ? Other LDAPS based applications we use internally sucessfully connect to same AD servers.
Anyone can help maybe?
Thanks!
Andrea