aru: there's an issue with that post that a coworker ran into last week. If you name the vnic "tailscale0" things will break as the software is explicitly checking for that nic name

I will publish an edit to that post sometime this week

unless of course you're hitting a different issue

papertigers: now that I'm thinking back, I had the interface named differently, but later settled on naming the interfaces after the zone they belong to, so it became tailscale0

that's an unexpected trap

while I'm at it, any suggestions on a vnic naming scheme?

aru I ended up doing <zonename><integer> because a zone might have multiple vnics.

so something like router zone has router0 and router1 for LAN and VLAN

That's what I did until I hit the issue with tailscale

yeah, I ended up naming my zone "tails" and ended up with tails0

I think smartos has some patches that let dladm have multiple vnic's named the same thing. iirc you end up with a bunch of vnic's named net0 on smartos but they have distinct mac addr's and map to distinct zones

Some of those more zone aware dladm changes would be nice to have upstream

wait, the default builds of illumos-gate is not with debug symbols ? o.O

DEBUG builds add a lot of other overhead.

non-DEBUG builds include CTF debug information