- Nav-users - lister.unit.no

Announcement: NAV 5.18.1 released
by Morten Brekkevold 13 Mai '26

13 Mai '26

The first maintenance release of the 5.18 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 11 (Bullseye), 12 (Bookworm) and 13 (Trixie) are available in our APT repository [2]. **NB!** This will be the LAST package we publish for Debian 11 (Bullseye). ## Fixed - Fixed post-login redirect not returning users to the page they originally requested (#3954) - Fix unclickable edit button for widget titles on the dashboard. (#3980) - Fixed removal of all aliases from rooms/locations in SeedDB not being persisted on save. (#4002) - Fixed LDAP authentication unconditionally rehashing the password on every login, which invalidated the Django session auth hash and broke MFA/TOTP setup for LDAP users. (#4003) ## Release notes We always advise you to have a look at NAV's accompanying release notes [3] before upgrading. 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-18 -- Best regards Morten Brekkevold Senior engineer, The Data and Infrastructure Division Phone: (+47) 735 57 802 Sikt – Norwegian Agency for Shared Services in Education and Research www.sikt.no

1 0

NAV behind haproxy
by Einar Bjarni Halldórsson 14 Apr '26

14 Apr '26

Hi, We got NAV deployed behind haproxy and since CSRF was enabled forms don't work, including the login form. The haproxy frontend is TLS while the connection to the NAV backend is http (it's on the same host for reasons). I've tried various suggestions for django csrf behind a reverse-proxy, including adding "http-request set-header X-Forwarded-Proto https" to haproxy frontend without success. There are various django config options that are suggested, but those are not exposed through the nav.conf file. .einar

2 2

Cam Records, Multicast Packets, Broadcast Packets not populating from Cisco Catalyst 1300
by Corey Thompson 09 Apr '26

09 Apr '26

I've been using NAV for well over a decade with very few issues... Recently, we've integrated a few Cisco Catalyst 1300 series switches to our network and I do not get cam data from them, nor do I get Multicast or Broadcast packet metrics Looking at ipdevpoll log only see theses warnings: [WARNING zen.pynetsnmp.agentproxy] Packet for x.x.x.x has error: Unknown oid. OIDS: [OID('.1.3.6.1.4.1.9.9.117.1.1.2.1.2.67109505')] [WARNING nav.mibs.power_ethernet_mib.powerethernetmib] [statuscheck 192.168.3.20] device response has bad table index .17.2.99 in POWER-ETHERNET-MIB::pethPsePortTable, ignoring Which seemingly shouldn't cause the issues I'm seeing, but maybe.. Nearly 500 devices on our NAV, and I've never had to do this deep of troubleshooting with it, wondering where to start, and if anyone else has Cisco Catalyst 1300s in their NAV? Corey Thompson

2 1

Cisco Catalyst 1300 issues
by Corey Thompson 30 Mar '26

30 Mar '26

I've been using NAV for well over a decade with very few issues... Recently, we've integrated a few Cisco Catalyst 1300 series switches to our network and I do not get cam data from them, nor do I get Multicast or Broadcast packet metrics Looking at ipdevpoll log only see theses warnings: [WARNING zen.pynetsnmp.agentproxy] Packet for x.x.x.x has error: Unknown oid. OIDS: [OID('.1.3.6.1.4.1.9.9.117.1.1.2.1.2.67109505')] [WARNING nav.mibs.power_ethernet_mib.powerethernetmib] [statuscheck 192.168.3.20] device response has bad table index .17.2.99 in POWER-ETHERNET-MIB::pethPsePortTable, ignoring Which seemingly shouldn't cause the issues I'm seeing, but maybe.. Nearly 500 devices on our NAV, and I've never had to do this deep of troubleshooting with it, wondering where to start, and if anyone else has Cisco Catalyst 1300s in their NAV? Corey Thompson

1 0

Announcement: NAV 5.18.0 released
by Morten Brekkevold 30 Mar '26

30 Mar '26

The first feature release of the 5.18 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for 11 (Bullseye), Debian 12 (Bookworm) and 13 (Trixie) are available in our APT repository [2]. ## Security - The CSRF cookie is now marked as secure when needs_tls is enabled in webfront.conf, matching the existing behavior of the session cookie. (#3829) - Passwords are no longer leaked in cleartext in Django error emails when LDAP authentication crashes. (#3870) ## Removed (developer-centric) - Removed obsolete Docker-based test environment. Replaced by test suite changes that can run in 'normal' development environments. (#3849) ## Added - Rooms and locations can now have multiple names (aliases). Aliases are searchable throughout NAV -- in the navbar, global search, device history, maintenance, netmap, network explorer, status widgets, and the REST API. Aliases can be managed in *SeedDB* and via bulk import/export. They are displayed on room/location detail pages, in search results, and in SeedDB list views. (#3314, #3315, #3815, #3818, #3819, #3820, #3821, #3822, #3823, #3836, #3840, #3841, #3844, #3851, #3852, #3868, #3880, #3895) - Added support for two-factor authentication (TOTP), OAuth2, OIDC, and SAML login via django-allauth. Authentication can be configured through the new TOML config file webfront/authentication.toml. (#3622, #3676, #3834, #3862, #3873, #3889, #3934, #3936) - Added a report of devices without a known uplink in the topology. - Debug log runtimes of individual NAVbar search providers. ## Changed - Auditlog entries can now be sorted by individual columns. Hyperlinks to more details are now provided for actors, objects and targets that still exist in the NAV database. (#3776) - Updated markdown dependency to 3.8.1. (#3812) - Downgraded spammy WARNING log about alerts referencing deleted objects to DEBUG level. (#3927) ## Changed (developer-centric) - Standardize vendored JavaScript library management. Vendored JS files now follow a consistent <name>-<version>.min.js naming convention and are tracked as npm dependencies for easier version management. A vendor.py tool is included to automate installing and copying vendored files. (#2470) - Tox environments and GitHub workflows switched over to uv for dependency management. (#3859) ## Fixed - Fix network explorer search not working after the first search per page load. (#3853) - Fixed l2trace crash when tracing through a netbox with no associated prefix. (#3866) - LDAP login no longer crashes with a 500 error when a user cannot be found during group membership verification. (#3871) - Fix report column tooltips ($explain_) not showing when the column also has a $name_ override. (#3876) - Fixed a crash in SeedDB bulk import when IP addresses contain trailing whitespace. (#3884) ## Release notes We always advise you to have a look at NAV's accompanying release notes [3] before upgrading. 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-18 -- Best regards Morten Brekkevold Senior engineer, The Data and Infrastructure Division Phone: (+47) 735 57 802 Sikt – Norwegian Agency for Shared Services in Education and Research www.sikt.no

1 0

Announcement: NAV 5.17.1 released
by Morten Brekkevold 27 Feb '26

27 Feb '26

The first maintenance release of the 5.17 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 12 (Bookworm), 11 (Bullseye) and 13 (Trixie) are available in our APT repository [2]. ## Fixed - Fix collapsed multiselects in status tool filters (#3797) - Event engine now yields to overdue scheduler callbacks between processing queued events, preventing long event batches from blocking time-critical tasks. (#3798) - Added missing index on netboxentity.deviceid to speed up lookups by device. (#3794) - Fix crash when rendering navlet error responses due to missing navlet ID (#3802) - Fixed a session crash (UpdateError) on the login page that could leak cleartext passwords in Django error emails. (#3803) - Fix chart widget failing to load images from URLs without query parameters (#3805) - Fixed sc.05.16.0001.sql migration failure on PostgreSQL 14 caused by ambiguous || operator when concatenating an integer without an explicit ::TEXT cast. (#3806) - Fixed a crash in Netmap when the topology graph exceeds memcached's max item size. The graph is now returned successfully even when it cannot be cached. (#3795) - Improved active IP collector query performance (~10x) by utilizing partial database indexes on the arp table more effectively. (#3793) - PortAdmin's "commit configuration" endpoint now returns 503 instead of 500 when the device is unreachable or does not support configuration commits, and no longer triggers spurious admin error emails for these expected operational failures. (#3801) - Turned support for REMOTE_USER back on. Regression caused by the new auth-system and its complicated route to the finish line. ## Release notes We always advise you to have a look at NAV's accompanying release notes [3] before upgrading. 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-17 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Upgrade to NAV 5.16.1, navsyncdb throws error
by Ingeborg Hellemo 27 Feb '26

27 Feb '26

While trying to upgrade to NAV 5.16.1, navsyncdb throws this error: sql/changes/sc.05.16.0001.sql: operator is not unique: unknown || integer LINE 1: new_token_str := 'token #' || token_rec.id || ' (' || trunca... ^ HINT: Could not choose a best candidate operator. You might need to add explicit type casts. QUERY: new_token_str := 'token #' || token_rec.id || ' (' || truncated_comment || ')' CONTEXT: PL/pgSQL function inline_code_block line 22 at assignment PostgreSQL version 14.21 (both client and server) on FreeBSD The solution is to explicitly cast the two places where it is missing: 28c28 < new_token_str := 'token #' || token_rec.id || ' (' || truncated_comment || ')'; --- > new_token_str := 'token #' || token_rec.id::TEXT || ' (' || truncated_comment || ')'; 30c30 < new_token_str := 'token #' || token_rec.id; --- > new_token_str := 'token #' || token_rec.id::TEXT; --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

Nav 5.17.0, regression in Chart widget
by Ingeborg Hellemo 27 Feb '26

27 Feb '26

Upgraded to NAV 5.17.1 and the Chart widget did not work as in previuos versions. Example: "URL to image" = http://weather.cs.uit.no/cam/cam_south.jpg gives "Error loading image" --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

NAV 5.17.0, login problems
by Ingeborg Hellemo 27 Feb '26

27 Feb '26

Upgraded to 5.17.0, but had to roll back since login broke: [Wed Feb 25 14:53:44.458545 2026] [wsgi:error] [pid 94060] [remote 129.242.6.226:46890] [Wed Feb 25 14:53:44 2026] [WARNING] [pid=94060 nav.web.auth.middleware] User <username> denied access to /?_=1772027624097 [Wed Feb 25 14:53:44.460908 2026] [wsgi:error] [pid 94060] [remote 129.242.6.226:46890] [Wed Feb 25 14:53:44 2026] [WARNING] [pid=94060 django.request] Unauthorized: / Neither local users nor ldap-users can log in. How to debug? We do not use REMOTE_USER which is mentioned in the release notes. From webfront/webfront.conf # Should it be possible to log in with the username set in a request header # (usually REMOTE_USER)? [remote-user] # Whether REMOTE_USER authentication should be enabled enabled = no --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

Unable to upgrade nav 12 in debian 11 to any upper version.
by Secundino Grau 17 Feb '26

17 Feb '26

Hello, I have a fully working nav 5.12 instance and when I try to upgrade to 5.13, 5.14, 5.15, always have a lot of internal server errors 500 , and I'm unable to get graphite work again. If the process of upgrade is always within debian 11 packages, no success. I tested upgrading from debian 11 to 12, and then upgraded NAV but not success! Please, does anyone know if there are some steps in the upgrade process that I have missed? Thanks in advance, S. Grau

2 2