Kevin Conway wrote:
Thanks. The "offending" directives were "trapsink 127.0.0.1 public"
ones. However, I would not have expected these to listen on ports
32768(9) on all interfaces, ie "0.0.0.0:32768 LISTEN" when the
directives contain 127.0.0.1. Is this bug?
In general, net-snmp has no knowledge what *destination* address (like
the one listed in a trapsink line) is reachable over which interface or
source address. localhost probably could be treated as a special case
but isn't.
However, you can *configure* the agent's source address for sending
notifications by specifying
[snmp] clientaddr <IP address>
which can even be 127.0.0.1 if you send to/from localhost only. Does it
work for you?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
