This FAQ is adapapted from the previous release notes. Please see man ngbuddy (also available in the repo as README.md) for detailed usage instructions.
These scripts were developed to assist with new netgraph features in vm-bhyve 1.5+, and were inspired by jng and the Netgraph article by Klara Systems.
The default public bridge binds to a real interface associated with the default route.
The default private bridge creates an interface called nghost0 intended for host-only networking or NAT networking. For example, you can run a DHCP & DNS server on nghost0 for your guests, and use pf or ipfw to NAT out.
It is generally a good practice to keep bridge names consistent between failover hosts, and you might want bridge names that are more descriptive than the defaults. For example cli1bridge, lan, and wan206 might be clearer bridge names than "public"/"private".
Can this coexist with my if_bridge (epair/tap) setup?
Yes; an if_bridge interface and eiface (Netgraph interface) can share a network through a bridge, including a physical or private network with DHCP. Try ifconfig bridge0 addm nghost0 to link your "private" ngup interfaces to your if_bridge epairs/taps/etc. This is handy for an in-place virtual jail migration from epair to netgraph.