>>>>> On Wed, 24 Nov 2004 16:56:15 +0800, "Francis Tay" <[EMAIL PROTECTED]> >>>>> said:
Francis> 1) Is there a API call to get the target and source IP Francis> addresses from an Francis> incoming SNMP packet? No, and there is a reason too... (technically, actually, it can be done but I'm going to argue against doing it). You want to support things independently of the transport it came in over if at all possible. That lets you use the same results over a non-IP based system in the future. Francis> 2) Is there an alternative to achieving what I wish to do? Yes. 1) SNMPv3 actually has "contexts" which let you do things the way you want. You register each mib implementation under a different context, and you let the context distinguish which thing you're talking to. If you're using SNMPv1, Net-SNMP 5.2 (due out today) will have the support to map SNMPv1 communities into SNMPv3 contexts so you can have a different community name per serial device. Or if you're using SNMPv3 (which I'd recommend) you simply have a different context name per device. 2) Put the device "name" or other identifier into every table index set that you implement. That way when you implement a table, it'll show you the information about all your devices not just one (each row in the table would be assigned to a particular device). -- Wes Hardaker Sparta ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
