Vadim Smirnov

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 1,478 total)
  • Author
    Posts
  • in reply to: local devices become unreacheable after some time #13970
    Vadim Smirnov
    Keymaster

      Great! Thank you for the update! 👍

      in reply to: amneziawg support #13963
      Vadim Smirnov
      Keymaster

        I’m excited to announce that AmneziaWG support is now available in WireSock Secure Connect v2.1.4!

        🔗 Download WireSock Secure Connect

        in reply to: [Wiresock] Bugs and Feature Requests #13959
        Vadim Smirnov
        Keymaster

          Thank you for your message! Let me clarify a few points:

          Interface Name in Commands
          Instead of using the placeholder %i, you can safely rely on the WIRESOCK_TUNNEL_NAME environment variable in your scripts and commands. This variable provides the actual Wiresock tunnel name at runtime, ensuring proper command execution.

          Table = off Setting
          Currently, Table = off is not supported by Wiresock. Could you let us know where you found this setting mentioned in the Wiresock documentation? If it’s listed somewhere, we’d like to correct that reference to prevent confusion.

          If you have any additional questions or need further assistance, feel free to let me know!

          in reply to: WinPkFilter 3.6 API documentation #13953
          Vadim Smirnov
          Keymaster

            I apologize for not being able to update the documentation sooner—these past months have been incredibly busy. The key difference between versions 3.4 and 3.6 lies in the subset of extensions to the Static Filters API. These include the following new functions:

            • AddStaticFilterFront
            • AddStaticFilterBack
            • InsertStaticFilter
            • RemoveStaticFilter
            • ResetPacketFilterTable
            • EnablePacketFilterCache
            • DisablePacketFilterCache
            • EnablePacketFragmentCache
            • DisablePacketFragmentCache

            All these functions are documented inline in ndisapi.cpp. I will update the online documentation as soon as I have time.

            in reply to: WireSock DNS is going over VPN (bug?) #13949
            Vadim Smirnov
            Keymaster

              All DNS requests on Windows are resolved within the DNSCACHE process, making it impossible to identify the originating application.

              in reply to: Winpkflt Rebind #13947
              Vadim Smirnov
              Keymaster

                Yes, that’s exactly what I mean. This technique is implemented in the WireSock VPN Client’s Transparent mode to ensure that packets sent by the TCP stack fit within 1420 bytes.

                in reply to: Winpkflt Rebind #13945
                Vadim Smirnov
                Keymaster

                  I would apply MSS clamping when relaying the TCP SYN packet from the Ethernet to the WireGuard interface. If issues persist despite the MSS clamping, I recommend recording the processed traffic (see the capture example) and analyzing it in Wireshark

                  in reply to: Connected to tunnel, but no traffic works #13942
                  Vadim Smirnov
                  Keymaster

                    Logs and PCAP files would be helpful for investigating your issue.

                    in reply to: Winpkflt Rebind #13941
                    Vadim Smirnov
                    Keymaster

                      The Ethernet connection likely has a larger MTU than the WireGuard adapter. To address this discrepancy, you need to clamp the Maximum Segment Size (MSS) for TCP connections.

                      in reply to: Can’t connect to WireGuard server #13938
                      Vadim Smirnov
                      Keymaster

                        I don’t see any handshake responses in the log. WireSock sends multiple handshake packets to the server, but there’s no response. This behavior is typical when the WireGuard protocol is blocked. You might want to try using the SOCKS5 configuration option—it could resolve the issue.

                        Vadim Smirnov
                        Keymaster

                          Hello Olivier,

                          Thank you for your message and for considering WinpkFilter as a solution for your network monitoring module. I’m glad to hear it aligns well with your requirements, and I appreciate your kind words about my responsiveness.

                          For your trial, you are welcome to use the publicly available version of WinpkFilter. However, please keep in mind that I don’t recommend using this build in a production environment on a permanent basis, as it may lead to potential conflicts.

                          Should you need any further assistance or clarification, feel free to reach out.

                          Best Regards,
                          Vadim

                          in reply to: Query on Filtering Capabilities in Windows Packet Filter API #13934
                          Vadim Smirnov
                          Keymaster

                            Olivier,

                            Yes, you can use a single instance of CNdisApi. Please refer to the dual_packet_filter class, which demonstrates how two threads can operate across two network interfaces.

                            Additionally, you can assume the timestamp when the Read call occurs, with some level of precision. For higher accuracy, minor driver modifications would be needed; for example, the reserved bytes in INTERMEDIATE_BUFFER could be used to store more precise timestamps.

                            in reply to: Ошибка 0xc0000005 #13929
                            Vadim Smirnov
                            Keymaster

                              С 1.4.7 есть проблема на Windows 7. Она собрана с версией компилятора Rust, который не поддерживает Windows 7. Используйте 1.4.5.

                              in reply to: Privacy[Приватность] #13927
                              Vadim Smirnov
                              Keymaster

                                Ни WireSock ни WireSockUI не собирают, не хранят и никуда не отсылают никакой телеметрии. Но, разумеется, мы не можем гарантировать, что этого не делает тот сервис который вам предоставляет Wireguard сервер. Поэтому я бы рекомендовал использовать свой собственный VPS.

                                in reply to: Kernel Logging #13925
                                Vadim Smirnov
                                Keymaster

                                  The driver shares a substantial amount of code across various Windows versions, so currently, the only available tracing method is through DbgPrint, which is enabled only in debug builds. If you’re specifically asking about ETW traces, this type of logging hasn’t been implemented yet. However, it can certainly be added for driver builds on Windows 7 and later versions if needed.

                                Viewing 15 posts - 1 through 15 (of 1,478 total)