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.
DescriptionDalibor Pospíšil
2016-04-13 14:28:08 UTC
This issue seems to be present also here net-snmp-5.7.2-24.el7
+++ This bug was initially created as a clone of Bug #1227640 +++
Description of problem:
When running snmpd on a machine with IPv6 UDP listening enabled (used udp6:161 as
argument), the snmpwalk program is unable to connect to the server from another
machine on the same network.
I'm using net-snmp version 50.el6_6.1. This is the result when I try with the
IPv6 address of the machine in question:
[root@server-prod01 ~]# snmpwalk -Os -c public -v 1 2001:700:110:1::80 system
No log handling enabled - turning on stderr logging
snmpwalk: Unknown host (2001:700:110:1::80) (No such file or directory)
[root@server-prod01 ~]#
strace show that the program do not try to connect to the other end at all.
Because the machines in question only have IPv6 connectivity between them, we need
to use IPv6.
--- Additional comment from Jan Safranek on 2015-10-22 13:34:24 CEST ---
net-snmp-5.5-54 in RHEL6 does support IPv6, just the address specification is not that obvious. The format is: udp6:ipaddr:port or udp6:[ipaddr]:port (so ':' in IPv6 address does not clash with ':' before port).
I tested today that all these works:
snmpget ... udp6:::1:161
snmpget ... udp6:[::1]:161
Indeed, these do not work (and they work in recent net-snmp-5.7.3-7.fc23) :
snmpget ... ::1:161
snmpget ... [::1]:161
We need to backport https://sourceforge.net/p/net-snmp/code/ci/df863a5348aabf71bbca7bfefcf8beb8bb9e7762 into RHEL 6. Please use 'udp6:' prefix in the meantime.
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, 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-2017:1863