[hyde]

Perhaps PreUp, PostUp, PreDown, and PostDown scripts can be used to start/stop the SOCKS5 local proxy server in time.

PostUp => start SOCKS5 local proxy server
PreDown/PostDown => stop SOCKS5 local proxy server

• This reply was modified 3 months, 1 week ago by hyde.

[hyde]

WARP Proxy mode disallows connection when the VPN connection goes down or when WARP is turned off using the toggle switch.

This feature is exactly what I’m looking for. I don’t want the app with configurable proxy support to connect AT ALL when the VPN is down or is in a turned off state.

For example, with WARP Proxy mode enabled (from WARP app settings) but WARP turned off (using the toggle switch), when a local SOCKS5 configured Firefox browser tries to establish a connection to a website, an error saying that the socks connection has failed/timed out, is thrown. This protects the Firefox process from making connections using my real IP address.

In WinSock + WinSockUI with VPN configuration having AllowedApps set to “firefox” process, I always have to ensure that it’s connected. I’m unaware of a way of STOPPING the Firefox app/process from connecting using my real IP when the VPN configuration is in a deactivated state.

To sum it up, AllowedApps do not STOP the allowed app to make connections using my real IP when the VPN configuration is inactive or deactivated in WinSock + WinSockUI.

Setting up a local SOCKS5 proxy using an app & adding that to the AllowedApps like you suggested will have the same effect since the local SOCKS5 proxy forwarder/relay will connect using my real IP when the VPN configuration is inactive or deactivated in WinSock + WinSockUI.

[hyde]

A WireSock remnant cleaner would be nice.

[Author]

Posts