On 9 September 2011 20:31, Tang, Peter <[email protected]> wrote: > Look like the forward function only has two options: forward traps base on > OID or Default
Essentially, yes. That's how the snmptrapd trap handling is modelled - given such-and-such a notification, what should be done with it? That could be logging the trap, forwarding it to another destination, or passing it to a script (or some combination of these) > Anyone know how can the forward function be used to forward traps base on IP > address ? > For example, forward IP123 <destination host> Source-based filtering has never really been part of the SNMP framework, and it's certainly not currently supported within snmptrapd. The simplest way to add this would probably be to write a traphandler script (registered as a 'default' handler), which would examine the source information and decide whether to forward it or not. Or you could do this in code, by making a copy of the existing 'forward_handler' routine, and tweaking that. But this functionality is not present as things stand. Dave ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
