Magnus Fromreide wrote:
> 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?
Shouldn't the fix be in the library code, rather than apps/snmptrap.c?
Otherwise, any other existing third-party code doing similar things and relying
on our backwards-compat promise would hit the same issue, wouldn't it?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
