Condition on adapter status disapears

Momo · 2021-01-28 15:44

Hello,
I try to define a HomeOffice profile which must autoswitch when a VPN is activated.
For that, I use Pulse Secure adapter status:

Unfortunately, the condition is erased when Netsetman is launched, after each boot :

Is this normal? How to have a profile depending on the VPN connection?

Windows Version: 10 Enterprise, x64
Netsetman version 5.0.4

Thanks for your help
Momo

NetSetMan Support · 2021-01-28 21:54

We have not been able to reproduce the problem.
After creating the same conditions as in your screenshots, terminating the application and launching it again, they were all still there.
Can you please try and see if the same problem happens after terminating (use the tray icon menu) and launching the software, instead rebooting the system?

If yes, do you have a screen recording software that you could use to record the whole process? Maybe there is some detail that you or we are missing, which might be important to identify the issue, but cannot be identified in your screenshots. You can also record the whole process with your smartphone, upload it as a non-listed video on YT or somewhere else and share its link here.

Momo · 2021-02-02 10:57

Hello,
You're right, no need to reboot. Quitting NetSetMan is enough.
I made a little movie by recording my screen (https://youtu.be/UD0Lu3wCgBQ).

Here the scenario:
Fresh start, after booting:
- Profile "Pulse Secure VPN" has no condition
- Profile "Home" has only one condition, based on Wi-Fi

Showing that there is no possibility to add a condition based on status of adapter "Pulse Secure".

Connecting the VPN

Adding a condition based on status of the adapter "Pulse Secure"

Quitting NetSetMan

Lauching NetSetMan: Conditions based on status of the adapter "Pulse Secure" were not saved and do not appear.

I hope it will help you.

Momo

NetSetMan Support · 2021-02-02 17:34

We discussed this issue internally. The only reason why this condition could be missing after restarting NetSetMan, would be if the selected adapter has no GUID. When the conditions are loaded from the settings file, they are verified to see if they contain valid data. For the connection condition there are three values: name, GUID and status. Name and status can be seen in the UI, the GUID is stored internally, because it is just a long id and not interesting for the user.

Now, your VPN connection does not seem to be a normal NIC, because it only shows up when it is connected. There are different types of virtual network adapters used for VPN so we can't tell for sure what is happening in your case.

If it is not a normal NIC, then it cannot be used as an AutoSwitch condition anyway. The connection status condition can check if a NIC is connected or not (LAN cable attached or WiFi connection established). It is not meant to check other types of connections. If your VPN connection does not have a NIC GUID then the actual bug is probably that it shouldn't be shown there in the first place. Other types of VPNs that install a normal NIC should work though.

You can verify it yourself:
Add the condition, then open the netsetman.xml file from the program installation folder in a text editor, find your profile and the AutoSwitch section. It should look like this:

<AutoSwitch enabled="True" delay="10">
  <Condition id="3" status="1" nic="Name" guid="{11111111-2222-3333-4444-555555555555}"/>
</AutoSwitch>

In your case the guid is probably empty. If not, then copy that part and post it here.
You can add another NIC as an additional condition to see the difference.

Momo · 2021-02-02 18:21

Hello,
Indeed, the GUID is empty for this condition.
If I understand well, I don't have the possibility to have a profile depending on this kind of VPN connection.
Or is there a workaround that you could advise me.

Cheers

NetSetMan Support · 2021-02-02 21:29

Is there a trial version of this VPN that we could use to analyse it? Maybe we can add a fallback that compares the connection status based on the name if no GUID is available.

Momo · 2021-02-03 08:48

The VPN used is Pulse Secure. There is a free trial proposal at https://www.pulsesecure.net/trynow/client-download/

Have a look!

NetSetMan Support · 2021-02-03 11:14

Yes we saw that already, but this is only the client. It requires to be connected to a VPN server. Initially we assumed, that this client connects to a specific server, but it turns out you have to set up your own. Is there an access that is compatible with this client, that you could set up provide to us for a couple of days? You can send us an email (see contact page) for not sharing credentials publicly.

Momo · 2021-02-03 12:17

Sorry, I can't find you such access on my work network...
Doesn't Pulse Secure offer servers for testing on this page ?
https://www.pulsesecure.net/trynow/

But you surely already saw this page...

NetSetMan Support · 2021-02-03 12:41

This is a rather minor and unique issue. We are still open for including a workaround for it, but the time we can invest in this is very limited. We installed their client and found that it doesn't help us reproducing the situation without a compatible VPN connection. We don't see any VPN server data at the page you linked and we are not going to sign up for some service just for this cause.
If you can provide what we need to reproduce this issue, we can work on a solution.

Momo · 2021-02-03 15:00

OK, I understand.

Thanks for your help and have a nice day.

Yves

bugapa · 2021-02-13 08:03

Hi everyone, I got same issue with Cisco Anyconnect Client v4.7, but this client worked right with previous Netsetman v4.x.

NetSetMan Support · 2021-02-13 10:35

Well, same thing here: We need to be able to reproduce the issue to work on it. Provide a VPN connection temporarily, then we can look into it. You can send it to our email address (see contact page) referring to this topic.

NetSetMan Support · 2021-02-20 12:00

Thanks for providing a test account. We have improved the implementation to support this kind of connection status as well for the next version. If no GUID is available, then the connection will be recognized by its name.

NetSetMan Support

#1 2021-01-28 15:44

Condition on adapter status disapears

#2 2021-01-28 21:54

Re: Condition on adapter status disapears

#3 2021-02-02 10:57

Re: Condition on adapter status disapears

#4 2021-02-02 17:34

Re: Condition on adapter status disapears

#5 2021-02-02 18:21

Re: Condition on adapter status disapears

#6 2021-02-02 21:29

Re: Condition on adapter status disapears

#7 2021-02-03 08:48

Re: Condition on adapter status disapears

#8 2021-02-03 11:14

Re: Condition on adapter status disapears

#9 2021-02-03 12:17

Re: Condition on adapter status disapears

#10 2021-02-03 12:41

Re: Condition on adapter status disapears

#11 2021-02-03 15:00

Re: Condition on adapter status disapears

#12 2021-02-13 08:03

Re: Condition on adapter status disapears

#13 2021-02-13 10:35

Re: Condition on adapter status disapears

#14 2021-02-20 12:00

Re: Condition on adapter status disapears