RFC: fix clientaddr for 5.8

2018-05-14 Thread Bill Fenner
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

Re: RFC: fix clientaddr for 5.8

2018-05-14 Thread Bart Van Assche
On 05/14/18 08:00, Bill Fenner wrote: 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 - sto

Re: RFC: fix clientaddr for 5.8

2018-05-14 Thread Robert Story
On Mon, 14 May 2018 08:44:19 -0700 Bart wrote: BVA> > https://sourceforge.net/p/net-snmp/code/ci/3defab66a7aee60ba582a8254412abd2e630c321/ BVA> > BVA> > It turns out that when you specify a clientaddr, the steps BVA> > the function takes are: BVA> > BVA> > - zero out addr_pair BVA> > - store the

Re: RFC: fix clientaddr for 5.8

2018-05-14 Thread Niels Baggesen via Net-snmp-coders
Den 14-05-2018 kl. 20:05 skrev Robert Story: +1 on both counts (commit it, but use cherry-pick). +1 (and I wouldn't mind the OpenBSD part getting merged too) /Niels -- Niels Baggesen - @home - Ã…rhus - Denmark - n...@users.sourceforge.net The purpose of computing is insight, not numbers ---

Re: RFC: fix clientaddr for 5.8

2018-05-15 Thread Bill Fenner
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