Patrick Welche <pr...@welche.eu> wrote: > Looking at documentation such as "Configuring bridged networking > on a NetBSD host" > > https://www.netbsd.org/docs/guide/en/chap-virt.html#chap-virt-net-bridge > > suggests > > You can now pass the arguments to QEMU to run with bridged networking: > > -netdev tap,id=tap0,ifname=tap0,script=no -device virtio-net-pci,netdev=tap0 > > but now we need to use vether(4) rather than tap(4). > > What is the new incantation? (-netdev tap implies "/dev/tapN"?)
Why not carry on using tap(4) with QEMU? Letting an application get access to the network stack seems to me to be the correct use of tap(4). People were using tap(4) for other purposes, vether(4) may be a better match for those.
