I am working with net-snmp 5.7.3, and will be using several Sub-Agents in
my project, with fairly large amounts of data. I have noted that issuing a
'snmpbulkwalk' to Master Agent results in this broken down into GETNEXT
requests to the Sub-Agent. This results in a lot of network traffic, as
Den 04-03-2015 kl. 10:17 skrev Gleb Smirnoff:
I see, you use { CTL_NET, PF_ROUTE, 0, 0, NET_RT_IFLIST, 0 };
I'd suggest to use getifaddrs(3), it uses more modern sysctl
NET_RT_IFLISTL, note the L at end. And the library function
takes the burden of parsing the stuff.
That looks interesting.
Niels,
On Wed, Mar 04, 2015 at 09:06:11PM +0100, Niels Baggesen wrote:
N Den 04-03-2015 kl. 10:17 skrev Gleb Smirnoff:
N I see, you use { CTL_NET, PF_ROUTE, 0, 0, NET_RT_IFLIST, 0 };
N
N I'd suggest to use getifaddrs(3), it uses more modern sysctl
N NET_RT_IFLISTL, note the L at end. And
I like to convert an existing net-snmp based agent in to windows extention
agent by providing required wrapper apis like
SnmpExtensionInit
SnmpExtensionTrap
SnmpExtensionQuery
and to do ofcorse need to convert the structure of windows net-snmp .
I looked at the
On Mon, Mar 02, 2015 at 09:33:30PM +0100, Niels Baggesen wrote:
N Den 27-02-2015 kl. 22:22 skrev Gleb Smirnoff:
N Now time for net-snmp, which isn't piece of cake. And I'd like
N to get it done properly, and not to store a patch in FreeBSD port
N for ages, but to integrate the patch right in