Date: Mon, 18 Nov 2019 16:22:32 -0500 From: "Michael W. Lucas" <mwlucas@michaelwlucas.com> To: ports@freebsd.org Subject: net-snmp crash Message-ID: <20191118212232.GA4543@mail.mwl.io>
next in thread | raw e-mail | index | archive | help
Hi, I can reliably crash net-snmp with an snmpset. Worth a formal bug report? $ uname -a FreeBSD freebsdtest 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 GENERIC amd64 $ pkg info net-snmp net-snmp-5.7.3_20,1 Name : net-snmp Version : 5.7.3_20,1 Installed on : Wed Oct 9 15:22:24 2019 EDT ... Detail: $ sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 0 $ snmpget freebsd IP-MIB::ipForwarding.0 IP-MIB::ipForwarding.0 = INTEGER: notForwarding(2) $ snmpset freebsd IP-MIB::ipForwarding.0 i 1 Timeout: No Response from freebsd Yep, the agent is dead: $ pgrep snmpd $ The sysctl change took place, however: $ sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 I can restart the agent and reverse the change, but snmpd crashes again. So: worth a bug report, or no? ==ml -- Michael W. Lucas https://mwl.io/ author of: Absolute OpenBSD, SSH Mastery, git commit murder, Immortal Clay, PGP & GPG, Absolute FreeBSD, etc, etc, etc...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191118212232.GA4543>