TeamViewer – to be or not to be
By now, you should have a configured Wireguard server and at least one client configuration that looks something like this:
[Interface]
PrivateKey = AD9GaupPbRlfjPTfhLm1/lm5qtgwvFcB1rGpKOZkXXE=
Address = 10.66.66.2/32, fd42:42:42::2/128
DNS = 94.140.14.14, 94.140.15.15
MTU = 1420
[Peer]
PublicKey = tRb3/FxzJBhinaVPY/tyoX40PS7EY1mmzFyrL/dAnwY=
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = ora.sshvpn.me:51820
-
Download and install Wiresock VPN Client. All quality claims can be sent directly to me. I wrote it myself, I use it all the time.
-
Adding to the client configuration file
AllowedApps = teamviewer
. The configuration file can be put next to the folder with the Wiresock VPN Client binaries (C:\Program Files\WireSock VPN Client\bin
) so that you do not need to prescribe the full path to it.
[Interface]
PrivateKey = AD9GaupPbRlfjPTfhLm1/lm5qtgwvFcB1rGpKOZkXXE=
Address = 10.66.66.2/32, fd42:42:42::2/128
DNS = 94.140.14.14, 94.140.15.15
MTU = 1420
[Peer]
PublicKey = tRb3/FxzJBhinaVPY/tyoX40PS7EY1mmzFyrL/dAnwY=
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = ora.sshvpn.me:51820
AllowedApps = teamviewer
-
Install Wiresock VPN Client as a service and run it. If you have a configuration file in the service folder, then as
config_full_path
_name is sufficient to use only the name of the client configuration file. Runcmd
as Administrator and do the following:
wiresock-client.exe install -start-type 2 -config [config_full_path_name] -log-level none
sc start wiresock-client-service
Now TeamViewer, and only he, will walk through the Wireguard tunnel. I still usually add one of the browsers separated by commas. If there are any problems, then stop the service and run wiresock-client.exe
in application mode with a log (see below). Usually it is immediately clear what went wrong, but if not, then write – I will help.
sc stop wiresock-client-service
wiresock-client.exe run -config [config_full_path_name] -log-level all