Hi Craig, Thanks for the update. I just tried the lastest package version, but it seems that RFC1212 and RFC1215 are still not generated. It seems that the RFC files included in the packages are not patched.
> The IETF MIBs are shipped with the downloader, so I can include them > and then patch the RFC using the standard Debian quilt patching. Are you sure standard patching is applied for Debian native packages? IIRC that was only for non-native packages? > That must be some old switch, most MIBs these days do not use RFC-1212/1215 > but instead are based upon SNMPv2-SMI. > SNMPv2-SMI was originally defined in RFC-1442 in 1993, so what we are > dealing with is MIBs that are really old, or using the wrong > definition. I'm working with the Netgear GS324T introduced in 2019, so not a super old switch. On the support package, I can download a package of MIBS, which includes a (I assume) old version of BRIDGE-MIB that still depends on 1155/1212/1213/1215. Based on your remarks I did try using the newer BRIDGE-MIB from your package, and loading SMNPv2-MIB instead of RFC123-MIB from my code, and that also appears to work with this switch. I suspect that these newer MIBs define attributes that are not actually supported by the switch, but everything I need for my application [1] seems to work (with your 1.7 package, since AFAICS this does still need the IANA-ENTITY-MIB because I need ENTITY-MIB). [1]: https://github.com/matthijskooijman/netgear-vlan-admin Still, I would say it is good to make the package supply 1212/1215 as well, since that makes it more internally consistent. > My concern is that RFC-1212 has a circular dependency with RFC-1213 so > there might be an issue anyway. Ah, you mean that 1212 import DisplayString from 1158 (which is not shipped) but DisplayString is usually provided by 1213? Looking at the 1212 file supplied by Netgear, they commented out the RFC1158-MIB import from RFC-1212. With that, I can load the MIBs just fine. Also, if I manually extract RFC-1212 from the rfc file and *not* comment out the RFC1158-MIB import, it also works (likely because the parser handles imports lazily and 1213 defines DisplayString before using OBJECT-TYPE). This might be implementation dependent, though. I use the python snimpy package, which uses libsmi to parse MIB files. I also have only confirmed that the MIBs load correctly, not that the new OBJECT-TYPE macro is actually used (not sure how to check in my setup). I also tried with snmpwalk from Net-SNMP, which also seems to work (but that command also works when RFC-1212 does not exist, or when I specify non-existent MIB names on the commandline, so not sure how much this really tells us): snmpwalk -m ENTITY-MIB -m IF-MIB -m RFC1213-MIB -m BRIDGE-MIB -m Q-BRIDGE-MIB -v2c -c public 192.168.1.1 Gr. Matthijs
signature.asc
Description: PGP signature
