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
On Fri, 4 May 2018 11:25:35 -0400 Bill wrote:
BF> I started writing a test for this, and found that it's seriously
BF> convoluted. The combination of clientaddr + trap*sink results
BF> in the bind() attempting to use port 161 for the clientaddr, so
BF> it doesn't work as non-root (in the test
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
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
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 address for
BF> > BF> traps any more. (And given that the code
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
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 suspect
BF> it doesn't work for client requests either).
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
On Sun, 29 Apr 2018 12:10:12 -0400 Bill wrote:
BF> BF> It's plausible that a workaround as simple as
BF> > BF>
BF> > BF> +/*
BF> > BF> + * We lie about being SNMPv3, because ...
BF> > BF> + */
BF> > BF> if (add_trap_session(main_session,
BF> > BF> AGENTX_MSG_NOTIFY, 1,
BF> > BF>
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,
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 how to
BF> >>> treat agentx sessions so doesn't count them -
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
>>> subagent. I
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/36270409/
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/36270409/
You can replicate it by configuring a normal snmpd as an agentx master,
and then
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
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?
16 matches
Mail list logo