[valera5505]

Wiresock supports split tunneling in the form of allowed apps but is it possible to do it otherwise — route all traffic through the tunnel except for certain apps?

[Vadim Smirnov]

In the current version, this is not possible, but I think it makes sense to add such an opportunity.

[valera5505]

That’d be great! Any idea on when can we expect this feature?

[Vadim Smirnov]

There are three small features that I would like to add to the next version. I hope to be ready in a week or two, depending on whether I have enough spare time.

[Vadim Smirnov]

The requested extended parameter to exclude applications (DisallowedApps) was added in v.1.1.16. Please give it a try.

[valera5505]

Seems to be working good, thank you for the quick update!

[Vadim Smirnov]

Thanks for testing. I’ve slightly improved the logic. Please update to v.1.1.18.

[valera5505]

I noticed very strange behavior where I have 4 apps but some of them are still going through the tunnel. But exactly which ones will be ignored is dependent on their order.

For example, with the following setting:

DisallowedApps = VMware,obs64,DDNet,chrome

I have:

2022-04-04 21:25:40 [FILTER]: Skipping VMware NAT Service : TCP : 192.168.0.101:62570 -> 213.180.204.63:443

2022-04-04 21:25:59 [FILTER]: obs64.exe : TCP : 192.168.0.101:62610 -> 149.56.72.190:443

2022-04-04 21:26:10 [FILTER]: DDNet.exe : TCP : 192.168.0.101:62647 -> 188.114.96.0:443

2022-04-04 21:26:25 [FILTER]: Skipping chrome.exe : UDP : 192.168.0.101:49935 -> 142.251.36.35:443

Yet with this order:

DisallowedApps = DDNet,obs64,VMware,chrome

I have:

2022-04-04 21:28:19 [FILTER]: VMware NAT Service : TCP : 192.168.0.101:65232 -> 139.45.192.1:443

2022-04-04 21:28:48 [FILTER]: obs64.exe : TCP : 192.168.0.101:57399 -> 149.56.72.190:443

2022-04-04 21:29:05 [FILTER]: Skipping DDNet.exe : TCP : 192.168.0.101:64433 -> 188.114.96.0:443

2022-04-04 21:29:21 [FILTER]: Skipping chrome.exe : TCP : 192.168.0.101:64458 -> 45.57.69.146:443

It seems like only the first and the last apps are actually ignored and the rest will go through the tunnel regardless of their presence in the config.

[Vadim Smirnov]

Thanks for pointing this out. I’ve resolved the issue in v.1.2.5, please give it a try.

[Author]

Posts