Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
A similar issue was fixed in BZ 1324306 which addressed upstream bug 2482.
https://sourceforge.net/p/net-snmp/bugs/2482/
However that only applied to snmp v1/v2 as noted here:
"Can you try the attached patch? It will fix the v1/v2c vs v3 issues, but multiple v3 msgs with different max sizes can still be an issue.."
And we still see the problem on RHEL 7.9 with snmp v3 and net-snmp-5.7.2-49.el7_9.1.x86_64.rpm
Sep 14 11:50:04 HOSTNAME snmpd[11083]: send response: Too long (if_nameindex() failed)
Sep 14 11:50:04 HOSTNAME snmpd[11083]: send response: Too long (if_nameindex() failed)
Sep 14 11:50:04 HOSTNAME snmpd[11083]: send response: Too long
Sep 14 11:50:04 HOSTNAME snmpd[11083]: send response: Too long
Looking through the net-snmp ChangeLog since that patch was applied upstream I came across another patch specifically for snmp v3 which looks like it might be related to the issue.
---
commit 78bf0069ddd24ea0cc716421c53e1daf46da7002
Author: Bart Van Assche <bvanassche>
Date: Wed May 15 21:25:46 2019 +0200
CHANGES: libsnmp: Increase the maximum SNMPv3 session receive size from 1472 to 2**31-1 bytes
For the UDP transport this patch increases the maximum message size from 1472
to about 64 KB.
This patch adjusts a limit that was introduced by commit 6e83b3cd891d
("respect msgMaxSize in received v3 PDUs (in the weak sense that if the
serialized response PDU is more than it, we don't send it)") # v5.7.
---
The limit referenced above appears to be from this patch from May 23, 2001.
---
https://github.com/net-snmp/net-snmp/commit/6e83b3cd891d
- respect msgMaxSize in received v3 PDUs (in the weak sense that if
the serialized response PDU is more than it, we don't send it)
- removed functions ascii_to_binary, hex_to_binary. Using these
functions is really bad, since they will happily overflow buffers.
The superior alternatives, defined in tools.h, are
snmp_{decimal, hex}_to_binary.
---
There does not appear to be a workaround.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (net-snmp bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:1202