On Wed, 20 Jul 2005 17:02:38 +0100 Andy wrote:
AF> What I am after is snmptrapd passing the port number of the trap
AF> currently being processed to the traphandler script. So essentially, the
AF> first line from the traphandler output would be 'port:9999' (if the f/w
AF> forwarded from port 162->9999). The only other way of differentiating
AF> between the remote networks (as they may share the same private address
AF> range (this is ultimately what I am trying to achieve here!!)) is to
AF> fire up more than one snmptrapd process and traphandler.
There is no way to do it out of the box, but it probably wouldn't be too hard
to hack up your local version to do that...
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
