[VirtualSmile]

Hi Vadim!

Thank you for responding so fast. I have already been through the sample before and actually used it for reference for my project (but in .NET).

I have solved the issue – on my end, it looks like the socket connection to the proxy was closing after a few packets, and that’s why tcp ping / connect tests were working fine (as only 1 packet). Thank you again for the help.

I have another question now, but if it’s better off being put on a new thread, let me know and I’ll make another one. Do you have any recommendations or tips on filtering by ProcessID or ProcessName? Would P/Invoke into C / C++ functions be the best way by comparing network tables? I was thinking of doing an LSP Hook via. DLL Injection to build an out-going network table but I want to avoid that due to anti cheat.

Thank you.

[VirtualSmile]

Anyone have any idea?

[VirtualSmile]

Looks like upon further inspection, the Driver is failing to load. Is it because the driver name or the way the driver is loaded has changed?

public static NdisApi Open(string driverName = "NDISRD")
        {
            if (!NdisApiDllExists())
                throw new Exception("Missing NDIS DLL");

            var driverNameBytes = Encoding.GetEncoding("ISO-8859-1").GetBytes(driverName);
            var handle = Native.NdisApi.OpenFilterDriver(driverNameBytes);
            return new NdisApi(handle, driverNameBytes);
        }

I.e the above is out of date?

[Author]

Posts