Tun interface visibility

Got a problem with Viscosity or need help? Ask here!

srlive

Posts: 1
Joined: Wed Dec 14, 2022 5:54 am

Post by srlive » Wed Dec 14, 2022 6:06 am
Hi,

I'm using viscosity on Mac OS 12.6 (Mac M1 Max). I'm facing a change of behavior with one of my app and I'm trying to figure out if there is a way to recover it.

I'm connecting to a tap openvpn. Also, one of my applications requires me to select the network interface I want it to work with. (Dante Controller for those wondering)

Before upgrading (using Mac OS 10.15), I had the ability to select the tap interface and connect it directly to my remote network completely seamlessly. Now, I cannot see this interface anymore (en14 if ifconfig is right). Is there some kind of security policy preventing other app to connect to a vpn interface? (I have not problem seeing other net interface). Or maybe something I don't know about how network interface are handled?

Thanks for your help,
Simon

James

User avatar
Posts: 2220
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Thu Dec 15, 2022 9:47 pm
Hi Simon,

Viscosity's network interfaces are virtual interfaces: they do not show up in system APIs designed to list all physical network interfaces on the system (such as "SCNetworkInterfaceCopyAll"). It's likely the software you are using is using such APIs, and so Viscosity's network interfaces are not appearing in the list.

Viscosity's network interfaces have always been virtual. My guess is why it used to work in the past is the software you're using had a special exemption for "tap" interfaces. Viscosity no longer uses the legacy tap kext driver (as macOS 11 deprecated kernel extensions). If this is the case, you may be able to ask the developers of the software to modify their exemption so it also identifies Viscosity's modern virtual network interfaces.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts Page 1 of 1