packages/net/net-snmp/files, branch master

net-snmp: fix 'bad number' warning when engineidtype is unset

2026-06-23T07:12:16Z

Add a -n guard before the arithmetic comparison of engineidtype in snmpd_engineid_add(). When the engineid UCI section exists but engineidtype is not configured, the empty string is passed to [ -ge ]/[ -le ] which causes 'sh: bad number' on every boot. Signed-off-by: Michael Pfeifroth

net-snmp: fix service not restarting on config change

2026-06-16T08:36:52Z

snmpd generates its runtime configuration in /var/run/snmpd.conf from UCI during start_service(). However, since the procd instance command line never changes, procd does not detect that a restart is needed when the UCI config is modified. Add 'procd_set_param file /etc/config/snmpd' so procd tracks the config file and restarts snmpd when it changes. Without this, 'reload_service' (triggered by procd_add_reload_trigger) re-creates an identical instance definition and procd skips the restart, leaving stale configuration active. This also fixes a usability issue with SNMPv3: when changing a user's authentication or privacy algorithm, net-snmp must restart to re-derive localized keys via createUser. Without the restart, the daemon keeps using cached key material and authentication fails. Tested with net-snmp 5.9.4 on OpenWrt (aarch64 and ppc64). Signed-off-by: Michael Pfeifroth

net-snmp: add distro extend using /etc/os-release

2026-03-24T06:30:51Z

Read PRETTY_NAME from /etc/os-release via /bin/sh for distro output. Bump PKG_RELEASE to account for the package configuration change. Signed-off-by: Kamil Bienkiewicz

net-snmp: fix newline when RestrictOID is neither yes nor no

2026-03-11T08:07:04Z

snmpd_access_default_add, snmpd_access_HostName_add, and snmpd_access_HostIP_add check if RestrictOID is `yes` or `no` but fail to write a newline for other values of RestrictOID (e.g., `true`, `false`) or if unset, corrupting the generated config. Fix by using config_get_bool and restructuring to write either a complete line or nothing. Also require RestrictedOID to be non-empty when RestrictOID is enabled. This is a breaking change for configs where RestrictOID is set to a value that the old code did not match as `yes` (e.g., `true`, `1`, `on`, `enabled`) but config_get_bool evaluates as true. In practice, this is unlikely to affect existing installs unless a user is unknowingly relying on unintended behavior or is deliberately relying on the old code's non-standard boolean evaluation; this latter case is considered unlikely by this commit's author. Configs where RestrictOID is enabled but RestrictedOID is empty are also affected; previously a directive with a trailing space was written, now no directive is written. Signed-off-by: Eric McDonald

net-snmp: add early return when IPMask is unset

2026-03-11T08:07:04Z

snmpd_access_HostIP_add would write unintended output to the config file if the IPMask option is not specified. Add an early return to prevent writing in that case. This is a breaking change for configs where IPMask is unset. Previously, an empty IPMask option would result in a malformed directive containing a trailing slash with no guaranteed newline, the exact form of which depended on the values of other options. Now, no directive is written. Signed-off-by: Eric McDonald

net-snmp: add early return when HostIP is unset

2026-03-11T08:07:04Z

snmpd_access_HostIP_add would write unintended output to the config file if the HostIP option is not specified. Add an early return to prevent writing in that case. This is a breaking change for configs where HostIP is unset. Previously, an empty HostIP option would result in a malformed directive containing a bare /mask with no guaranteed newline, the exact form of which depended on the values of other options. Now, no directive is written. Signed-off-by: Eric McDonald

net-snmp: add early return when HostName is unset

2026-03-11T08:07:04Z

snmpd_access_HostName_add would write unintended output to the config file if the HostName option is not specified. Add an early return to prevent writing in that case. This is a breaking change for configs where HostName is unset. Previously, an empty HostName option would result in a malformed directive with a trailing space and no guaranteed newline, the exact form of which depended on the values of other options. Now, no directive is written. Signed-off-by: Eric McDonald

net-snmp: add early return when CommunityName is unset

2026-03-11T08:07:04Z

snmpd_access_default_add, snmpd_access_HostName_add, and snmpd_access_HostIP_add would write unintended output to the config file if the CommunityName option is not specified. Add an early return to each function to prevent writing in that case. This is a breaking change for configs where CommunityName is unset. Previously, an empty CommunityName option would result in a malformed directive with a double space and no guaranteed newline, the exact form of which depended on the values of other options. Now, no directive is written. Signed-off-by: Eric McDonald

net-snmp: add early return when Mode is unset

2026-03-11T08:07:04Z

snmpd_access_default_add, snmpd_access_HostName_add, and snmpd_access_HostIP_add would write unintended output to the config file if the Mode option is not specified. Add an early return to each function to prevent writing in that case. This is a breaking change for configs where Mode is unset. Previously, an empty Mode option would result in a malformed directive with a leading space and no guaranteed newline, the exact form of which depended on the values of other options. Now, no directive is written. Signed-off-by: Eric McDonald

net-snmp: fix literal string test in snmpd_sink_add

2025-12-14T21:52:39Z

The function snmpd_sink_add() has a guard clause that tests the literal string "section", not the variable value "$section". The test `[ -n "section" ]` always evaluates to true because the string literal "section" is non-empty, making the check useless. This function is only called internally with hardcoded arguments, so the bug has no actual impact currently. For the same reason, this change should not break existing configurations. However, I think it should be fixed so future callers do not have a false sense of security. Signed-off-by: Eric McDonald