I'm using the lib through the python wrapper yapsnmp. It uses the netsnmp 'session' object to do the job. Whatever I put in the 'remote_port' member of the session object, it seems netsnmp always uses 161.
After a (quick) look to the sources, it seems indeed that 'session.remote_port' is not used when binding to the peer: the function to look into seems to be 'netsnmp_sockaddr_in()' (in snmpUDPDomain.c), and it's always called with its third argument (remote_port) equal to 0. I didn't see any report related to that in sourceforge bugs / patches lists. Is it a bug or is there something I misunderstood ? netsnmp version: 5.1.1 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
