Bug 1729667 - snmpd must not listen on IPv6 socket on IPv4-only machine
Summary: snmpd must not listen on IPv6 socket on IPv4-only machine
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: net-snmp
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Josef Ridky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-13 09:58 UTC by Frantisek Hanzlik
Modified: 2019-07-13 09:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Frantisek Hanzlik 2019-07-13 09:58:44 UTC
Description of problem:
According to documentation, by default snmpd listens on UDP port 161 on all IPv4 interfaces. The same result should be using "udp:161" or "udp" as listening address. But all of these ways lead on the IPv4-only machine to flooding logs with messages as 
Jul 13 11:50:25 xx snmpd[19887]: ipaddress_linux: could not open /proc/net/if_inet6: No such file or directory
Jul 13 11:50:25 xx snmpd[19887]: ipaddress_linux: could not open /proc/net/if_inet6: No such file or directory

Version-Release number of selected component (if applicable):
net-snmp-5.8-10.fc30.x86_64

How reproducible:
Always - starting snmpd daemon on IPv4-only host start this problem.

Additional info:
Perhaps snmpd (maybe also snmptrapd) daemons should behave as their listening address specification tell (usual -4 / -6 cmdline switches are perhaps redundant here)


Note You need to log in before you can comment on or make changes to this bug.