relayd and TLS client cert verification

2018-11-22 Thread Ashe Connor
Hi all, It appears that relayd doesn't support TLS client certificate validation (in the manner that httpd does with "tls client ca [cafile]"). Would there be interest in a patch that added such support? Apologies if I've missed something obvious here. Best, Ashe

Re: typo in vxlan.4

2018-11-22 Thread Josh Grosse
On Thu, Nov 22, 2018 at 06:33:57PM +0100, Reyk Floeter wrote: > On Thu, Nov 22, 2018 at 11:50:52AM -0500, Josh Grosse wrote: > > The page refers to vmx0 rather than vxlan0 in its pf.conf > > guidance. > > > > ... I committed a change to use em0 instead of vmx0. > > vmx0 wasn't a good example (I

Re: typo in vxlan.4

2018-11-22 Thread Reyk Floeter
On Thu, Nov 22, 2018 at 11:50:52AM -0500, Josh Grosse wrote: > The page refers to vmx0 rather than vxlan0 in its pf.conf > guidance. > ... I committed a change to use em0 instead of vmx0. vmx0 wasn't a good example (I wrote the manpage around the time when vmx(4) was new and I used it as a paren

Re: typo in vxlan.4

2018-11-22 Thread Reyk Floeter
On Thu, Nov 22, 2018 at 11:50:52AM -0500, Josh Grosse wrote: > The page refers to vmx0 rather than vxlan0 in its pf.conf > guidance. > Are you sure? In this example, vmx0 is the parent interface that receives VXLAN UDP packets - it could also be em0, ix0, or whatever you like. Reyk > Index: vx

Re: bgpd refactor community code

2018-11-22 Thread Claudio Jeker
On Tue, Nov 13, 2018 at 06:53:55PM +0100, Claudio Jeker wrote: > This is a large diff that changes the way communities are stored in > filters and filter_sets. Both standard communities and large communities > now share the same data structure for lookups and at the same time the > filters are exte

typo in vxlan.4

2018-11-22 Thread Josh Grosse
The page refers to vmx0 rather than vxlan0 in its pf.conf guidance. Index: vxlan.4 === RCS file: /systems/cvs/src/share/man/man4/vxlan.4,v retrieving revision 1.7 diff -u -p -r1.7 vxlan.4 --- vxlan.4 22 Feb 2018 01:35:04 -

Re: pvclock(4)

2018-11-22 Thread Landry Breuil
On Thu, Nov 22, 2018 at 05:24:10PM +0100, Landry Breuil wrote: > On Thu, Nov 22, 2018 at 07:44:01AM -0800, Mike Larkin wrote: > > On Thu, Nov 22, 2018 at 04:37:49PM +0100, Reyk Floeter wrote: > > > On Mon, Nov 19, 2018 at 01:12:46PM +0100, Reyk Floeter wrote: > > > > the attached diff is another at

Re: pvclock(4)

2018-11-22 Thread Landry Breuil
On Thu, Nov 22, 2018 at 07:44:01AM -0800, Mike Larkin wrote: > On Thu, Nov 22, 2018 at 04:37:49PM +0100, Reyk Floeter wrote: > > On Mon, Nov 19, 2018 at 01:12:46PM +0100, Reyk Floeter wrote: > > > the attached diff is another attempt at implementing a pvclock(4) > > > guest driver. This improves t

cleanup decision process

2018-11-22 Thread Claudio Jeker
Since a while announcements added by bgpctl will overwrite the ones from the config and no longer live next to each other. Because of this step 13 in the decision process is no longer needed. OK? -- :wq Claudio Index: bgpd.8 === RCS

Re: pvclock(4)

2018-11-22 Thread Mike Larkin
On Thu, Nov 22, 2018 at 04:37:49PM +0100, Reyk Floeter wrote: > On Mon, Nov 19, 2018 at 01:12:46PM +0100, Reyk Floeter wrote: > > the attached diff is another attempt at implementing a pvclock(4) > > guest driver. This improves the clock on KVM and replaces the need > > for using the VM-expensive

Re: pvclock(4)

2018-11-22 Thread Reyk Floeter
On Mon, Nov 19, 2018 at 01:12:46PM +0100, Reyk Floeter wrote: > the attached diff is another attempt at implementing a pvclock(4) > guest driver. This improves the clock on KVM and replaces the need > for using the VM-expensive acpihpet(4). > So far I only got positive reports. Where are the pr