[Bug Report]: Managed TrueNAS bind interfaces not including tailscale0 interface after app install

[cybersader]

App Name

Tailscale

Version (TrueNAS Catalog App Version)

1.3.26

App Issue

TrueNAS Version: 25.10.1

Problem:
The SSH service bind interfaces dropdown only shows "managed" interfaces from midclt call interface.query. Dynamically-created interfaces like tailscale0 (from Tailscale container) don't appear, even though they exist at kernel level.

Steps to Reproduce:

1. Install Tailscale app with Host Network enabled, Userspace disabled
2. Confirm tailscale0 exists: ip link show | grep tailscale
3. Go to System → Services → SSH → Edit → Bind Interfaces (or Network tab)
4. tailscale0 is not listed

Expected Behavior:
Per https://tailscale.com/kb/1483/truenas, users should be able to bind SSH to tailscale0 for secure remote access.

Actual Behavior:

• ip link show shows tailscale0 ✓
• midclt call interface.query does NOT show tailscale0 ✗
• SSH bind dropdown doesn't include tailscale0 ✗
• CLI workaround fails: midclt call ssh.update '{"bindiface": ["tailscale0"]}' returns validation error

Workaround:
None currently. Users cannot bind native SSH to Tailscale interface.

App Logs

[cybersader]

https://www.truenas.com/community/threads/tailscale-doesnt-create-the-network-adapter.114122/

"We don't expose the tailscale app interface (any app network interface in that respect) to the webUI."

^ This suggests that the Tailscale article is lying, but it seems some people have been able to do it, so I'm left confused