Maxim> It looks as tkined only listens for snmp traps v1 with
Maxim> community name public. When I send it with different community
Maxim> name it refuses to catch them completely. Is it possible to
Maxim> change this behaviour, because I badly need it?
Scotty 2.1.X indeed filters traps based on the community. If you want
to receive traps from different communities, you have to create
multiple snmp sessions with the relevant community strings. You can
code this into the snmp_monitor.tcl script. The proc TrapSink creates
the listening SNMP session. It should be straight forward to put a
list of SNMP sessions into the static ts variable and to develop a
more intelligent scheme to read the community strings from e.g. the
tkined.defaults file.
BTW, scotty 3.0.X does not filter traps anymore. It accepts any traps
and passes them to the callback. It is then the responsibility of the
receiving callback to throw away traps that are not wanted. There are
additional % substitutions so that you can access the community string
(or the context in SNMPv3). This behaviour is more consistent with the
new SNMPv3 architecture.
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.