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: overflow in implicit constant conversion
[-Werror=overflow] on
Looking into using clang on Windows might be worth the effort to get
net-snmp code caught up to C99. Google Chrome now uses clang to
compile in Windows:
http://blog.llvm.org/2018/03/clang-is-now-used-to-build-chrome-for.html
Thanks,
Keith
-Original Message-
Subject: RE: C99 (was: Re: Fix
> Bill
>
>
> On Thu, Mar 22, 2018 at 6:13 PM, Keith Mendoza wrote:
>>
>> My next question is then, why exactly is it basically copying parts of
>> an oid into cp and basically truncating parts of it?
>>
>> Thanks,
>> Keith
>> Thanks,
>> Ke
I personally feel that whoever is running the automated tests should
make the necessary changes to their environment to resolve any
hostname that is needed to run the tests. In my case,
onea.net-snmp.org and twoa.net-snmp.org resolves to IP's in the
127.0.0.0/24 network; however no.such.address res
Bart,
Thank you for your interest. Please let us know when you're free; we
will schedule the meeting based on what works best for the net-snmp
devs who would like to join us.
Thanks,
Keith
On Tue, Apr 3, 2018 at 7:11 PM, Bart Van Assche wrote:
> On 04/03/18 17:54, Eric S. Raymond wrote:
>>
>> IC
Bart,
On Sun, Apr 1, 2018 at 8:26 AM, Bart Van Assche wrote:
> On 03/31/18 22:19, Keith Mendoza wrote:
>>
>> I personally feel that whoever is running the automated tests should
>> make the necessary changes to their environment to resolve any
>> hostname that
So far, this is the time that may work for everyone if we do it the
week of April 8 (UTC and US time zones): 5:30 AM PDT/6:30 AM MDT/7:30
AM CDT/8:30 AM EDT/12:30 PM UTC--6:00 AM PDT/7:00 AM MDT/8:00 AM
CDT/9:00 AM EDT/1:00 PM UTC.
Eric,
How do you feel about having the meeting the week of April 1
So again, at what point do we stop adding code to net-snmp because
ISP's are messing around as if they're doing us a favor by letting us
use their services?
Thanks,
Keith
Thanks,
Keith
On Wed, Apr 4, 2018 at 7:13 PM, Bart Van Assche wrote:
> On 04/04/18 09:30, Keith Mendoza w
Simon,
Those options have to be enabled in the configure options. I suggest
building with the following configure options:
--with-transports="DTLSUDP" --with-security-modules="tsm"
There might be other configure options that you need to make it work.
Just note though that SNMPv3 RFC _does not
net-snmp dev team,
Ian and I went through another round of going through the bug lists
for ones that we feel can either be closed, or placed in WONTFIX:
* 1989, 2490, 2101, 1765, 2554: These have proposed patches that
doesn't appear to have been applied.
* 2438: Fixed in patch 1249, which is merge
hanks,
Keith
On Wed, Apr 4, 2018 at 10:18 PM, Eric S. Raymond wrote:
> Keith Mendoza :
>> So far, this is the time that may work for everyone if we do it the
>> week of April 8 (UTC and US time zones): 5:30 AM PDT/6:30 AM MDT/7:30
>> AM CDT/8:30 AM EDT/12:30 PM UTC--6:00
On Thu, Apr 12, 2018, at 10:03 AM, Bill Fenner wrote:
> 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
On Thu, Apr 12, 2018, at 2:18 PM, Magnus Fromreide wrote:
> On Thu, Apr 12, 2018 at 12:19:35PM -0700, Keith Mendoza wrote:
> > On Thu, Apr 12, 2018, at 10:03 AM, Bill Fenner wrote:
> > > I'm sorry that I wasn't available for this meeting. I think one important
>
As I mentioned in the "Summary of meeting between NET-SNMP devs and ICEI"
thread, here's a list of bugs that I found could be included in a 5.7.4 release.
Comment indicate change is in v5-7-patch branch, and waiting for confirmation
from submitter
* 2810 Logical error in agent/helpers/table.c
Net-SNMP devs,
After a few discussion in IRC, I feel that I have an understanding on why
project leadership prefers patches over merge request. I would like to
summarize them here to make sure that my understanding is correct. Patches are
applied in the master and the current release's branch (a
Not ideal; but I guess it'll have to do for now.
On Sat, Apr 14, 2018, at 3:56 PM, Bart Van Assche wrote:
> On 04/05/18 16:38, Lee wrote:
> > On 4/5/18, Keith Mendoza wrote:
> >> So again, at what point do we stop adding code to net-snmp because
> >> ISP's a
Bart,
I was actually working on this yesterday. This is what I know so far after a
few hours of digging into this: It appears that there's an issue with getting
to the memory address that EVP_sha512() returns when it's called in
sc_get_openssl_hashfn(). Why this is so, I don't know. Below are de
Bart,
I was hoping to discuss with you on IRC; but, you're not online.
On Sun, Apr 22, 2018, at 4:10 PM, Bart Van Assche wrote:
> On 04/22/18 08:35, Keith Mendoza wrote:
> > Bart,
> > I was actually working on this yesterday. This is what I know so far after
> > a few
Bart,
On Sun, Apr 22, 2018, at 4:59 PM, Keith Mendoza wrote:
> Bart,
> I was hoping to discuss with you on IRC; but, you're not online.
>
> On Sun, Apr 22, 2018, at 4:10 PM, Bart Van Assche wrote:
> > On 04/22/18 08:35, Keith Mendoza wrote:
> > > Bart,
>
Bart,
On Mon, Apr 23, 2018, at 6:45 AM, Bart Van Assche wrote:
> On 04/23/18 00:34, Keith Mendoza wrote:
> > Even with the -std=c89 flag the issue is still present. I was able to
> > replicate the issue with the following code:
> >
> > === BEGIN C CODE ==
Net-SNMP dev team,
I have submitted a merge request to verify that when the
--enable-blumenthal-aes is used in configure that it checks that OpenSSL's
aes.h and evp.h are available. Merge request is at
https://sourceforge.net/p/net-snmp/code/merge-requests/14/. This should fully
resolve the fol
Bart,
Out of curiosity, do you have a "fork" of Net-SNMP on github to connect it to
Travis and Appveyor?
On Wed, Apr 25, 2018, at 8:06 AM, Bart Van Assche wrote:
> Hello,
>
> One of the advantages of github over SourceForge is that integration
> with continuous integration (CI) services like Tr
Bart,
On Wed, Apr 25, 2018, at 9:28 AM, Bart Van Assche wrote:
> On 04/25/18 10:04, Keith Mendoza wrote:
> > Net-SNMP dev team,
> > I have submitted a merge request to verify that when the
> > --enable-blumenthal-aes is used in configure that it checks that OpenSSL'
On Wed, Apr 25, 2018, at 11:05 AM, Bart Van Assche wrote:
> On 04/25/18 11:54, Keith Mendoza wrote:
> > Out of curiosity, do you have a "fork" of Net-SNMP on github to connect it
> > to Travis and Appveyor?
>
> Hello Keith,
>
> If you are looking for a
On Wed, Apr 25, 2018, at 12:08 PM, Robert Story wrote:
> On Thu, 12 Apr 2018 10:31:13 -0500 Ian wrote:
> IB> This morning we (Keith, Ian) met with an assortment of the
> IB> NET-SNMP developers / contributors (primarily Bart Van Assche)
> IB> to discuss how we could best help the project. The meeti
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 against
master branch, are there any bugs that are part of 5.8?
D
I have a question about what permissions DISMAN PING MIB test case expects. I'm
running on a macOS 12.3.4 with --enable-blumenthal-aes --with-openssl= --with-defaults. When I run make test as my normal
user I get "skipped: Not permitted to create raw sockets". However, when I run
make test using
On Fri, Apr 27, 2018, at 7:38 AM, Venkateswarlu Konamki wrote:
> HI,
>
> I am facing one issue with snmp. While fecting the ifPhysAddress for my
> device interfaces, one of the mac address is displaying wrong data.
>
> Version : 5.7.3
> OS: armv7l GNU/Linux
Can you please provide more informa
an revisit this code after 5.8 is released?
>
> Bill
>
>
> On Thu, Apr 26, 2018 at 2:01 PM, Keith Mendoza wrote:
>
> > I have a question about what permissions DISMAN PING MIB test case
> > expects. I'm running on a macOS 12.3.4 with --enable-blumenthal-aes
On Fri, Apr 27, 2018, at 9:05 PM, Venkateswarlu Konamki wrote:
> Hi Robert,
>
> Iam running snmpd on my ARM embedded device. Since memory is important so i
> can't load any extra mibs into it. Any further solition ?
You have to load the MIB on the machine where you're running snmpget. Here's
t
On Fri, Apr 27, 2018, at 7:53 PM, Wes Hardaker wrote:
> Robert Story writes:
>
> |> That discussion is going on over on our admin list. It's not just a
> |> few of us running amok. ;-)
First, I meant no disrespect when I said "I think it would be best to get full
agreement from the team on thi
On Fri, Apr 27, 2018, at 2:40 PM, Robert Story wrote:
> On Wed, 25 Apr 2018 10:28:59 -0600 Bart wrote:
> BVA> On 04/25/18 10:04, Keith Mendoza wrote:
> BVA> > I have submitted a merge request to verify that when the
> BVA> > --enable-blumenthal-aes is used in con
On Fri, Apr 27, 2018, at 11:00 PM, Keith Mendoza wrote:
> >
> > Regardless, configure should be doing the right thing based on what
> > is currently installed.
> >
> > BVA> Regarding your pull request:
> > BVA> I'd like to a
n the module is not enabled at all.
On Mon, Apr 30, 2018, at 9:11 AM, Keith Mendoza wrote:
>
>
> On Sun, Apr 29, 2018, at 9:20 AM, Bill Fenner wrote:
> > On Fri, Apr 27, 2018 at 12:15 PM, Keith Mendoza wrote:
> >
> > > Bill,
> > >
> > > On Thu, Apr 26,
On Sun, Apr 29, 2018, at 9:20 AM, Bill Fenner wrote:
> 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.
Dave,
Try adding --with-openssl=/usr in the call to configure on your raspberry pi.
If you're brave you can also try 5.8pre3 from
https://sourceforge.net/projects/net-snmp/files/net-snmp/5.8-pre-releases/
--
Thanks,
Keith (pantherse)
On Wed, May 2, 2018, at 7:04 PM, Dave C wrote:
> I'm trying
; Encryption support: DES AES
> > Local DNSSEC validation:disabled
> > -
>
>
>
> root@raspberrypi:~# snmpd --version
> > NET-SNMP version: 5.8.pre3
> > Web: http://www.net-snmp.org/
I feel that Net-SNMP should follow what the OS maintainers are willing to
support. If they're saying they're only going back 2 versions; I strongly urge
the team to cut the support for them loose. I understand the team's desire to
maintain backwards compatibility; however, we have to consider th
On Fri, May 11, 2018, at 1:59 AM, Josef Ridky wrote:
> Hi,
>
> here are my 0.02$
>
> |
> | We have decided to move our Net-SNMP development to GitHub after many
> | wonderful years being hosted at SourceForge. We greatly appreciate
> | SourceForge's support of open source projects over the ye
Wes,
On Thu, May 10, 2018, at 4:12 PM, Wes Hardaker wrote:
> Keith Mendoza writes:
>
> > I would very much like to be part of the discussion regarding moving
> > to Github if its amenable to you guys.
>
> Sorry for the delay on this; I had a week and a half of constant
On Sun, May 13, 2018, at 3:41 PM, Bart Van Assche wrote:
> On 04/12/18 08:31, Ian Bruene wrote:
> > This morning we (Keith, Ian) met with an assortment of the NET-SNMP
> > developers / contributors (primarily Bart Van Assche) to discuss how we
> > could best help the project. The meeting went w
That is a very useful list. What I would recommend though is we should finish
dealing with the #ifdef hell and replacing autotools with cmake first. That way
if we have to onboard new people to the project they are dealing with the
"cleaned-up" code base.
On Sun, May 13, 2018, at 6:37 PM, Rober
Wes,
Thank you for taking the time to put the history of Net-SNMP's codebase to
paper. I feel that it puts why the codebase is the way it is in its proper
perspective.
After reading this very insightful essay, I feel that Net-SNMP being the
"de-facto SNMP stack" also means that it's the refere
Wes
On Mon, May 14, 2018, at 4:40 PM, Wes Hardaker via Net-snmp-coders wrote:
>
> We (my last employee) received a patch from a company that implemented a
> cmake build system for some percentage of the code. It was better in
> many ways and had issues in others as it was a different form of
>
On Tue, May 15, 2018, at 12:58 PM, Wes Hardaker wrote:
> Keith Mendoza writes:
>
> > Now that development is going to be done on github, what I would
> > recommend is forking from the official net-snmp and then maybe create
> > a branch on your github fork.
>
>
On Mon, Jun 4, 2018, at 9:31 AM, Bart Van Assche wrote:
> On 06/04/18 17:22, Wes Hardaker via Net-snmp-coders wrote:
> > So, I assume most people have seen that Microsoft is purchasing github.
> > We were just about to move Net-SNMP to GitHub, and certainly still can.
> > But it's definitely tim
46 matches
Mail list logo