Any idea why snmpd would listen on a different UDP port every time it is
restarted?
Things are working for us on Ubuntu, but on our Debian Lenny devices
running net-snmp v5.4.1 the same configuration results in snmpd opening 2
udp listening ports instead of the single port we'd expect.
For example, if the IP address of the box is 192.168.1.111, this is what we
see:
# netstat -lnup | grep snmp
udp 0 0 0.0.0.0:63493 0.0.0.0:*
5031/snmpd
udp 0 0 192.168.1.111:161 0.0.0.0:*
5031/snmpd
udp 0 0 127.0.0.1:162 0.0.0.0:*
5035/snmptrapd
Having snmpd on port 161 and snmptrapd on port 162 is expected. What I
cannot figure out is why snmpd is also listening on all interfaces on port
63493. Every time I run "/etc/init.d/snmpd restart" that stray UDP port
keeps changing to some seemingly random value.
Here are parts of what I think are the relevant configuration files:
# cat /etc/default/snmpd
export MIBDIRS=/usr/share/snmp/mibs
SNMPDRUN=yes
SNMPDOPTS='-Lf /dev/null -u snmp -g snmp -I-smux -p /var/run/snmpd.pid'
TRAPDRUN=yes
TRAPDOPTS='-Lf /dev/null -u snmp -g snmp -p /var/run/snmptrapd.pid'
SNMPDCOMPAT=yes
# head -7 /etc/snmp/snmpd.conf
file /var/log/snmp.log 1
agentuser snmp
agentgroup snmp
agentaddress udp:192.168.1.111:161,tcp:192.168.1.111:161
# agentxsocket tcp:localhost:705
master agentx
agentxtimeout 2
Thanks in advance for any pointers.
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
