On Mon, 9 Jul 2018 12:33:36 +0530 Thommandra wrote: TG> > Configure can exclude entire MIBs, but not individual OIDs. TG> > You can modify the code, but make sure you deal with get and TG> > get-next properly. TG> TG> Even if we comment/modify the code for individual OIDs, we TG> cannot skip OIDs that are part of a MIB Table. Right? TG> TG> I mean skip the OID in the snmpwalk o/p because OID will be TG> part of the Table Entry. Please let me know
Once you are changing code, you can make it do whatever you want. You can eliminate a column or skip certain indexes. But this will affect all users. If you only want to skip certain columns or rows by user, then you could use VACM views to exclude those objects. TG> > The size of the data field shouldn't matter. Try stepping TG> > through the mib2c generated code that creates the varbind and TG> > see where the value in the varbind gets a bad value. TG> TG> I found that the mib2c utility did not have a conversion for TG> in_addr_t type(that is used for ASN_IP_ADDRESS). Changing the TG> VAR templates of mib2c, fixed the issue. Great. Can you submit a bug report on this, along with the change you made to fix it? Thanks, Robert ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
