ifconfig description for wireguard peers

2021-10-20 Thread Noah Meier
Hi, While wireguard interfaces can have a description set by ifconfig, wireguard peers currently cannot. I now have a lot of peers and descriptions of them in ifconfig would be helpful. This diff adds a 'wgdesc' option to a 'wgpeer' in ifconfig (and a corresponding '-wgdesc' option). Man page

Re: nsd 4.3.8

2021-10-20 Thread Mischa
Got it. Oct 20 20:47:19 name2 nsd[62305]: nsd starting (NSD 4.3.8) Oct 20 20:47:19 name2 nsd[37128]: nsd started (NSD 4.3.8), pid 31864 Oct 20 22:07:09 name2 nsd[37128]: signal received, shutting down... Oct 20 22:07:09 name2 nsd[39445]: nsd starting (NSD 4.3.7) Oct 20 22:07:10 name2 nsd[72021]:

Re: nsd 4.3.8

2021-10-20 Thread Florian Obser
Sorry, I messed up the GitHub issues, this is the interesting one. - Fix #194: Incorrect NSEC3 response for SOA query below delegation point. On 20 October 2021 18:24:13 CEST, Florian Obser wrote: > >Particularly interesting is >- Fix #190: NSD returns 3 NSEC3 records for NODATA response. > >w

Re: nsd 4.3.8

2021-10-20 Thread Florian Obser
I mean the diff I sent to bugs@ in response to the thread you started on misc. "Re: NSD exit status 11 on 7.0" This thread is about upgrading nsd in current, but we also need to fix 7.0. I thought you are running stable in production? Anyway, having the full upgrade tested is also valuable, so

Re: nsd 4.3.8

2021-10-20 Thread Mischa
Is the below patch not needed? I did run it without the below patch first, without any problems. After I applied the below patch and compiled again. Mischa On 2021-10-20 21:34, Florian Obser wrote: Uhm, could you please try the single patch from the other mail on 7.0? We are probably not going

Re: nsd 4.3.8

2021-10-20 Thread Florian Obser
Uhm, could you please try the single patch from the other mail on 7.0? We are probably not going to syspatch to a new nsd version in 7.0. On 20 October 2021 21:18:17 CEST, Mischa Peters wrote: >Hi Florian, > >Great stuff! >Applied both patches and NSD has been running without crashing since >20

Re: nsd 4.3.8

2021-10-20 Thread Mischa Peters
Hi Florian, Great stuff! Applied both patches and NSD has been running without crashing since 20:47 CEST. Oct 20 20:47:19 name2 nsd[62305]: nsd starting (NSD 4.3.8) Oct 20 20:47:19 name2 nsd[37128]: nsd started (NSD 4.3.8), pid 31864 Oct 20 20:47:30 name2 /bsd: carp24: state transition: BACKUP

Re: nsd 4.3.8

2021-10-20 Thread Florian Obser
On 2021-10-20 18:24 +02, Florian Obser wrote: > +4.3.8 > + > +FEATURES: > + - Set default for answer-cookie to no. Because in server deployments > + with mixed server software, a default of yes causes issues. sthen and me think that we shouldn't flip-flop between cookie

nsd 4.3.8

2021-10-20 Thread Florian Obser
Particularly interesting is - Fix #190: NSD returns 3 NSEC3 records for NODATA response. which I believe is a fix for the problem mischa reported on misc: "NSD exit status 11 on 7.0" Tests, OKs? diff --git doc/RELNOTES doc/RELNOTES index 054eb9b8f60..b7157bbc0a6 100644 --- doc/RELNOTES +++ doc

Re: Missing semicolon in snmpd/parse.y

2021-10-20 Thread Otto Moerbeek
On Wed, Oct 20, 2021 at 01:58:03PM +0200, Gerhard Roth wrote: > Hi, > > the rule for 'listen_udptcp' is missing a semicolon at its end. > > I have no idea what yacc does to the following 'port' rule without > that semicolon. Looks like the generated c code is the same; ok otto@ -Otto

Missing semicolon in snmpd/parse.y

2021-10-20 Thread Gerhard Roth
Hi, the rule for 'listen_udptcp' is missing a semicolon at its end. I have no idea what yacc does to the following 'port' rule without that semicolon. Gerhard Index: usr.sbin/snmpd/parse.y === RCS file: /cvs/src/usr.sbin/snmpd/par