I hope I'm missing something real basic. If you're doing an snmpwalk
and it comes up to write-only variables, I can understand not printing
anything for those variables, but should it then skip the "peer"
variables just beyond those? (By peer I mean they're at the same
OID depth as the previous v
On Tue, 4 May 2010, Jacob Steinberger wrote:
> From looking at the mailing list, this issue was last reported in
> 2007 but appears to still be an issue today.
>
> When running Net-SNMP on a linux based system, Net-SNMP duplicates ppp
> interfaces based on the number of connects/disconnects
On Fri, 13 Nov 2009, Dave Shield wrote:
> No - that fix won't have been ported to 5.3.x,
> because the file defaultrouter_linux.c isn't
> present in the 5.3.x line.
>It's not there in 5.4.x either - it's new in 5.5
> (and a version of this fix has been applied).
OK, I see that Red Hat has inc
We're using V5.3.2.2 on RHEL 5.4, and there's still bug 2081243. An snmpwalk
can freeze after:
...
IP-MIB::ipv6ScopeZoneIndexB.8 = Gauge32: 0
IP-MIB::ipv6ScopeZoneIndexC.7 = Gauge32: 0
IP-MIB::ipv6ScopeZoneIndexC.8 = Gauge32: 0
IP-MIB::ipv6ScopeZoneIndexD.7 = Gauge32: 0
IP-MIB::ipv6ScopeZoneInde
