On Thu, May 3, 2012 at 2:00 AM, Dave Shield <[email protected]> wrote: > On 3 May 2012 06:34, Stéphane Charette <[email protected]> wrote: >> Any idea why snmpd would listen on a different UDP port every time it is >> restarted? > > Have you got any trap destinations set up in the snmpd.conf file? > I have a feeling that these will each open a socket for communicating > with the remote trap receiver. It's possible that this is what you are > seeing.
Thanks, Dave. Correct. If I comment out the trap2sink line, then snmpd doesn't open up a random UDP listening port. Here is the line line that causes this problem for us: > trap2sink udp:127.0.0.1:162 blah So now I have 2 questions: 1) Why does having a trap2sink (not informsink) cause snmpd to open up a listening socket on a random UDP port? 2) If this is required, is there a way to limit the interface to a single IP address instead of having it use 0.0.0.0? Our devices have many IP addresses, several of which are internal for management purposes, but many of which are public-facing. Having a daemon open up additional unexpected ports on those IP addresses is problematic. snmpd is being limited to a single IP address using lines such as this in snmpd.conf: > agentaddress udp:192.168.1.22:161,tcp:192.168.1.22:161 Thanks for your insight. Stéphane Charette ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
