On Mon, 11 Jun 2012 14:07:37 +0200 Jan wrote: JS> >> As a matter of fact the first version of my reply did mention clientAddr JS> >> but then I looked in the code and saw that we are setting JS> >> client_addr.sin_port to 0, and that kills any address binding. JS> > ^^^^^^^ JS> JS> I now have a request to bind to a port too, someone wants to have very JS> strict firewall + SELinux rules and wants snmpd to send traps from fixed JS> port. Would anyone be against extending clientaddr to (optionally) bind JS> to a given port?
I'm fine with a new optional ability to bind to a port for trunk. ------------------------------------------------------------------------------ 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-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
