> Anyone interested in sharing why the ifXTable, ifTestTable, ifStackTable > are not implemented in net-snmp 5.1.1.
Because up to now, no-one has actually sat down and implemented them. > is there any contraint in implementing these groups or what? The main constraint tends to be time. Remember that this is an Open Source project, and none of us are paid to be involved with it. The time we spend on it has to be fitted around the work that we *are* paid to do. So implenting new MIBs (or extensions to existing ones) tends to be driven by individual requirements. If no-one has had a specific need for access to the ifXTable information, then it's correspondinly less likely to happen. > If i want to implement these tables then what should i do? Start by retrieving the main CVS code base, where there *is* now an initial implementation of these tables. I haven't looked at the code recently, so I don't know how complete it is, but that's likely to be the most sensible starting point. > where to get the information about the statistics of incoming > and outgoing multicast & broadcast packets? Yes - that's usually the hardest problem. Not least becaause it's typically different on different O/S's. So there isn't a single answer that fits all systems. Also, you're asking in the wrong place - we're mostly SNMP experts here. If you need to find out how to retrieve a particular network statistic, you'll probably need to ask the kernel developers for that particular O/S. They'd be able to tell you how to get hold of this information (and whether it's available at all). This list is likely to be more help in guiding how you use that information once you've got hold of it. > Also, i found that ifAdminStatus is not implemented in linux and only > implemented for win32. why the same is not implemented for linux? Historical Reasons. The Linux implementation is a direct development of the original CMU agent, which had a slightly confused approach to the Admin and Oper status objects. (The same holds true for most of the other Unix-based systems). These two objects were never really implemented properly. And as indicated above - no-one has had the requirement to address this. The Windows implementation is significantly newer, so may well have been written with the benefit of subsequent experience, and hence got these objects right. (I assume - I haven't actually checked). But again, have a look at the CVS code. I'd expect that Robert's new re-write should be addressing this problem, and be implementing these objects correctly. Dave ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
