Re: SIGHUP for changing snmpv3 context

Hi Vivek, There are some types of configuration that can only be applied with a restart, because the option to change them has not yet been implemented. There is nothing fundamental that prevents this from being implemented, but it is not a simple fix, which is why it hasn't been done yet.

Re: Convert cleartext password to localised key

Hi Pushpa, You can try https://gist.github.com/fenner/696cbb2d0e4429a8dff32af70b2bb8b1 for some sample python code. Bill On Fri, Oct 20, 2023 at 4:45 AM Pushpa Thimmaiah wrote: > Hi, > > I would like to convert cleartext password to localized key for trapsess > line. I understood that one

Re: helpers/scalar's realloc() of rootoid vs. netsnmp_subtree_split copying just the known size

I happened to get to talk to Wes about this, and his answer was basically that these things were not meant to be mixed in this way. I have since changed my code to use netsnmp_register_scalar when I want to shadow a scalar, and that works fine. Bill On Wed, Nov 9, 2022 at 8:36 AM Bill Fenner

helpers/scalar's realloc() of rootoid vs. netsnmp_subtree_split copying just the known size

Hi, I have a MIB module that uses netsnmp_register_scalar() which realloc's the given root oid to have one more space in it, so that the netsnmp_scalar_helper_handler can use that space to store the ".0" instance during the handling of a request. This all works fine, until we register an

Re: oldEngineID format in snmpd.conf

On Wed, Jul 20, 2022 at 2:46 AM Feroz wrote: > What I configured in snmpd.conf file > > *engineID 8000b85c03d0672649a01e* > This configured net-snmp to use the string " 8000b85c03d0672649a01e" to generate an engineID. If you want to configure the engine-id with a hex string, please use the

Re: snmpv3 poll

Hi Paban, This means that your manager and your agent are not using the same algorithm for short-key extension. There are two different algorithms that are in use to extend the output of a short hash function (like SHA) for use with longer encryption keys (like AES192). When you run into this

Re: multiple subagent with same set of oid.

If there's interest, I have a patch that allows communities of the form "community@context" to be treated by the snmp agent as separate community and context values, eliminating the need to define each combination as a valid community, and use com2sec to do the mapping. I hadn't upstreamed it

Re: When exactly the response is received from node 2 ?

e. > You could try -DALL. That doesn't quite track all function calls, but at least it tracks all places where there is any debugging specified. Bill > On Mon, 6 Sept 2021 at 19:26, Bill Fenner wrote: > >> On Sun, Sep 5, 2021 at 9:59 AM Nishant Nayan >> wrote: >> >>

Re: Varbind orfer in SNMP TRAP's

On Thu, Oct 28, 2021 at 6:01 PM Fulko Hew wrote: > > > On Thu, Oct 28, 2021 at 5:23 PM Craig Small wrote: > >> On Fri, 29 Oct 2021 at 05:14, Feroz wrote: >> >>> hi, >>> Is it necessary to maintain any specific order in SNMP TRAP for varbinds? >>> >> For the first two, yes. >> > > I always

Re: How to support SNMPv2 mib traps per VRF.

On Wed, Oct 20, 2021 at 5:00 AM chandrasekharreddy chinnapareddygari < chandrasekhar...@hotmail.com> wrote: > Spell check has done in line. > -- > *From:* chandrasekharreddy chinnapareddygari > > *Sent:* Wednesday, 20 October, 2021, 14:15 > *To:*

Re: When exactly the response is received from node 2 ?

doc/html/rfc3416#section-4.1 and specifics about how they are set when handling a GetRequest in section 4.2.1 https://datatracker.ietf.org/doc/html/rfc3416#section-4.2.1 Bill > > > Thanks > Nishant > > On Mon, 6 Sept 2021 at 19:34, Bill Fenner wrote: > >> By th

Re: I have some qhestions about work you library.

Hi Ivan, Does the example at http://www.net-snmp.org/wiki/index.php/TUT:Simple_Application help? Specifically, in that example, "session.peername" is the remote DNS name, but you can place a (string-formatted) IP address in that field as well. Bill On Wed, Sep 15, 2021 at 5:27 PM Иван Иванов

Re: Agent+Sub-Agent

On Fri, Sep 3, 2021 at 3:43 AM Feroz wrote: > My question is, is there a way to block an agent from responding to > queries ( by timeout), till time the sub-agent connects to the agent. > No, the master agent always lives under the impression that it knows everything. You may be able to fake

Re: When exactly the response is received from node 2 ?

By the way, I wanted to mention - I noticed your example was using SNMPv1. SNMPv1 has been obsolete since 2002 (when the RFC was moved to historic status). You should ideally be using SNMPv3, with its authorization and privacy improvements, and if not, at least use SNMPv2 which is not obsolete.

Re: When exactly the response is received from node 2 ?

On Sun, Sep 5, 2021 at 9:59 AM Nishant Nayan wrote: > My aim is to know how various parameters like errorstat and errindex etc. > are set from response. > > For an example command : > snmpget -v1 -c cmty_remotehost1 localhost SNMPv2-MIB::sysName.1 > SNMPv2-MIB::sysDescr.0

Re: cannot get mac address value starting by "00" with an snmp module

It's hard to say without seeing your code, but a common source of problems like this is using functions that are meant for nul-terminated strings (e.g., strncpy() ) instead of those meant for moving bytes around (e.g., memcpy() ). Bill On Fri, Jan 15, 2021 at 10:06 AM dga via Net-snmp-coders

Re: Suggestions for testing changes regarding names of anonymous nodes

On Mon, Nov 2, 2020 at 9:37 AM Bill Fenner wrote: > I imagined writing a test that exercises all of the output options (-Of, > -On, -Os, -OS, -Ou) for both netSnmpExampleAnonymousIntermediateNode > and netSnmpExamples.42.1. Does anyone have any other suggestions of what > t

Suggestions for testing changes regarding names of anonymous nodes

Hi, I found that net-snmp will output a nonsense name if there's an anonymous node in the path. For example, if you add +-- +-- An object defined with an anonymous intermeidate node +-- for testing object output in "-On" mode +-- + +netSnmpExampleAnonymousIntermediateNode OBJECT IDENTIFIER +

Re: response source IP for SNMP walk

On Wed, May 13, 2020 at 9:47 AM chandrasekharreddy chinnapareddygari < chandrasekhar...@hotmail.com> wrote: > Hi team, > > > I want to change source ip for snmpwalk like changing source IP for traps. > I know , we can use clientaddr for changing source IP for traps. > > > Is there any token is

Re: identical snmpEngineID across multiple device

On Wed, Mar 18, 2020 at 6:30 AM Pushpa Thimmaiah wrote: > If two device has same snmpEngineID then will it impact on device security? > Two things off the top of my head: 1. The localized keys will be the same, meaning that if a localized key is stolen it can be used for all devices with the

Re: [netsnmp-coders] missing information in logmatch trap

On Sat, Sep 28, 2019 at 10:14 AM Thommandra Gowtham wrote: > Thank you Bill for your response. > > When you said that I have configured two separate features, can you > explain? How else can we get a logmatch trap by just one directive? > You currently can not. That is how I imagine the feature

Re: [netsnmp-coders] missing information in logmatch trap

Hi Gowtham, Please file your request at https://github.com/net-snmp/net-snmp/issues . The reason the info is not present in the trap is because you have configured two separate features: 1. count log file matches in the logMatch table - note that there is no place in this table for a list of

Re: snmpv3 context partial output

On Mon, Sep 23, 2019 at 11:48 AM T S, SURYA wrote: > So is there any way to merge null subtree with context subtree in netsnmp, > so that I can get access to entire oid with context specifc oids on > snmpwalk with context. > I looked into this a couple of months ago. In my opinion, it would

Re: snmptrapd

On Wed, Sep 18, 2019 at 7:13 AM jayshankar nair wrote: > Hi, > > I am using variant of snmptrapd. > In what way is it a variant? > The snmptrapd is processing trap packet at 4min delay. Why so much delay??. > Does this delay happen with unmodified snmptrapd? Bill

Re: MAC Address As Index

On Tue, Sep 17, 2019 at 4:27 AM Krishna Chaitanya wrote: > On Tue, Sep 17, 2019 at 5:18 AM Bill Fenner wrote: > > > > You can do this if you use snmp_varlist_add_variable() to create the > index info (you can't use netsnmp_table_helper_add_indexes). The code > wo

Re: MAC Address As Index

at 2:12 PM Krishna Chaitanya > > wrote: > > > > > > On Mon, Aug 26, 2019 at 9:22 PM Bill Fenner wrote: > > > > > > > > On Tue, Aug 20, 2019 at 8:45 AM Krishna Chaitanya < > chaitanya.m...@gmail.com> wrote: > > > >> > > > >

Re: [net-snmp:code] treewide: Terminate netsnmp_feature_*() uses with a semicolon

On Tue, Aug 27, 2019 at 11:11 PM Bart Van Assche wrote: > On 8/26/19 3:12 PM, Bill Fenner wrote: > > It turns out a typo in the .travis.yml did not export the environment > > variables to the build script. Looks like MODE=minimalist and > > MODE=read-only are both br

Re: Regarding snmpv3 inform packet

On Fri, Aug 23, 2019 at 12:19 PM Pushpa Thimmaiah < pushpa.thimma...@gmail.com> wrote: > Hi All, > > I would like to understand messages exchanged between manager and agent > during snmpv3-inform. > Following is my understanding > Msg1. Agent to manager : Request for engineID > Msg2. Manager to

Re: commit e56699f5e2ef ("Add the ability to set the source address with "-s" for trapsess")

On Mon, Aug 26, 2019 at 9:51 PM Bart Van Assche wrote: > On 8/26/19 9:08 AM, Bill Fenner wrote: > > Here's my proposed documentation: > > [ ... ] > > Hi Bill, > > Does this mean that you have a patch ready for man/snmpd.conf.5.def? If > so, how about posting that

Re: [net-snmp:code] treewide: Terminate netsnmp_feature_*() uses with a semicolon

It turns out a typo in the .travis.yml did not export the environment variables to the build script. Looks like MODE=minimalist and MODE=read-only are both broken as-is: https://travis-ci.org/fenner/net-snmp/builds/577056671 Bill ___ Net-snmp-coders

Re: [net-snmp:code] treewide: Terminate netsnmp_feature_*() uses with a semicolon

On Mon, Aug 26, 2019 at 11:48 AM Bill Fenner wrote: > On Tue, Aug 13, 2019 at 11:17 PM net-snmp Git repository < > nore...@code.net-snmp.p.re.sourceforge.net> wrote: > >> Branch: V5-8-patches >> >> treewide: Terminate netsnmp_feature_*() uses with a semicolon &g

Re: [net-snmp:code] treewide: Terminate netsnmp_feature_*() uses with a semicolon

On Mon, Aug 26, 2019 at 4:51 PM Bart Van Assche wrote: > On 8/26/19 12:59 PM, Bill Fenner wrote: > > Just as a personal preference, I like to use "awk" instead of grep|... - > > "awk '/NSF_WW/ {print $1}' $tmpf" gives the same result and doesn't car

Re: [net-snmp:code] treewide: Terminate netsnmp_feature_*() uses with a semicolon

On Mon, Aug 26, 2019 at 12:34 PM Bill Fenner wrote: > On Mon, Aug 26, 2019 at 11:48 AM Bill Fenner > wrote: > >> On Tue, Aug 13, 2019 at 11:17 PM net-snmp Git repository < >> nore...@code.net-snmp.p.re.sourceforge.net> wrote: >> >>> Branch

Re: [net-snmp:code] treewide: Terminate netsnmp_feature_*() uses with a semicolon

On Mon, Aug 26, 2019 at 11:48 AM Bill Fenner wrote: > On Tue, Aug 13, 2019 at 11:17 PM net-snmp Git repository < > nore...@code.net-snmp.p.re.sourceforge.net> wrote: > >> Branch: V5-8-patches >> >> treewide: Terminate netsnmp_feature_*() uses with a semicolon &g

Re: commit e56699f5e2ef ("Add the ability to set the source address with "-s" for trapsess")

a few paragraphs above, but I think it's worth doing since if you search for "src" you may gloss over the above reference. What do you think? Thanks, Bill On Mon, Aug 26, 2019 at 11:57 AM Bill Fenner wrote: > Hi Bart, > > I'm afraid I deferred t

Re: commit e56699f5e2ef ("Add the ability to set the source address with "-s" for trapsess")

Hi Bart, I'm afraid I deferred to the documentation for df26f8f2d51409827a3ce131c1b9de67d01ee6e5 which added "-s" for trapsink. (i.e., nowhere.) I acknowledge that was lazy, and I will write documentation for both commits in snmpd.conf.5.def. Bill On Fri, Jul 26, 2019 at 9:28 PM Bart Van

Re: MAC Address As Index

On Tue, Aug 20, 2019 at 8:45 AM Krishna Chaitanya wrote: > Hi, > > When using MAC Address as an index ( I am using MacAddress type from > SNMPv2-TC.) the output is incorrect because the length of the string > is prefixed as mac address is defined as OCTET STR there is an extra > byte and the

Re: [net-snmp:code] treewide: Terminate netsnmp_feature_*() uses with a semicolon

On Tue, Aug 13, 2019 at 11:17 PM net-snmp Git repository < nore...@code.net-snmp.p.re.sourceforge.net> wrote: > Branch: V5-8-patches > > treewide: Terminate netsnmp_feature_*() uses with a semicolon > > This patch has been generated by the following shell command: > > git grep -l netsnmp_feature_

Re: [net-snmp:code] 2 new commits to Code

B: Account reclaimable > space")? > I'm fine with 4e3ace87b566 ("NET-SNMP-SYSTEM-MIB: Account reclaimable space"). It's change a88d81f1144e ("NET-SNMP-SYSTEM-MIB, Linux: Update calculation of free space") that I'm concerned about, that changes the long-standing values r

Re: [net-snmp:code] 2 new commits to Code

There's a long history of telling people "You're polling a Linux system, you have to know that you subtract buffers and cached from physical before you report free memory" in the HOST-RESOURCES-MIB. I'm not against simplifying, but - if people have data collection set up for "the old way", where

Re: [net-snmp:patches] #1388 patch for bug 2923: snmpv3 bulkget errors result in double free core dump

The memory leak is gone in the current V5-8-patches. I have not dug into trying to bisect which change fixed it. Bill On Tue, May 14, 2019 at 7:01 AM Bill Fenner wrote: > Perhaps getbulk no longer dumps core, but I can not get it to return > anything but GENERR any more, and, it

Re: [net-snmp:patches] #1388 patch for bug 2923: snmpv3 bulkget errors result in double free core dump

To try to make it easier I've created a fake pull request, allowing comments on the diff and discussion, and a clear set of diffs between this stuff and 5.8-patches: https://github.com/fenner/net-snmp/pull/3 Bill On Mon, May 20, 2019 at 11:27 AM Bill Fenner wrote: > Some of the b

Re: [net-snmp:patches] #1388 patch for bug 2923: snmpv3 bulkget errors result in double free core dump

helps the "state that was freed" part. With 3 different solutions for the problem it's hard to figure out exactly how to proceed.) Bill On Mon, May 20, 2019 at 9:28 AM Bill Fenner wrote: > On Tue, May 14, 2019 at 1:38 PM Bart Van Assche > wrote: > >> On 5/14/19 4

Re: [net-snmp:patches] #1388 patch for bug 2923: snmpv3 bulkget errors result in double free core dump

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

Re: [net-snmp:patches] #1388 patch for bug 2923: snmpv3 bulkget errors result in double free core dump

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

Re: [net-snmp:code] 4 new commits to Code

On Tue, May 7, 2019 at 7:41 PM Bart Van Assche wrote: > On 5/7/19 9:42 AM, Bill Fenner wrote: > > I was hoping you might have an idea of a more graceful solution that > > allows keeping const'ness. If not, I can check in my change. > > Hi Bill, > > Please have a

Re: [net-snmp:code] 4 new commits to Code

On Mon, Apr 29, 2019 at 7:10 PM Bart Van Assche wrote: > On Mon, 2019-04-29 at 17:19 -0400, Bill Fenner wrote: > > On Sun, Apr 28, 2019 at 7:52 PM net-snmp Git repository < > nore...@code.net-snmp.p.re.sourceforge.net> wrote: > > Branch: V5-8-patches > > c

Re: [net-snmp:code] 4 new commits to Code

On Sun, Apr 28, 2019 at 7:52 PM net-snmp Git repository < nore...@code.net-snmp.p.re.sourceforge.net> wrote: > Branch: V5-8-patches > > configure: Determine endianness at compile time instead of at configure > time > > The new test supports cross-compilation. In other words, --with-endianness >

Re: [PATCH 0/6] Add support for interface binding

On Fri, Jan 25, 2019 at 11:37 AM Magnus Fromreide wrote: > On Sun, Oct 28, 2018 at 01:54:22PM -0700, Bart Van Assche wrote: > > Hello, > > > > As you may have noticed multiple people asked to add SO_BINDTODEVICE > support > > to Net-SNMP. This patch series adds such support by allowing to

Re: [PATCH 0/6] Add support for interface binding

p" 28 > > which gives > format > > udp > hostname[@interface[@namespace]][:port] > > > IPv4-address[@interface[@namespace]][:port] > > > > ons 23 jan. 2019 kl 20:38 skrev Bill Fenner >: > >> My attempts at updat

Re: [PATCH 0/6] Add support for interface binding

On Wed, Jan 23, 2019 at 10:17 PM Bart Van Assche wrote: > On 1/23/19 9:43 AM, Bill Fenner wrote: > > The pattern I was trying to follow from the existing code appeared to be > > basically > > > > if (cp == delimiter of optional section) { > > *cp = '\

Re: [PATCH 0/6] Add support for interface binding

My attempts at updating the man page formats really poorly in 80 columns: At its simplest, the AGENT specification may consist of a host- name, or an IPv4 address in the standard "dotted quad" notation. In this case, communication will be attempted using UDP/IPv4 to

Re: [PATCH 0/6] Add support for interface binding

On Wed, Jan 23, 2019 at 12:58 AM Anders Wallin wrote: > Hi Bill, > > I'm missing updates to the documentation/man pages. (I can't find that the > man pages are update with @iface either) > Yes, I documented it in the same place as @intf ;-) I'll fix that. Bill

Re: [PATCH 0/6] Add support for interface binding

On Wed, Jan 23, 2019 at 12:15 AM Bart Van Assche wrote: > On 1/22/19 12:40 PM, Bill Fenner wrote: > > On Wed, Nov 7, 2018 at 1:26 AM Bart Van Assche > <mailto:bvanass...@acm.org>> wrote: > > > > On 11/6/18 8:03 AM, Bill Fenner wrote: > > > Giv

Re: [PATCH 0/6] Add support for interface binding

On Wed, Nov 7, 2018 at 1:26 AM Bart Van Assche wrote: > On 11/6/18 8:03 AM, Bill Fenner wrote: > > Given your proposed code structure, I imagine that we could add network > > namespaces to netsnmp_ep too - this basically ends up using "socketat( > > /* magic */, family,

Re: [PATCH 0/6] Add support for interface binding

I've applied my clientaddr parsing fix for IPv4 and IPv6, passing ":0" as the default transport, and also modified the IPv6 address parser to handle a bare IPv6 address (no brackets, no port). With these changes, all of the tests pass in their original form. I'd like to add some more tests for

Re: [PATCH 0/6] Add support for interface binding

> 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

Re: [PATCH 0/6] Add support for interface binding

(They were regressions before your changes here, but your changes broke my fix that Sam tried in https://sourceforge.net/p/net-snmp/bugs/2888/ ) Bill On Tue, Nov 6, 2018 at 3:31 PM Bill Fenner wrote: > Playing with this in V5-8-patches, I see it broke my fix for using > clientaddr to specify th

Re: [PATCH 0/6] Add support for interface binding

RT, is probably completely working around this same bug of setting the port when it doesn't need to be set, and could be eliminated altogether if that bug is fixed.) Bill On Tue, Nov 6, 2018 at 11:03 AM Bill Fenner wrote: > Hi Bart, > > My main question is, what's the adv

Re: [PATCH 0/6] Add support for interface binding

Hi Bart, My main question is, what's the advantage of storing the IPv4/IPv6 address as a string and a port number, instead of as a sockaddr_*? I.e., why use netsnmp_ep_str? Is the API change here ok? Are we assuming that nobody ever calls netsnmp_foo_transport() directly? Should there be an

Re: configure interface to send traps

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

Re: Issue 10852 in oss-fuzz: net-snmp: Build failure

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:

Re: Test code review request

gt;> 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 >> >> (Patch appended)

Re: Test code review request

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

Test code review request

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

Re: [PATCH / request for votes] Support double byte characters

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

Re: [PATCH 5/9] snmplib/transports: Unbreak the MSVC build

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 > > co

Re: [PATCH 5/9] snmplib/transports: Unbreak the MSVC build

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: >

Re: net-snmp 5.8: "unknown snmp version 193" from agentx subagent

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. --

Re: net-snmp 5.8: "unknown snmp version 193" from agentx subagent

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

Re: [PATCH; request for votes] snmplib: Avoid that sprint_realloc_octet_string() triggers a segmentation fault

On Mon, May 21, 2018 at 11:18 AM, Wes Hardaker < harda...@users.sourceforge.net> wrote: > Bill Fenner <fen...@gmail.com> writes: > > > So, +1 on committing Bart's patch, because it accomplishes the goal of > > fixing the regression, with the caveat that I really

Re: [PATCH; request for votes] snmplib: Avoid that sprint_realloc_octet_string() triggers a segmentation fault

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

Re: [PATCH; request for votes] snmplib: Avoid that sprint_realloc_octet_string() triggers a segmentation fault

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

Re: [PATCH, RFC] Add Travis and Appveyor CI support

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>

Re: RFC: fix --enable-read-only build failure due to snmpping

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

Re: RFC: fix clientaddr for 5.8

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

RFC: fix --enable-minimalist build failure due to target MIB

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

Re: On the nature of backward comparability

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

RFC: fix --enable-read-only build failure due to snmpping

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:

snmpping doesn't build with --enable-read-only

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

RFC: fix clientaddr for 5.8

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 -

Re: RFC: "-@" command line argument to set clientaddr per request/session

On Sun, May 6, 2018 at 7:33 PM, Bill Fenner <fen...@gmail.com> wrote: > On Sun, May 6, 2018 at 4:33 PM, Robert Story <rst...@freesnmp.com> wrote: > >> BF> The tests: >> BF> https://github.com/fenner/net-snmp/commit/41be11b4e3ab93cda3 >> 76bf044de2f77

Re: RFC: "-@" command line argument to set clientaddr per request/session

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

Re: RFC: "-@" command line argument to set clientaddr per request/session

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>

Re: 5.8 testing status

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

Re: 5.8 testing status

On Fri, May 4, 2018 at 11:25 AM, Bill Fenner <fen...@gmail.com> 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:trapso

Re: RFC: "-@" command line argument to set clientaddr per request/session

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

Re: 5.8 testing status

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

Re: 5.8 testing status

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

Re: RFC: "-@" command line argument to set clientaddr per request/session

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

Re: 5.8 testing status

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

Re: DISMAN PING MIB test case question

On Fri, Apr 27, 2018 at 12:15 PM, Keith Mendoza <ke...@icei.org> 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 sinc

RFC: "-@" command line argument to set clientaddr per request/session

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

Re: 5.8 testing status

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,

Re: 5.8 testing status

On Thu, Apr 26, 2018 at 10:00 PM, Bill Fenner <fen...@gmail.com> wrote: > On Thu, Apr 26, 2018 at 10:02 AM, Bart Van Assche <bvanass...@acm.org> > wrote: > >> On 04/26/18 04:57, Bill Fenner wrote: >> >>> A new feature went into 5.8 that conflicts a li

Re: 5.8 testing status

On Thu, Apr 26, 2018 at 10:02 AM, Bart Van Assche <bvanass...@acm.org> 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

Re: DISMAN PING MIB test case question

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

Re: 5.8 testing status

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

Re: [PATCH RFC] Add Travis and Appveyor CI support

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.

Re: Summary of meeting between NET-SNMP devs and ICEI

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

  1   2   3   >