Hi Dave
>Sorry if I sounded a bit sharp last week.
>Supporting this software does get a bit frustrating at times.
I completely understand, I feel the same when any forum posts only part of the
fix to a problem.
We do enable the IPv6 support in the makefile. It looks like when Net SNMP is
configured on Ubuntu system, all the default MIBs are used, I mean without the
configure options
--with-out-mib-modules="$(SNMP_MIB_MODULES_EXCLUDED)" \
--with-mib-modules="$(SNMP_MIB_MODULES_INCLUDED)" \
So I removed these two lines from the makefile of the target(openWRT machine)
and now I could see the result with out any seg fault for getsubtree, gettable
and getbulk and walk(request timesout here as I enabled the debugging). Once I
disable debugging I think walk should also work fine, but before that I wanted
to confirm with you is this a good idea to remove these two lines from the make
file? Do we face any performance issues with that?
Thanks and Regards,
Malathi
--- On Mon, 4/12/10, Dave Shield <[email protected]> wrote:
From: Dave Shield <[email protected]>
Subject: Re: Seg fault when querying for the UDP table
To: "Malathi Panyam" <[email protected]>
Cc: [email protected]
Date: Monday, April 12, 2010, 12:48 AM
On 11 April 2010 00:21, Malathi Panyam <[email protected]> wrote:
> Hi Dave,
> Sure, once I figure out the fix, I will definitely update the users
> list.
Thanks.
Sorry if I sounded a bit sharp last week.
Supporting this software does get a bit frustrating at times.
> I tried to debug further on OpenWRT machine at netsnmp_old_api_helper() and I
> saw
> 260 cvp->findVar = vp->findVar;
> (gdb) print vp->findVar
> $6 = (FindVarMethod *) 0x757f4 <var_tunnelIfEntry>
>
>
> Where as on Ubuntu where everything works fine looks like
> 260 cvp->findVar = vp->findVar;
> (gdb) print vp->findVar
> $1 = (FindVarMethod *) 0x7f6c5e13fa80 <var_udp6>
>
> I could not understand why the handler's "findVar" got asssigned to
> "var_tunnelIfEntry"
> instead of "var_udp6"..Am I missing something fundamentally?
var_udp6 is the (old-style) handler routine for the 'ipv6UdpTable', which
does come immediate after the udpTable in the OID ordering.
The next two subtrees of mib-2 (egp(8) and cmot(9)) aren't implemented
by the Net-SNMP agent, so the handler following that would typically be
something under transmission(10). Most likely either 'dot3' or 'tunnel',
depending on what code is included in the agent.
So it's not unreasonable that var_tunnelIfEntry comes fairly soon.
As for why var_udp6 is not included, that might well depend on what
options were passed to 'configure'. For example, did this include or
exclude IPv6 support? What MIB modules were included or excluded
from the build?
Dave
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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
