On lör, 2006-12-16 at 10:34 +0100, Magnus Fromreide wrote:
> Ahrg! Does the attached patch correct the problem for you?
>
> The problem is that snmp_open() calls
> netsnmp_tdomain_transport_full("snmp", ...) and this tells the library
> that when it looks for default values to use then it should use the
> "snmp" domain, and there port 161 is reasonable. In this case we should
> have told it to use the "snmptrap" domain. That is all the patch does.
>
> Another thing is that maybe NETSNMP_DS_LIB_DEFAULT_PORT should have
> higher precedence than the value from the domain transport lookup?
>
> In any case the attached patch or something along those line should be
> used as it is more correct than the current code.
In fact this patch isn't good enough - I am working on a more complete
patch that removes more special cases to make it work as intended but it
won't happen today as I have to leave.
/MF
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
