On 10/10/06, Juergen Schoenwaelder <[EMAIL PROTECTED]> wrote: > c) The opposite of b) would be to require that each transport provides > its own check function in order to localize the problem. The proper > way to do this would be to add a additional function pointer to the > netsnmp_transport structure and to call the ..._getSecName() > function indirectly using this function pointer.
That feels the cleanest solution in the medium term. And I've got a reasonable idea about how to implement this. But closer investigation of the code seems to indicate that it's actually only TCP/IPv4 that was broken by the recent change. (Since the UDP/IPv4 code was changed - including the Community->Security name mapping routine.) The UDP/IPv6 and TCP/IPv6 seems to be untouched, so should still continue to work (although I'm not currently in a position to check this). I've just commited a patch to the TCP/IPv4 processing, to bring this in line with the new UDP/IPv4 approach. So the trap receiver now successfully accepts incoming traps over TCP. That's probably sufficient for the 5.4 release. I'm a little reluctant to try re-working this code significantly, so late in the release cycle. But I'm sure that we can come up with something better for 5.5 (and provide an official patch that can be applied to the 5.4 code for those that wish to try it). Dave ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
