On Mon, 2008-09-29 at 14:22 -0400, Nicholas Jones wrote:
> I am looking at snmpd. I noticed that if you pass a LISTENING
> ADDRESSES it will still listen on port 161. Why not just have the
> listening address override the default ports? I am thinking that I
> would like to install an adapter between snmpd and the rest of the
> world. This is to take care of a proprietary chunk of software.
> It seams that the LISTENING ADDRESSES over writting the default
> ports should be the default behavoir.
> Should I make the changes to the snmp_api.c and submit a patch?


I just tried to repeat your bug (using 5.5) and the command line
snmpd udp:127.0.0.1:5555
and netstat then told me that snmpd used no port but 5555.

Could you please indicate what version you are using, how you call it,
what you expect to happen and what really happens.

/MF




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.p...r_id=100&url=/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders