vmctl: start: Require one interface at minimium with -i

2019-10-25 Thread Klemens Nanni
It makes no sense to allow zero interfaces; either a positive count is given or -i is omitted entirely. vm.conf(5) does not allow interface configuration that results in zero interfaces either. $ doas vmctl start -Li0 -b ~/bsd.rd foo vmctl: starting without disks vm

Re: vmd: static address for local interfaces, fix static tapX names

2019-10-25 Thread Mischa Peters
-- > On 25 Oct 2019, at 21:53, Mike Larkin wrote: > > On Fri, Oct 25, 2019 at 07:47:35PM +, Reyk Floeter wrote: >>> On Fri, Oct 25, 2019 at 12:27:25PM -0700, Mike Larkin wrote: >>> On Fri, Oct 25, 2019 at 06:15:59PM +, Reyk Floeter wrote: Hi, the attached diff is rather l

Re: [PATCH: 0/3] MMIO handler in vmm(4)

2019-10-25 Thread Mike Larkin
On Thu, Oct 24, 2019 at 08:54:16AM +0900, Iori YONEJI wrote: > Hello tech@, > > I introduce an MMIO handler in vmm(4) as an attempt to make a > scaffolding for full-featured MMIO handler which requires more effort. > I will send a few emails with patches after this one. First of all, I > show the

Re: vmd: static address for local interfaces, fix static tapX names

2019-10-25 Thread Reyk Floeter
On Fri, Oct 25, 2019 at 12:27:25PM -0700, Mike Larkin wrote: > On Fri, Oct 25, 2019 at 06:15:59PM +, Reyk Floeter wrote: > > Hi, > > > > the attached diff is rather large and implements two things for vmd: > > > > 1) Allow to configure static IP address/gateway pairs local interfaces. > > 2)

Re: vmd: static address for local interfaces, fix static tapX names

2019-10-25 Thread Mike Larkin
On Fri, Oct 25, 2019 at 07:47:35PM +, Reyk Floeter wrote: > On Fri, Oct 25, 2019 at 12:27:25PM -0700, Mike Larkin wrote: > > On Fri, Oct 25, 2019 at 06:15:59PM +, Reyk Floeter wrote: > > > Hi, > > > > > > the attached diff is rather large and implements two things for vmd: > > > > > > 1)

Re: vmd: static address for local interfaces, fix static tapX names

2019-10-25 Thread Mike Larkin
On Fri, Oct 25, 2019 at 06:15:59PM +, Reyk Floeter wrote: > Hi, > > the attached diff is rather large and implements two things for vmd: > > 1) Allow to configure static IP address/gateway pairs local interfaces. > 2) Skip statically configured interface names (eg. tap0) when > allocating d

vmd: static address for local interfaces, fix static tapX names

2019-10-25 Thread Reyk Floeter
Hi, the attached diff is rather large and implements two things for vmd: 1) Allow to configure static IP address/gateway pairs local interfaces. 2) Skip statically configured interface names (eg. tap0) when allocating dynamic interfaces. Example: ---snip--- vm "foo" { disable l

faq/current.html: reset changes already present in 6.6

2019-10-25 Thread Adriano Barbosa
Hi in faq/current.html there are still modifications wich are already present in 6.6 and described in faq/upgrade66.html. Best -- Adriano Barbosa Index: faq/current.html === RCS file: /cvs/www/faq/current.html,v retrieving revision

Re: HID devices without numbered reports

2019-10-25 Thread Patrick Wildt
On Fri, Oct 25, 2019 at 03:59:25PM +0200, Patrick Wildt wrote: > On Fri, Oct 25, 2019 at 03:10:48PM +1100, Damien Miller wrote: > > Hi, > > > > Some HID devices do not list any report IDs for communication, e.g. my > > Yubikey5: > > > > > uhidev0: iclass 3/0 > > > uhid0 at uhidev0: input=64, outp

Re: HID devices without numbered reports

2019-10-25 Thread Patrick Wildt
On Fri, Oct 25, 2019 at 03:10:48PM +1100, Damien Miller wrote: > Hi, > > Some HID devices do not list any report IDs for communication, e.g. my > Yubikey5: > > > uhidev0: iclass 3/0 > > uhid0 at uhidev0: input=64, output=64, feature=0 > > ugen0 at uhub0 port 2 configuration 1 "Yubico YubiKey FIDO

Re: HID devices without numbered reports

2019-10-25 Thread Martin Pieuchot
On 25/10/19(Fri) 15:10, Damien Miller wrote: > Some HID devices do not list any report IDs for communication, e.g. my > Yubikey5: > > > uhidev0: iclass 3/0 > > uhid0 at uhidev0: input=64, output=64, feature=0 > > ugen0 at uhub0 port 2 configuration 1 "Yubico YubiKey FIDO+CCID" rev > > 2.00/5.12 a

ospfd: type p2p

2019-10-25 Thread Remi Locherer
Hi tech@, earlier this year I sent a diff that allowed to change an interface from broadcast to point-to-point. https://marc.info/?l=openbsd-tech&m=156132923203704&w=2 It turned out that this was not sufficient. It made the adjacency come up in p2p mode (no selection of DR or BDR) but didn't set

Re: vmd: opentap: ifname is not optional

2019-10-25 Thread Reyk Floeter
On Fri, Oct 25, 2019 at 10:16:14AM +0200, Klemens Nanni wrote: > The function argument is not checked at all and strlcpy(3) will segfault > if it NULL. > > Slightly adjust the comment to reflect this and defer the error case's > default value to the end: If a node is successfully opened, ifname g

vmd: opentap: ifname is not optional

2019-10-25 Thread Klemens Nanni
The function argument is not checked at all and strlcpy(3) will segfault if it NULL. Slightly adjust the comment to reflect this and defer the error case's default value to the end: If a node is successfully opened, ifname gets rewritten. There's only one usage of this function in config.c which