15:26:42 <papertigers> 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
15:27:10 <papertigers> I will publish an edit to that post sometime this week
15:41:14 <papertigers> unless of course you're hitting a different issue
16:40:15 <aru> 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
16:41:55 <aru> that's an unexpected trap
16:49:38 <aru> while I'm at it, any suggestions on a vnic naming scheme?
18:49:50 <antranigv> aru I ended up doing <zonename><integer> because a zone might have multiple vnics.
18:50:12 <antranigv> so something like router zone has router0 and router1 for LAN and VLAN
19:02:00 <aru> That's what I did until I hit the issue with tailscale
22:22:42 <papertigers> yeah, I ended up naming my zone "tails" and ended up with tails0
22:23:48 <papertigers> 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
22:24:33 <papertigers> Some of those more zone aware dladm changes would be nice to have upstream
23:48:14 <antranigv> wait, the default builds of illumos-gate is not with debug symbols ? o.O
23:54:14 <sommerfeld> DEBUG builds add a lot of other overhead.
23:54:57 <sommerfeld> non-DEBUG builds include CTF debug information