Vadim Smirnov

Forum Replies Created

Viewing 15 posts - 241 through 255 (of 1,507 total)
  • Author
    Posts
  • in reply to: Split Tunneling in WireSock vpn client #13183
    Vadim Smirnov
    Keymaster

      The feasibility of this depends on the application in question. If you’re able to rename the second instance or relocate it to a different path (such as a portable edition), you can still use the “AllowedApps” option by specifying the full pathname. For example, you could set “AllowedApps = C:\Program Files\Mozilla Firefox\firefox.exe”.

      However, if the only difference between your application instances is the process ID, unfortunately, this feature is not supported. While it’s technically feasible to implement, I’m currently unsure of how to do so in a user-friendly manner.

      in reply to: Split Tunneling in WireSock vpn client #13180
      Vadim Smirnov
      Keymaster

        The current Wiresock VPN Client does not support local Wireguard endpoints in the configuration file, rendering the method of redirecting WireGuard through the local proxy, as described in the provided link, unfeasible. I’m contemplating the inclusion of local endpoints as a feature, however, this isn’t necessary for your specific situation.

        You can simply specify the applications you want to forward over the Wireguard tunnel under the “AllowedApps” configuration option. For instance, setting “AllowedApps = firefox” will result in only the Firefox browser’s traffic being forwarded over the WireGuard tunnel.

        If you prefer to have your browser explicitly configured to use the specified local proxy, you can install a lightweight SOCKS5 proxy and include its name in the “AllowedApps”. Consequently, all outgoing traffic from this proxy will be directed through Wiresock over the WireGuard tunnel. This setup will also apply to all traffic from the proxy’s clients.

        in reply to: cant install wiresock vpn client #13146
        Vadim Smirnov
        Keymaster

          В логах anti-spam’а я не нашел ничего релевантного, затрудняюсь сказать, что ему не понравилось. Но без него тоже никак, вручную текущие объёмы спама модерировать невозможно. Можете отправить мне напрямую на [email protected].

          Установить драйвер получилось или опять ACCESS_DENIED? Такое ощущение, что что-то в системе блокирует установку определенного типа драйверов…

          in reply to: cant install wiresock vpn client #13142
          Vadim Smirnov
          Keymaster

            Ясно, конcоль была запущена под админом? А если так как на скриншоте попробовать?

            Manual installation of ndiswgc driver

            in reply to: cant install wiresock vpn client #13139
            Vadim Smirnov
            Keymaster

              Может в “роллбеке” msi, при неудачной инсталляции указывать именно удаление через sc? Потому что через “‘C:\WINDOWS\system32\netcfg.exe” -v -u nt_ndisrd’ не отработало и в системе остался не запускающийся драйвер:

              Да, пожалуй имеет смысл. Но сперва надо разобраться с ACCESS_DENIED.

              Если не затруднит, скачайте ndiswgc и попробуйте установить его вручную, либо используя netcfg:
              netcfg.exe -v -l ndiswgc_lwf.inf -c s -i nt_ndiswgc

              Либо через свойства сетевого соединения, Install->Service->Have a Disk.

              Если при установке в ручную ошибки не будет, то дело в MSI скрипте, будем разбираться что с ним не так.

              in reply to: The process cannot access the file #13134
              Vadim Smirnov
              Keymaster

                DNS reserves a significant range of ports, the specifics of which you can explore here: DNS Port Allocation. It would be advisable to select a different range when assigning a port for WireGuard.

                in reply to: Recommended SOCKS5 Proxy setup? #13131
                Vadim Smirnov
                Keymaster

                  The purpose of this DPI protection is to mask the WireGuard handshake from the DPI system that sits between the WireGuard peers.

                  in reply to: The process cannot access the file #13130
                  Vadim Smirnov
                  Keymaster

                    The log says: Could not bind socket to [::]:59539 (0xc0000043)

                    From the error messages provided, it seems like there is a conflict on port 59539, which WireSock is trying to bind to. The error message “The process cannot access the file because it is being used by another process” often means that the port is being used by another application or service on the system.

                    I would recommend trying to identify the application using the port. Use the netstat command to identify which application is currently using the port 59539. Open the Command Prompt and type netstat -aon | findstr 59539. The last column of the output will give you the process ID (PID) of the application using the port. You can then use the Task Manager to find the application associated with this PID.

                    in reply to: Recommended SOCKS5 Proxy setup? #13126
                    Vadim Smirnov
                    Keymaster

                      I’m not entirely sure if I have accurately comprehended your question. The premise seems to be that when tunneling the Wireguard handshake via SOCKS5, Deep Packet Inspection (DPI) will observe the handshake and handshake response packets with an additional SOCKS5 header appended. This extra layer increases the complexity of accurately identifying the nature of these packets.

                      in reply to: NAT has failed to start #13125
                      Vadim Smirnov
                      Keymaster

                        Could you please start the service with verbose logging enabled -log-level all and share the log?

                        in reply to: PostUp and PostDown #13118
                        Vadim Smirnov
                        Keymaster

                          Hmm, it might be beneficial for you to consider utilizing the command line version of the WireSock VPN Client. This allows you the flexibility to start or stop the client either as a standalone application or as a service, directly from a PowerShell script.

                          in reply to: Recommended SOCKS5 Proxy setup? #13117
                          Vadim Smirnov
                          Keymaster

                            Yes, you’re absolutely correct. The SOCKS5 proxy should indeed be remote, preferably residing on the same machine as the VPN server. This configuration ensures it is beyond the DPI (Deep Packet Inspection), thus facilitating pass-through.

                            in reply to: WiresockUI freezes once or twice a day #13116
                            Vadim Smirnov
                            Keymaster

                              Apologies for the oversight in our documentation update. The new log location is C:\ProgramData\NT KERNEL\WireSock VPN Client. PCAP files are saved either to the working directory or within Windows\System32 when operating as a service.

                              in reply to: WiresockUI freezes once or twice a day #13102
                              Vadim Smirnov
                              Keymaster

                                Thank you for your diligent efforts in troubleshooting the issue. I greatly appreciate your time and your willingness to try out different steps to diagnose the problem.

                                In order to assist us with a deeper analysis, I recommend starting the console version of the Wiresock client. Please use the “-log-level all” argument to collect detailed logs and capture network traffic during the times when the connection drops, which could shed light on what may be causing these disruptions.

                                Thank you once again for your cooperation.

                                in reply to: Recommended SOCKS5 Proxy setup? #13101
                                Vadim Smirnov
                                Keymaster

                                  Wiresock VPN Client implements this feature via additional parameters:

                                  • Socks5Proxy – specifies SOCKS5 proxy endpoint, e.g. Socks5Proxy = socks5.sshvpn.me:1080 or Socks5Proxy = 13.134.12.31:1080
                                  • Socks5ProxyUsername – specifies SOCKS5 username (optional)
                                  • Socks5ProxyPassword – specifies SOCKS5 password (optional)

                                  Wiresock operates by establishing a connection to the indicated SOCKS5 proxy. This involves associating a UDP endpoint and transmitting handshake packets through the SOCKS5 UDP tunnel. The handshake response emerges from the same tunnel. However, all subsequent data traffic is routed directly to the intended WireGuard endpoint.

                                  Although the methodology is quite straightforward, it adds a layer of complexity to the WireGuard handshake and response process, making it more challenging to detect and subsequently block the tunnel.

                                Viewing 15 posts - 241 through 255 (of 1,507 total)