veb(4) control flooding via the discover flag only

2023-04-30 Thread Nicolas Bouliane
This make it possible to prevent port flooding by simply disabling the discover bit per interface. --- sys/net/if_veb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys/net/if_veb.c b/sys/net/if_veb.c index c5f865b7154..58d48312e41 100644 --- a/sys/net/if_veb.c +++

Re: OpenBSD 7.2 on Oracle Cloud

2023-04-30 Thread Aaron Mason
On Mon, May 1, 2023 at 10:08 AM Aaron Mason wrote: > > I can reproduce it with this in QEMU 8.0 in Winders (thanks Antun who > sent something like this to the bugs@ list): > > qemu-system-x86_64 -accel whpx,kernel-irqchip=off -machine q35 \ >-cpu EPYC-Rome,-monitor -m 8g -smp

Re: OpenBSD 7.2 on Oracle Cloud

2023-04-30 Thread Aaron Mason
I can reproduce it with this in QEMU 8.0 in Winders (thanks Antun who sent something like this to the bugs@ list): qemu-system-x86_64 -accel whpx,kernel-irqchip=off -machine q35 \ -cpu EPYC-Rome,-monitor -m 8g -smp 6,sockets=1,cores=6 \ -nic user,model=virtio-net-pci,hostfwd=tcp::10022-:22

Re: OpenBSD 7.2 on Oracle Cloud

2023-04-30 Thread Stefan Fritsch
Hi, what qemu version are you using? I cannot reproduce this with qemu 7.2. Can you try with a newer qemu? Cheers, Stefan Am 25.04.23 um 14:53 schrieb Aaron Mason: Yeah I'm getting the same thing. Trying a build in QEMU and transferring in to see if that helps. Will report back. Ok, good

Re: vmd(8): multi-process device emulation (plz test)

2023-04-30 Thread Brian Conway
On Sun, Apr 30, 2023, at 12:43 PM, Brian Conway wrote: > On Tue, Apr 25, 2023, at 9:47 AM, Dave Voutila wrote: >> tech@: >> >> The below diff splits out virtio device emulation for virtio block and >> network devices into separate fork+exec'd & pledge(2)'d subprocesses. >> >> In order of priority,

Re: vmd(8): multi-process device emulation (plz test)

2023-04-30 Thread Brian Conway
On Tue, Apr 25, 2023, at 9:47 AM, Dave Voutila wrote: > tech@: > > The below diff splits out virtio device emulation for virtio block and > network devices into separate fork+exec'd & pledge(2)'d subprocesses. > > In order of priority, this diff: > > 1. Isolates common exploit targets (e.g.

installer: amd64 EFI: default to GPT

2023-04-30 Thread Klemens Nanni
Installing to a wiped disk on EFI machines suggests MBR not GPT when chosing (E)dit because MBR vs. GPT in this manual case is picked based on existing data on the disk, not whether it has EFI. Fix that so users get correct instructions and don't end up with legacy partitioning in fresh installs