finally got to updating OmniOS particulars in tcpdump and libpcap after the recent r151052 release

Nice, thanks :)

There are packages for clang17, 18 and 19 if they'd be useful to be installed in CI environment.

andyf: clang-19 would be nice

Hi to all. Moving my first steps with Crossbow... I managed to see several scenarios working (zones connected to etherstub and NATed to the physical network with ipfilter, the same but using VLAN and VNIC only, zones bridged to physical NIC, etc.). Wonderful system! :)

I'd like to know whether there are best practices to assign names to virtual links and interfaces, or if each Solaris/Illumos sysadmin uses its own naming scheme... if so, what is your favorite one?

during my tests, I found handy to set pretty stupid names: "vnic[N]" for VNICs linked to physical NICs, "net[N]" for etherstubs, "n[N]nic[N]" for VNICs linked to etherstubs, where "[N]" is a progressive integer number

any suggestion here from someone who have been using Crossbow in production environments?

warden: I have named them after the zone (e.g., zone "blah" gets "blah0") or sometimes after the VLAN (e.g,. "wifi0" or "comcast0")

It's really a site policy question for the most part

Named after zones is not a bad idea. I still use old-school GZ management of vnics and zonecfg(8) to pass them down on my OmniOS-powered HDC. E.g. `webserver0`, `external0`, `dns0`... etc.

(I do also sometimes pass raw NICs into zones too, to be fair.)