Cameron> Anyone had success sending and receiving traps on a port
Cameron> other than 162? I haven't. I've worked with Scotty
Cameron> 2.1.4 and 2.1.5, and I've tried various combinations of
Cameron> launching processes, but I have yet to convince Scotty
Cameron> to receive a trap on a higher port (such as 2162). I
Cameron> *think* I'm getting a "#snmp trap ..." command to communi-
Cameron> cate with straps, but nothing seems to go beyond that.
Sending traps to arbitrary ports works. However, the current version
is not able to receive traps from ports != 161. I agree that this
limitation should be removed. However, this requires first to clearly
distinguish between manager and agent sessions. The -port session
option is currently completely overloaded (sometimes it defines the
destination port for a trap PDU, sometimes it defines the destination
port of SNMP requests, sometimes it defines the local port where a Tnm
agent receives requests). It is my intention to clearly distinguish
between SNMP manager and agent session and to add -trapaddress,
-trapport and -trapcommunity configuration options. This ensures that
these options will have well defined semantics.
However, I am not sure if this will all be implemented in the 2.2.0
release. (I can either delay the next release until this work is
finished or I can make a new release earlier and add these things as
one of the patches. Note that the second option will introduce small
incompatibilities in the Tcl API which is probably a bad thing to do
without incrementing the minor version number.)
Juergen
-- Juergen Schoenwaelder schoenw@cs.utwente.nl http://www.cs.utwente.nl/~schoenw Computer Science Department, University of Twente, (Fax: +31-53-489-3247) P.O. Box 217, NL-7500 AE Enschede, The Netherlands. (Tel. +31-53-489-3678)