> you mean the new snmpd is working correctly but net-snmp is not? this > doesn't surprise me, there were some issues with net-snmp in the past, > this was one of my reasons to start working on a new implementation. >
yes, concerning i'm just graphing interface traffic via mrtg/cacti > there is no conflict between net-snmp and "opensnmpd", they do not > share any configuration and, unlike net-snmpd, the openbsd snmp daemon > does not parse any ASN.1 MIB files on runtime and uses a compiled-in > mib implementation. the only possible conflict is listening on udp > port 161 (snmp). > well, in my case seems it's not port conflict. could it possible the build in mib somehow effecting net-snmp mibs environment ? considering its not respond to oid query from net-snmp while respond to same query from "opensnmpd" also previous query from net-snmp show machine uptime, and now show system uptime, same like "opensnmpd" query thanks agung
