RE: SNMPD error (ASAP)
"Mike Ayers" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <83E753BE7B6A324ABB336245BAF1DAAC08E258E3@mailserver.metatv-ds.metatv.com> |
> From: [email protected] > [mailto:[email protected]] On > Behalf Of Umesh Kamath > Sent: Monday, July 14, 2008 12:04 PM > 1) Please let me know the use of "snmpTrapdAddr. My > understanding on snmpTrapdAddr is that, it should always bind > to localhost(loop back address(127.0.0.1)) No. That would only permit you to receives traps from the local host. The most common value for snmpTrapdAddr is 0.0.0.0, which means, "listen on all IPv4 interfaces, including localhost", which means that notifications may be directed to any of the hosts' interfaces, including 127.0.0.1, and be received. For production systems it is common practice to restrict the listening to a single back end network interface so traffic from the internet at large is summarily ignored. This has nothing to do with which hosts may send notifications to your listener. The only mechanism to screen IP addresses is the "authCommunity" statement - see the snmptrapd.conf man page for details. HTH, Mike ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users