Sad Clouds <cryintotheblue...@gmail.com> writes: > Hi, current documentation at: > https://www.netbsd.org/docs/rump/sptut.html > > suggests using tap(4) and bridge(4) on the host, then within rump > server virt(4) can be used to provide connectivity via tap(4). > > However, NetBSD-10 tap(4) man page states: > > CAVEATS > Starting from NetBSD 10.0, the tap driver can no longer be used as a > bridge(4) endpoint because it supports a link state based on if it has > been opened or not. Use the vether(4) driver instead as it's been > explicitly designed for this purpose. > > So the question is - what is the alternative for rump server virt(4) as > it seems to only want to open tap(4) devices and not vether(4)?
My guess is that in 10, vether is split off from tap, and that rump/virt was simply not updated to use it instead. If so, it simply remains for someone to fix the code and docs.
