snmptrapd info for Fedora users

I spent an hour looking at syslog, tcpdump output, itpables, and tried
all kinds of snmptrapd logging options (syslog and file) and was posting
to this list to ask for help when the cluebat struck me just before I
side-kicked the old packard smell monitor.

hosts.allow

ok the fact that hosts.allow was the cause since i didnt have this entry
in it is not the big problem

snmptrapd:192.168.1.1:ALLOW

The problem was debugging this issue. Is it something with Net SNMP or
tcp wrappers that never put in syslog a connection refused message?

syslog entry was *.* /dev/tty9  so everything should have been logged. 

Had I saw a log entry saying connection refused I would have realized
it. 

Anyhow I am not sure if this truly is a bug (ie did fedora compile
something wierd) or if it is a bug, is it net-snmp's interaction with
wrappers or vice versa.

So im sending here to see if anyone else has seen this before

-Greg



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@xxxxxxxxxxxxxxxxxxxxx
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users