trapsink directive creates a socket on a random ephemeral port

Hi,

I am trying to understand why when I have a trapsink directive in snmpd.conf, snmpd creates a socket which listens for UDP connections on a random ephemeral port.

For example I have configured this in the snmpd config to send traps to 192.168.1.5:

trapsink 192.168.1.5 public

And for some reason, I now have three sockets:

~]# netstat -ntupl | grep [s]nmpd
tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN 8998/snmpd
udp 0 0 0.0.0.0:49689 0.0.0.0:* 8998/snmpd
udp 0 0 0.0.0.0:161 0.0.0.0:* 8998/snmpd

I know that 161 is for SNMP polling requests and 199 is for SMUX, but what is the purpose of the socket which listens on UDP port 49689 here?

- Jeremy

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d

_______________________________________________
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