Feature Request: Allow tun0 as a valid network interface source #191

Open
Alives opened this Issue Nov 5, 2012 · 5 comments

3 participants

@Alives

So I can then trigger actions based on VPN connection or not.

Thanks,
Elliott

@dustinrue
Owner

If you create the rule while the VPN is connected is tun0 then available? That interface is dynamically created as is the list that CP has available during rule create.

@Alives

No. I got on VPN (tun0 now exists), and checked and it only showed en0 still. I then restarted the app and checked again, but no tun0.

tun0 doesn't exist unless the VPN is up though. Not sure if that matters.

@dustinrue
Owner

Yes, tun0 needs to visible on the system before CP can see it.

@Alives

It's only visible when it is active. I restarted CP while it was active and CP didn't see it then either though.

@lassebirnbaum

Create a small script and use this as evidence source. It works fine for me using Cisco Anyconnect VPN client.

If utun0 is UP the script evidence is true

#!/bin/bash
ifconfig utun0 inet|grep UP 2>/dev/null >/dev/null
exit $?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment