Kotik

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Failed to find a matching WinpkFilter interface. #13526
    Kotik
    Participant

      I spoke too soon 🙂

      I still have to disable the Kerio Control Filter from the WireSock virtual adapter after the reboot and use the Virtual Adapter option, otherwise outgoing traffic is working but incoming is not.

      It seems to be working fine tho with this combination of settings and considering that TunSafe is slow and old i am pleased.

      in reply to: Failed to find a matching WinpkFilter interface. #13525
      Kotik
      Participant

        I did some further investigations.

        I came up with some very interesting results:

        On a VM with the Kerio Control installed, a restart is required after installing WireSock and then everything is working (i do not even need to disable the Kerio Filter in the adapter options).

        On a VM without Kerio Control, a restart is not required after installing WireSock.

        So essentially my issue is resolved and i am sorry for not trying a simple restart prior to posting, but i was used to WireSock NOT needing a system restart post installation on all my other machines which obviously did not have Kerio Control installed.

        Thank you for your time and work.

        in reply to: Failed to find a matching WinpkFilter interface. #13524
        Kotik
        Participant

          Sure here are the steps to reproduce:

          1. Install Windows 8.1 Pro on a VM

          2. Download and install Kerio Control with Windows support.

          eu.download.kerio.com/dwn/control/control-7.4.2-5136/kerio-control-7.4.2-5136-win64.exe

          (This is the latest version that supported the Windows platform)

          3. Install Kerio with their inbuilt VPN disabled, everything else should be left at defaults. (there is no need to configure anything since we only need Kerio to install its own network filters)

          4. Download WireSock and WireSockUI and use any wireguard .conf file.

          I just re-did this on the fly and got exactly the same error.

          Let me know if i can be of more help.

        Viewing 3 posts - 1 through 3 (of 3 total)