In a direct e-mail from November 30, 2025 ray@ said he had little access to his FreeBSD mailbox these days but said he didn't really have input on this, and recommended asking ed@ instead.

GitHub PR rebased on main.

An ng_device(4) is not an interface, so it does not have a MAC address. The way I see it, it is just a wire. If you think about a tap(4), it's like an ng_eiface(4) linked to a ng_device. But the MAC address belongs to the ng_eiface end, not the ng_device one.

Github pull request created: https://github.com/freebsd/freebsd-src/pull/1912

Replace asserts() with error messages

Added a unix: prefix for UNIX domain sockets

Replace strncpy with strlcpy, add assert before freeaddrinfo and newline to bhyve.8

Here you go: https://github.com/freebsd/freebsd-src/pull/1880

Thanks a lot for your help!

Move ENXIO check behind mutex and add or fix comments

Remove superflous mtx_unlock and braces

Clean up device destruction

Fix braces, indentation, restore original lock and set VNET

Add reference to netgraph(4)

Add missing carriage return in bhyve.8

In D52542#1201906, @markj wrote:

tap_init() will open the device and add it to the mevent loop, which uses kevent() under the hood. But, ng_device doesn't implement d_kqfilter, i.e., ngd_cdevsw doesn't have a d_kqfilter implementation, in contrast with tap devices. How does bhyve know when to read packets from the device?

Removed superfluous Xo and Xc in bhyve.8

Added bhyve.8 changes and fixed if syntax.