Upstream has a patch for a bug in 5.4 caused by net-snmp believing that an IP address is present on more than one interface. The URL points to the upstream bug report; last update at time of writing was that the patch was requested to go into 5.4.1-rc1. As there are a number of reports of bugs in 5.4 fixed by patches from upstream, please consider adding an ebuild (testing would be fine) that includes these upstream patches. Reproducible: Always Steps to Reproduce: 1. Build net-snmp-5.4 from portage ebuild 2. Start snmpd Actual Results: Error messages appear in syslog every 20 seconds. Expected Results: No error messages every 20 seconds OR a warning message at startup. The issue has also been reported when using interface bonding (my situation I believe, as I don't have IP addresses on more than one interface). When I build 5.4 including the upstream patch, I get the following single message at startup: snmpd[21091]: Duplicate IPv6 address detected, some interfaces may not be visible in IP-MIB which is the behaviour that the patch produces.
Created attachment 123282 [details] Output from "emerge --info"
Created attachment 123283 [details, diff] Upstream patch for "duplicate IP address" bug This is the patch from upstream that resolves the issue I'm seeing. I created a "net-snmp-5.4-r1.ebuild" in my portage overlay with just the epatch to apply it, and it cleanly builds for me.
For completeness, the diff to show what I did to make the ebuild... --- /usr/portage/net-analyzer/net-snmp/net-snmp-5.4.ebuild 2007-05-18 06:38:30.000000000 +1000 +++ /usr/local/portage/net-analyzer/net-snmp/net-snmp-5.4-r1.ebuild 2007-06-28 01:36:12.000000000 +1000 @@ -40,6 +40,7 @@ cd "${S}" epatch "${FILESDIR}"/${P}-makefile.patch + epatch "${FILESDIR}"/net-snmp-5.3.1-shared-ip-2.patch # The lm_sensors patch has a memory leak # If you can help, please attach a patch to bug 109785
This has been fixed in our 5.4.1 ebuild with upstream patch from Robin Johnson
