esn't use this approach because it doesn't
need any configuration.
Bill
>
>
> I’m very new to the net-snmp API, so I’m sort of still finding my feet.
>
>
>
> Regards,
>
>
>
> Tim
>
>
>
>
>
> *From:* Bill Fenner [mailto:fen...@gma
On Wed, Mar 4, 2015 at 11:51 AM, Thomas Besemer
wrote:
> 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
On Thu, Mar 5, 2015 at 1:39 PM, Thomas Besemer
wrote:
>
>
> On Thu, Mar 5, 2015 at 7:37 AM, Bill Fenner wrote:
>
>> On Wed, Mar 4, 2015 at 11:51 AM, Thomas Besemer > > wrote:
>>
>>> I am working with net-snmp 5.7.3, and will be using several Sub-Agen
On Sat, Mar 7, 2015 at 4:39 PM, Thomas Besemer
wrote:
>
>
> On Fri, Mar 6, 2015 at 10:39 AM, Bill Fenner wrote:
>
>> On Thu, Mar 5, 2015 at 1:39 PM, Thomas Besemer
>> wrote:
>>
>>>
>>>
>>> On Thu, Mar 5, 2015 at 7:37 AM, Bill Fenner
What net-snmp version are you using?
https://sourceforge.net/p/net-snmp/bugs/2611 seems to have established that
while these files are read, they have no effect in net-snmp 5.7.3 because
the security parameters are read from the data store before the file is
read.
Bill
On Sat, Apr 4, 2015 at 1
Try:
SNMP::register_debug_tokens("read_config,snmp_build,snmp_send,snmpv3");
$SNMP::debugging = 2;
to see what it's doing. In theory the per-host files are read deep inside
the transport, which perl can't avoid using, but using the debugging may
help see what's happening. When I was reading the
You don't mention which helper you're using, but if you're using the
table_iterator, is the not-accessible column in
your column_info->details.list?
Bill
On Mon, Apr 27, 2015 at 6:47 AM, Tim Culhane
wrote:
> Hi,
>
> I believe it is correct for index objects in a mib to be marked as
> 'not-ac
On Tue, Apr 28, 2015 at 7:33 AM, Tim Culhane
wrote:
> Does anybody know if it is possible to get the ‘MAX-ACCESS’ value for an
> oid from a request via the net-snmp API?
>
mib2c has access to it (and in theory it's in charge of getting that info
into the code). There's no access to this info fr
On Sat, Nov 28, 2015 at 9:00 AM, Tim Cox wrote:
>
> My agent (which is *not* NET_SNMP) may be obliged to force zero bits onto
> the front of unsigned data
>
> * counter*
>
> * TimeTicks*
>
> * gauge*
>
> I don't think an agent should need to do this, but manager NET-SNMP
> version: 5.4.2.1 is dis
On Sun, Mar 6, 2016 at 4:36 PM, Magnus Fromreide
wrote:
> On Sat, Mar 05, 2016 at 02:59:55PM -0800, Bart Van Assche wrote:
> > On 03/03/16 19:05, Robert Story wrote:
> > > On Sat, 20 Feb 2016 19:36:20 -0800 Bart wrote:
> > > BVA> On 02/05/16 17:35, Robert Drake wrote:
> > > BVA> > The perl guys a
Hi Sam,
I think you'll find this is just a documentation weakness -
in pass_common.c:netsnmp_internal_pass_parse, you can see if the type is
"octet", it's parsed by netsnmp_internal_asc2bin(), which seems to parse
space-separated octets, e.g., "00 e0 ec 00 52 6d".
Bill
On Mon, Aug 1, 2016 at
Sam,
I have two "big ideas" here; one is already published so, can you run your
test case against the code here:
https://github.com/fenner/net-snmp/tree/V5-7-fix-view-filtering
The diffs are
https://github.com/fenner/net-snmp/compare/V5-7-travis...fenner:V5-7-fix-view-filtering
The other "big i
On Mon, Nov 28, 2016 at 11:44 PM, bart
wrote:
>
> The branch, V5-7-patches has been updated
> 413eb441c2f71298cd07ff0c480505ba62cad8bb ->
> 920f20b745da6c90c56a68d6d1ea782ca4fc074b
>
> ...
> create mode 100644 include/net-snmp/library/netsnmp-attribute-format.h
>
>
My code that builds outsid
On Tue, Dec 13, 2016 at 1:47 AM, Bart Van Assche
wrote:
> On 12/12/2016 08:56 PM, Bill Fenner wrote:
>
>> On Mon, Nov 28, 2016 at 11:44 PM, bart > <mailto:bvass...@users.sourceforge.net>> wrote:
>>
>>
>>
snmp_enum.c has been (very reasonably) changed to
use register_const_config_handler(). This confounds --with-minimalist,
though, because snmp_enum.c doesn't require the feature.
I see two ways forward here:
1. Make register_const_config_handler unconditional. It's used by
snmp_enum.c and snmp_en
Now I get a fair number of
cc1: warning: unrecognized command line option "-Wno-implicit-fallthrough"
Would it be better to try __attribute__((fallthrough))? Or, only add the
-W flag if the compiler supports it?
Bill
On Mon, Apr 10, 2017 at 12:44 AM, bart
wrote:
> This is an automated ema
On Tue, Apr 11, 2017 at 11:40 AM, Bart Van Assche
wrote:
> On Tue, Apr 11, 2017 at 8:27 AM, Bill Fenner wrote:
> > Now I get a fair number of
> >
> > cc1: warning: unrecognized command line option
> "-Wno-implicit-fallthrough"
> >
> > Would it be b
On Tue, Apr 11, 2017 at 11:51 AM, Magnus Fromreide
wrote:
> On Tue, Apr 11, 2017 at 10:27:42AM -0500, Bill Fenner wrote:
> > Now I get a fair number of
> >
> > cc1: warning: unrecognized command line option
> "-Wno-implicit-fallthrough"
> >
>
Hi Soubhagya,
What kind of system is running the SNMP server that you're querying? E.g.,
it's Debian 7 running net-snmp 5.7.3, or ...? (Not the client, which
you've already said is net-snmp 5.7.3).
Bill
On Mon, Apr 24, 2017 at 12:22 PM, Soubhagya Panigrahi <
srpanigrahi1...@gmail.com> wrote
You have to implement the "save" and "load" persistent data. If using the
mfd mib2c system, for example, you can answer:
This table has writable columns. Do you want to generate
code for writeable columns, or restrict the table to read-only?
1) generate code with writeable columns [DEFAULT]
Linux platform with 2.6.23 kernel
> verison.
>
> One more info : I googled about this issue and found below patch.
> https://bugzilla.redhat.com/attachment.cgi?id=98840&action=diff
>
> --
> *Regards*,
> Soubhagya
>
>
> On Tue, Apr 25, 2017 at 6:03 PM, Bill Fenner
re of
> this issue with 2.6.32 kernel version.
>
> Really looking forward for some pointers.
>
> Thank you in advance.
>
>
> On Tue, Apr 25, 2017 at 10:25 PM, Bill Fenner wrote:
>
>> I am afraid I don't have anything to add - I have no experience with such
>>
On Mon, Jun 5, 2017 at 10:55 AM, Madhusudhana R
wrote:
> Hi Coders,
>
>
>
> My query is, does net-snmp support heterogeneous trap types?
>
> More precisely, is it possible to send traps with different data types
> like integer signed/unsigned/32bit/64bit , strings etc. during same
> execution
>
On Mon, Jun 5, 2017 at 9:04 AM, deepak.sachan deepak.sachan <
deepak.sac...@deal.drdo.in> wrote:
> hi,
> My agent is slow in responding to the request.
> so how can i increase time out value??
>
http://net-snmp.sourceforge.net/docs/man/snmpcmd.html
Madhu,
How are you supplying the values to net-snmp? Many of these can be
explained by net-snmp's internal representation (e.g., using "uint32" for
non-negative types, so supplying -1 turns into UINT32_MAX inside C, without
any explicit behavior on net-snmp's part. A lot of these limitations are
;
> 2. COUNTER64 exceeding UINT64_MAX should wrap around but currently
> it remains at UINT64_MAX and does not wrap.
>
>
>
> Please comment on these 2 points.
>
>
>
> Also I am still not able understand how to use BITSTRING type. I don’t
> know how the input
Are you sure it is a memory leak, or is it simply the NOTIFICATION-LOG-MIB
implementation?
Does the memory usage still increase when you run with
"--doNotRetainNotificationLogs=yes" or the equivalent in snmptrapd.conf?
Bill
On Tue, Jul 11, 2017 at 3:12 AM, Jeffry Copps
wrote:
> Hi NET-SNMP,
addr_in2+150
> netsnmp_sockaddr_in2+134
> netsnmp_tcp_create_tstring+24
> netsnmp_tdomain_transport_full+508
> netsnmp_transport_open_client+18
> subagent_open_master_session+125
> agentx_reopen_session+82
> run_alarms+ce
> SnmpTrapdMain+c28
>
>
> Thanks,
> Jeffry copps
&g
This works on UNIX. It may be a difference in how getopt is implemented in
the Windows libc? I recommend filing a bug report at
http://www.net-snmp.org/bugs/ .
Bill
On Wed, Aug 2, 2017 at 9:38 AM, cryptoservices--- via Net-snmp-coders <
net-snmp-coders@lists.sourceforge.net> wrote:
> Dear r
On Fri, Oct 27, 2017 at 4:34 AM, Josef Ridky wrote:
> These changes has been delivered to upstream, unfortunately, nobody has
> response on them yet and I do not have commit access to official net-snmp
> repository.
>
When you say "nobody has response on them yet", are you talking about
https://
snmplib/netsnmp-openssl.c is not built unless HAVE_LIBSSL is defined, which
is only defined if the TLS transports are used. After the removal of the
compat functions from apps/snmpusm.c, if you build with only USM
transports, there is nothing to provide the DH_get0_pqg compatibility
function.
B
compiles that pulls the compat
functions that snmpusm needs into the new #if, dunno if you have a better
idea. I haven't tested it with TLS transports.
Bill
On Tue, Dec 19, 2017 at 8:53 PM, Bart Van Assche wrote:
> On 12/19/17 10:36, Bill Fenner wrote:
> > snmplib/netsnmp-ope
On Wed, Dec 20, 2017 at 10:24 AM, Bart Van Assche
wrote:
> On 12/20/17 05:42, Bill Fenner wrote:
>
>> I've attached a patch that at least compiles that pulls the compat
>> functions that snmpusm needs into the new #if, dunno if you have a better
>> idea. I haven&#x
On Wed, Dec 20, 2017 at 10:51 AM, Robert Story wrote:
> On Wed 2017-12-20 08:42:19-0500 Bill wrote:
> > I've attached a patch that at least compiles that pulls the compat
> > functions that snmpusm needs into the new #if, dunno if you have a
> > better idea. I haven't tested it with TLS transpor
On Wed, Dec 20, 2017 at 12:01 PM, Robert Story wrote:
> On Wed 2017-12-20 10:51:07-0500 Robert wrote:
> > On Wed 2017-12-20 08:42:19-0500 Bill wrote:
> > > I've attached a patch that at least compiles that pulls the compat
> > > functions that snmpusm needs into the new #if, dunno if you have a
>
On Wed, Dec 20, 2017 at 12:22 PM, Robert Story wrote:
> On Wed 2017-12-20 12:13:48-0500 Bill wrote:
> > > The attached patch against master builds with and without TLS
> > > transports on CentOS 6 (openssl 1.0) and Fedora 27 (openssl 1.1).
> >
> > Can you attach "git show" instead of "git log", o
Jose,
Your debugging determined that you have a loop in your network, which
delivers one copy to your trap receiver every time around the loop. The
number of traps that you receive maps directly to the TTL of the packet
that net-snmp sends out. This is not a problem with how net-snmp sends
packe
On Tue, Jan 16, 2018 at 8:57 AM, Fulko Hew wrote:
>
>
> On Mon, Jan 15, 2018 at 11:56 PM, Bart Van Assche
> wrote:
>
>> On 01/15/18 20:22, Fulko Hew wrote:
>>
>>> b) I've always considered David Perkins' book 'Understanding SNMP MIBs'
>>> as a good reference on how to interpret the specs.
>>>
>>
Simon,
Can you try with global addresses? I wouldn't be horribly surprised if
scope zones were not supported properly. (Global v6 addresses have worked
for me in net-snmp for years.)
Bill
On Mon, Jan 15, 2018 at 2:37 PM, Simon Chamlian
wrote:
> Hi,
>
> Just recompiled the agent by enabling
On Mon, Jan 22, 2018 at 10:02 AM, Ján Gnip wrote:
> ##
> # AT - Address Translation
> ##
>
> atTable OBJECT-TYPE 1.3.6.1.2.1.3.1 - not implemented
>
atTable was marked as deprecated in 1990.
> #
Can you paste the end of your configuration run, where it summarizes the
results? The “rocommunity6” configuration directive will be available if
that configuration summary includes “UDPIPv6” in the “Network transport
support:” list - e.g.,
-
etsnmpmibs.so.30.0.3
> libnetsnmpagent.so.30.0.3
> libnetsnmptrapd.so.30.0.3
>
> S.
>
>
> On Wed, Jan 24, 2018 at 11:57 AM, Bill Fenner wrote:
>
>> Can you paste the end of your configuration run, where it summarizes the
>> results? The “rocommunity6” con
On Mon, Jan 29, 2018 at 8:19 AM, Magnus Fromreide
wrote:
> On Mon, Jan 29, 2018 at 10:53:31AM -0300, Pedro Barbosa wrote:
> > Hi,
> >
> > Does anyone know which CVE regards to this issue?
> >
> > https://github.com/rapid7/metasploit-framework/pull/9396
> >
> > /This exploit module exploits the SN
The new code in net-snmp 5.8 that tries to account for v1 or v2 trap
sessions logs an error from an agentx subagent, since the agentx code
registers the session as being AGENTX_VERSION_1. This constant is only
defined in the agentx code, so agent_trap.c doesn't know what it is.
I suspect that thi
I have an unofficial Travis build setup; in it the only tests that fail are
because the Travis environment seems to not have even localhost IPv6
available: https://travis-ci.org/fenner/net-snmp
The configure script test can fail if you've regenerated it using autoconf
but not using 2.68.
By "test
I don't think the patch is the issue. There are two questions to be
addressed first:
1. For the embedded environment, is it acceptable to use an extra several
bytes for this (or is there a way to rearrange the struct so that padding
reduces the extra cost)?
2. Is it reasonable to have more than 2
On Thu, Mar 22, 2018 at 8:33 AM, Eric S. Raymond wrote:
> Bill Fenner :
> > By "test 31" do you mean "snmpv1 traps are sent by snmpd API"?
>
> Now I'm getting a different result, which is a little disturbing in itself:
>
> com2sec directive
>
On Thu, Mar 22, 2018 at 9:16 AM, Eric S. Raymond wrote:
> On the other hand, I question whether the extra overhead is a real
> issue in 2018.
I have the same question, but know that I have no useful opinion here - my
"embedded system" ships with 4 gigs minimum, but the project has more use
case
On Wed, Mar 21, 2018 at 5:50 PM, Keith Mendoza wrote:
Hi,
> I'm one of the volunteer developers with ICEI (please see email with
> subject "ICEI asks what help you need" for details). I was attempting
> to compile net-snmp code with -std=c99 compiler option, and the
> compiler failed with "error:
On Thu, Mar 22, 2018 at 9:37 AM, Bart Van Assche wrote:
> On 03/21/18 19:47, Eric S. Raymond wrote:
>
>> - 3) make
>>>
>> + 3) Run make. If the build fails with a complaint that it can't resolve
>> + -lperl, install libperl-dev and try again.
>>
> This should be elaborated further: anoth
On Thu, Mar 22, 2018 at 3:26 PM, Eric S. Raymond wrote:
> Or possibly it might have but your build system messed me over. I don't
> trust
> autoconf as far as I can throw it.
>
I understand someone's done a conversion to cmake. Does that make you
happier or vomityer?
Bill
---
m--before
> proceeding any further. Where are dev-related documents usually
> stored? I'd like to contribute my notes once when I'm done.
>
> Thanks,
> Keith
> Thanks,
> Keith
>
>
> On Thu, Mar 22, 2018 at 3:14 PM, Bill Fenner wrote:
> > The oid rep
On Thu, Mar 29, 2018 at 5:57 AM, Pushpa Thimmaiah <
pushpa.thimma...@gmail.com> wrote:
> Query 1. Which interface does 'snmptrap'/snmpd use to send traps out?
>
It will use the kernel's routing table.
> Query 2. Suppose, eth1 firewall blocks 'snmp' packets then
> Does 'snmpd/snmpt
On Wed, Mar 28, 2018 at 1:09 PM, Ian Bruene wrote:
>
> Trawling through the bugtracker I found a number of bugs - some reaching
> back to 2002 - which have either been fixed, or from the explanations in
> the comments need to be listed as WONTFIX. This is obviously not a complete
> list, but it i
Simon,
The USM AES192 and AES256 support is based upon an Internet Draft, which
never became a standard - therefore, you have to pass
"--enable-blumenthal-aes" to ./configure. (You don't have to enable TSM or
the TLS transports; that's a whole different kettle of fish.)
Bill
On Fri, Apr 6, 20
ead of "AES192" (this uses the "Cisco"
algorithm);
2. Use a stronger auth mechanism, which creates a longer auth key, which
doesn't have to be lengthened for the strong privacy algorithm, avoiding
the question of how to lengthen it. I think SHA suffices, but of course
SHA2
Stepping back one step from the fact that they enable/disable different
bits of code: is there a semantic difference intended here, or was this
some feature collision and both were retained? Is there a WRITE that is not
a SET?
NETSNMP_NO_WRITE_SUPPORT came in with the features/minimalist stuff;
NE
I'm sorry that I wasn't available for this meeting. I think one important
pain point is the overhead of doing releases - 5.7.3 was years ago and
there are very useful fixes in the 5.7 branch; why can't we just say "now's
a good time for 5.7.4 and if we don't get it right then we can release
5.7.5
Hi Bart,
Also check out my travis config - configuring with different sets of
configure args - minimalist is important to me, so it's nice to have
regression testing against, and we had a couple of interesting bugs
reported agaist --disable-set-support and --enable-read-only, so I added
them. Obv
On Wed, Apr 25, 2018 at 5:14 PM, Keith Mendoza wrote:
> Just want to see where everyone is regarding 5.8 release. Other than
> what's listed in the 5.8pre2 announcement are there any other features that
> will go into 5.8?
>
> Other that the bugs I filed last week from running the test suite agai
I do not think the DISMAN PING module builds anywhere but Linux. I am not
a fan of the existing implementation since it is synchronous.
(I have a from-scratch asynchronous rewrite sitting around languishing that
I haven't tested anywhere but Linux; raw sockets are pretty notoriously
incompatible
On Thu, Apr 26, 2018 at 10:02 AM, Bart Van Assche
wrote:
> On 04/26/18 04:57, Bill Fenner wrote:
>
>> A new feature went into 5.8 that conflicts a little with using an agentx
>> subagent. I mentioned this here:
>> https://sourceforge.net/p/net-snmp/mailman/message/362704
On Thu, Apr 26, 2018 at 10:00 PM, Bill Fenner wrote:
> On Thu, Apr 26, 2018 at 10:02 AM, Bart Van Assche
> wrote:
>
>> On 04/26/18 04:57, Bill Fenner wrote:
>>
>>> A new feature went into 5.8 that conflicts a little with using an agentx
>>> suba
On Fri, Apr 27, 2018 at 6:36 PM, Robert Story wrote:
> On Thu, 26 Apr 2018 22:07:27 -0400 Bill wrote:
> BF> >>> (The context is that the library now tries to suppress
> BF> >>> converting traps from v1 to v2 or vice versa if there is no
> BF> >>> trap sink of the right type, but, it does not know
I’ve got a local patch that’s been hanging around for a long time to set
session.localaddr from an -@ command line argument. The use case is a bit
esoteric, but has been mentioned a couple of times on the lists: the
existing clientaddr configuration has only one value, so we can’t set
values for IP
On Fri, Apr 27, 2018 at 12:15 PM, Keith Mendoza wrote:
> Bill,
>
> On Thu, Apr 26, 2018, at 6:54 PM, Bill Fenner wrote:
> > I do not think the DISMAN PING module builds anywhere but Linux. I am
> not
> > a fan of the existing implementation since it is synchronous.
>
I just filed https://sourceforge.net/p/net-snmp/bugs/2864/ : "clientaddr"
doesn't work to set the source address for traps any more. (And given that
the code path is the same, I suspect it doesn't work for client requests
either). This is a regression against 5.7.3; that code has been
restructure
On Thu, May 3, 2018 at 1:07 PM, Robert Story wrote:
> On Wed, 2 May 2018 11:49:46 -0400 Bill wrote:
> BF> Is it too late to add this? This occurs to me just because it’s
> BF> an easier way to test the transports’ support of clientaddr, by
> BF> being able to set clientaddr dynamically via the co
On Thu, May 3, 2018 at 12:53 PM, Robert Story wrote:
> On Wed, 2 May 2018 11:08:44 -0400 Bill wrote:
> BF> I just filed https://sourceforge.net/p/net-snmp/bugs/2864/ :
> BF> "clientaddr" doesn't work to set the source address for traps
> BF> any more. (And given that the code path is the same, I
On Fri, May 4, 2018 at 12:08 AM, Robert Story wrote:
> On Thu, 3 May 2018 14:32:40 -0400 Bill wrote:
> BF> > On Wed, 2 May 2018 11:08:44 -0400 Bill wrote:
> BF> > BF> I just filed
> BF> > BF> https://sourceforge.net/p/net-snmp/bugs/2864/ :
> BF> > BF> "clientaddr" doesn't work to set the source a
On Fri, May 4, 2018 at 12:06 AM, Robert Story wrote:
> On Thu, 3 May 2018 14:29:09 -0400 Bill wrote:
> BF> On Thu, May 3, 2018 at 1:07 PM, Robert Story
> BF> wrote:
> BF> Depends on at what level you are looking at the functionality.
> BF> -@ would set session.localaddr, which is a little differ
On Fri, May 4, 2018 at 11:25 AM, Bill Fenner wrote:
> Should I commit the broken tests so anyone else who wants to try to fix
> the trap*sink code has a starting point?
>
> Here are the tests:
https://github.com/fenner/net-snmp/compare/master...fenner:trapsourcetests?expand=1
T18
On Fri, May 4, 2018 at 5:20 PM, Robert Story wrote:
> On Fri, 4 May 2018 11:25:35 -0400 Bill wrote:
> BF> My proposed fix works for my trapsess case, so I guess that's
> BF> something. Should I commit the broken tests so anyone else who
> BF> wants to try to fix the trap*sink code has a starting
On Fri, May 4, 2018 at 5:10 PM, Robert Story wrote:
> On Fri, 4 May 2018 11:40:21 -0400 Bill wrote:
> BF> I apologize for mis-speaking. I meant, session.localname,
> BF> which is used in _sess_open() as follows:
> BF>
> BF> https://sourceforge.net/p/net-snmp/code/ci/master/tree/
> snmplib/snmp_a
On Sun, May 6, 2018 at 4:33 PM, Robert Story wrote:
> BF> The tests:
> BF> https://github.com/fenner/net-snmp/commit/
> 41be11b4e3ab93cda376bf044de2f77534b56518
> BF> (T180 and T181 fail. T181 is testing the new functionality in
> BF> 5.8, so, no biggie. T180 tests functionality that worked in
>
On Sun, May 6, 2018 at 7:33 PM, Bill Fenner wrote:
> On Sun, May 6, 2018 at 4:33 PM, Robert Story wrote:
>
>> BF> The tests:
>> BF> https://github.com/fenner/net-snmp/commit/41be11b4e3ab93cda3
>> 76bf044de2f77534b56518
>> BF> (T180 and T181 fail. T181 is
I've committed the following fix to the 5.7-patches branch:
https://sourceforge.net/p/net-snmp/code/ci/3defab66a7aee60ba582a8254412abd2e630c321/
It turns out that when you specify a clientaddr, the steps the function
takes are:
- zero out addr_pair
- store the remote address in addr_pair
- looku
On Tue, May 15, 2018 at 9:58 AM, Bart Van Assche wrote:
> Even if I do not enable any additional MIBs building with
> --enable-read-only fails on the master branch:
>
> snmpping.c: In function ‘cleanup_ctlTable’:
> snmpping.c:276:27: error: ‘SNMP_MSG_SET’ undeclared (first use in this
> function)
Since snmpping requires set support, it should be conditional. My proposed
patch is
https://github.com/fenner/net-snmp/commit/b6e69f9ccbadcb7d4a49a4a6020ef932e84bbc5c
The build with --enable-read-only now succeeds, as can be seen by the fact
that we got to tests:
https://travis-ci.org/fenner/ne
On Tue, May 15, 2018 at 11:33 AM, Wes Hardaker via Net-snmp-coders <
net-snmp-coders@lists.sourceforge.net> wrote:
> 3) --enable-minimalist is an interesting one that is also designed for
>code reduction in that one section of code can declare the need for a
>function, and if and only if t
When I was looking at the master travis results, I saw that
--enable-minimalist was broken since the target MIB started using
netsnmp_compare_mem() without requiring the feature. This change unbreaks
it:
https://github.com/fenner/net-snmp/commit/be725381766a60b16ef32a14378cda0fdbaecd23
Bill
--
I got myself confused again with the rewritten transport code. "Applying
the patch to 5.8" is nonsense, so, nevermind this request.
Bill
--
Check out the vibrant tech community on one of the world's most
engaging tech si
On Tue, May 15, 2018 at 9:40 PM, Robert Story wrote:
> On Wed, 16 May 2018 03:13:34 +0200 Magnus wrote:
> MF> > Yes, but it doesn't break for a default configure, which is
> MF> > the criteria for a show stopper in the RC phase. Of course +3
> MF> > votes for anything is an automatic show stopper
On Thu, May 17, 2018 at 9:56 AM, Niels Baggesen via Net-snmp-coders <
net-snmp-coders@lists.sourceforge.net> wrote:
> Den 17-05-2018 kl. 15:54 skrev Robert Story:
>
>> On Wed, 16 May 2018 07:23:32 -0700 Bart wrote:
>> BVA> This patch makes it possible to enable Travis and Appveyor
>> BVA> continuo
On Sun, May 20, 2018 at 12:18 AM, Robert Story wrote:
> On Sat, 19 May 2018 14:07:56 -0700 Bart wrote:
> BVA> strlcpy() implementations typically scan for the end of the
> BVA> source argument passed to strlcpy(). Hence avoid passing an
> BVA> unterminated string to strlcpy().
>
> I'm going to sa
On Sun, May 20, 2018 at 2:25 PM, Robert Story wrote:
> On Sun, 20 May 2018 13:06:43 -0400 Bill wrote:
> BF> I do not think that now is the time to try to deal with any of
> BF> the fundamentals, but just not regress from previous released
> BF> behavior, and deal with the underlying issue in 5.8.
On Mon, May 21, 2018 at 11:18 AM, Wes Hardaker <
harda...@users.sourceforge.net> wrote:
> Bill Fenner writes:
>
> > So, +1 on committing Bart's patch, because it accomplishes the goal of
> > fixing the regression, with the caveat that I really think that this
> &g
On Wed, Mar 21, 2018 at 10:58 AM Bill Fenner wrote:
> The new code in net-snmp 5.8 that tries to account for v1 or v2 trap
> sessions logs an error from an agentx subagent, since the agentx code
> registers the session as being AGENTX_VERSION_1. This constant is only
> defined i
Oops, it turns out that the reason that it works is because the agentx
session is in the session list that is always iterated over, so, this fix
is wrong: we should just silently ignore agentx sessions in this code.
--
Chec
Hi Bart,
I see that when it's a souce, you use "const char *", and when it's a
destination, you use "unsigned char *". I understand the reason for the
constness difference, but is there a reason for the signedness difference?
Bill
On Thu, Jun 21, 2018 at 10:23 PM Bart Van Assche wrote:
> A
On Thu, Jul 12, 2018 at 10:33 AM Bart Van Assche wrote:
> On 07/12/18 04:59, Bill Fenner wrote:
> > I see that when it's a souce, you use "const char *", and when it's a
> > destination, you use "unsigned char *". I understand the reason for the
&g
I agree with the concept of handling UTF-8, but I do not like this
implementation. We discussed this a couple of months ago,
https://sourceforge.net/p/net-snmp/mailman/message/36322758/
Bill
On Mon, Jul 16, 2018 at 5:16 AM Josef Ridky wrote:
> Net-SNMP isn't able to handle double byte charac
I wrote some tests for traps and clientaddr, since there were a bunch of
changes between 5.7 and 5.8 in this area. I did a couple of unusual things:
1. I factored a ton of the test code out into a support file,
S180trapaddrinfra, since the bulk of the tests were the same.
2. I created a little he
On Sun, Sep 16, 2018 at 12:11 AM Bart Van Assche wrote:
> On 09/13/18 10:55, Bill Fenner wrote:
> > I wrote some tests for traps and clientaddr, since there were a bunch of
> > changes between 5.7 and 5.8 in this area. I did a couple of unusual
> things:
> >
> > 1
usr
>> 0.01 csys = 0.04 CPU)
>> Result: PASS
>>
>> Don't use bash specific "==", use single "=" instead to avoid this
>> printout.
>>
>> Use "$localhost" in T180 and T181 instead of fixed IP's
>>
>> (Patc
On Mon, Oct 8, 2018 at 9:46 PM Bart Van Assche wrote:
> On 10/8/18 3:00 AM, ClusterFuzz-External via monorail wrote:
>
> Status: New Owner: CC: ma...@lysator.liu.se, bvanass...@acm.org,
> harda...@users.sourceforge.net, fen...@gmail.com, rst...@freesnmp.com
> Labels: Proj-net-snmp Type: Buil
On Thu, Oct 4, 2018 at 1:19 AM Pushpa Thimmaiah
wrote:
> Hi All,
>
> I have understood that option 'clientAddr' to provide source-IP address
> for outgoing traps. There is no option to provide source-interface to send
> traps.
> Kindly let me know reason for this restriction.
>
The source IP a
> On Nov 7, 2018, at 1:27 AM, Bart Van Assche wrote:
>
>> On 11/6/18 12:31 PM, Bill Fenner wrote:
>> Playing with this in V5-8-patches, I see it broke my fix for using
>> clientaddr to specify the source address for traps:
>> netsnmp_sockaddr_in: addr 0xf
Perhaps getbulk no longer dumps core, but I can not get it to return
anything but GENERR any more, and, it seems to leak memory.
Any "large enough" request seems to fail in this way, e.g., snmpbulkget -v
3 ... -Cn 5 -Cr 50 sysUpTime sysUpTime sysUpTime sysUpTime sysUpTime .1
This is particularly
On Tue, May 14, 2019 at 1:38 PM Bart Van Assche wrote:
> On 5/14/19 4:01 PM, Bill Fenner wrote:
> > Perhaps getbulk no longer dumps core, but I can not get it to return
> > anything but GENERR any more, and, it seems to leak memory.
> >
> > Any "large enough&qu
101 - 200 of 260 matches
Mail list logo
