I have modified snmptrapd codes, removed codes relate to sysytem service and
some other codes and options that I think I don't need, and changed main
function of snmptrapd.c into a regular function which is a child thread entry
function from a main process which in turn started by another Windows service
application.
Once my snmptrapd app is started by the Windows service app, it can
successfully recieve traps from snmptrap that reside on the same host, but it
can't recieve traps when snmptrap app is on another host (my case is a VM).
There is nothing wrong with the network because in the same situation I can
use original snmptrapd to receive traps from either of the locations; Both
snmptrapd apps listening on exactly the same IP and port, which are the default
udp:0.0.0.0:162.
I added debug code, found the select() function used in my snmptrapd app
can't detect anything so snmp_read is not called when trap is sent from another
host/VM.
Any of my code change may impact snmptrapd's select function to see traffic
from other host while see traffic from local?
May there be something wrong with the transport initialization?
Or, may Windows servcie shield the app from seeing visit from remote?
Appreciate any help.
Thanks
Gary
---------------------------------
Looking for earth-friendly autos?
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
