[Vadim Smirnov]

Понимаю… Постараюсь найти время…

[Vadim Smirnov]

Hello,

Unfortunately, only one active tunnel is currently supported. Adding more configs/tunnels is not that hard, and the idea is fascinating. I’ll add this feature request to the to-do list. Unfortunately, I don’t have much spare time lately, so I can’t say when I’ll be able to my hands on this.

[Vadim Smirnov]

As far as I can see, Firefox works great over VPN, while IE slows down. And I suspect that the problem may be related to DNS. Since you specified DNS in the Wireguard config file, all DNS requests (not only Firefox, but also IE) go to this server. Try removing DNS from the config and/or changing it to something like 8.8.8.8 to see if there is a difference.

One more question, did you run the wiresock client as administrator?

[Vadim Smirnov]

I think the problem you are having is related to the MTU setting in your config file. Try reducing the MTU (for example, from the default 1420 to 1412 or even 1280) and see if there is a difference.

Unlike the standard WireGuard client, WireSock does not support fragmented UDP frames and download performance may be degraded due to packet loss.

[Vadim Smirnov]

Hmm, I’m running Wiresock in a similar setup, although Chrome uses a Wireguard tunnel and Firefox connects directly, and I’ve never noticed much slowdown. Of course, depending on the distance to your Wireguard server (and associated network latency), when you’re browsing the tunnel, websites usually don’t respond as quickly as they would with a direct connection, but that’s expected behavior.

I would first try testing another Wireguard server, preferably one that you set up yourself and has enough CPU and network resources. Otherwise, other VPN clients may affect the performance of your tunnel in unpredictable ways, and a clean test will not be possible.

Do i have to add any tag in the setupcommand for using multiple cores of the processor?

The Wiresock client uses 4 worker threads (4 cores) to process packets, this design seems quite scalable.

 

[Vadim Smirnov]

Hi, the Wi-Fi hotspot feature requires a special mode to be activated on the Wi-Fi adapter, and this may affect the performance of your Internet access over Wi-Fi network. So, a couple of questions:

1. Is the Wi-Fi adapter your only internet connection?
2. Are you experiencing Wi-Fi internet degradation without using Wiresock?

 

[Vadim Smirnov]

Можно побольше информации? Если речь про Wiresock VPN Gateway, то надо переконфигурировать его из режима proxy в NAT. Proxy поддерживает только TCP и UDP.

[Vadim Smirnov]

Hi, yes you are right and in fact I already have a tray icon project. I will finish the first simple version as soon as I have spare time. Hopefully, next weekend.

[Vadim Smirnov]

Hi,

If this is the exact command line

wiresock-client.exe run -config C:\Program Files\WireSock VPN Client\bin\config.conf -log-level all -lac,

then you must either add quotes (path contains spaces) or remove the full path (wiresock checks the \bin folder for a config file):

wiresock-client.exe run -config "C:\Program Files\WireSock VPN Client\bin\config.conf" -log-level all -lac

OR

wiresock-client.exe run -config config.conf -log-level all -lac

Hope it helps!

 

[Vadim Smirnov]

Тут или путь к wireguard.exe (обычно это C:\Program Files\WireGuard) не был добавлен в PATH (wireguard-installer.exe его должен был добавить) или забыли консоль перезапустить после установки wireguard-installer.exe. Если в PATH его нет, то добавьте вручную и перезапустите powershell.

[Vadim Smirnov]

Если виснет при неработающем WireSock VPN Gateway, значит дело не в нем, а в WireGuard Windows Client v0.5.3 и/или, что менее вероятно, его совместимости с Windows 7 (OS уже старенькая, могли не протестировать).

WireGuard Windows Client v0.3.16 год назад прекрасно справлялся с множественными тоннелями, но, если не ошибаюсь, это еще была версия построенная на основе wireguard-go и WinTun…

[Vadim Smirnov]

Добрый день!

Любопытно, дело в том, что похоже, что именно такую конфигурацию я строил тут. Боюсь что-то могли поломать в самом WireGuard Windows Client, к сожалению переход на модуль ядра не добавил ему стабильности.

Для начала попробуйте остановить службу WireSock VPN Gateway, в сущности это всего лишь NAT/PROXY для клиентов подключающихся к  серверному тоннелю. Если при неактивной службе подвисание с двумя тоннелями повторится, то тут надо разбираться, что поломали в WireGuard клиенте и возможно откатится на старую версию.

В противном случае для начала попробуйте изменить режим работы WireSock VPN Gateway с PROXY на NAT или наоборот. Эти режимы довольно значительно отличаются, возможно будет какая-то разница в поведении.

[Vadim Smirnov]

Hmm, I suspect that this termination may be due to the panic of the Boringtun library on some particular network packet. Could you collect and share the pcap files by running the Wiresock with -log-level all until the application unexpectedly exits?

[Vadim Smirnov]

Yes, if you add “powershell” to AllowedApps then this request will be tunneled.

[Vadim Smirnov]

The Windows API only allows you to get the process context for the TCP and UDP protocols. So, ping.exe sending ICMP packets cannot be resolved and therefore not tunneled.

The simplest alternative would probably be a simple UDP based pinger, which can be easily implemented in Golang.

[Author]

Posts