basil00
basil00
I am not familiar with VS2012 or its debugger (I exclusively use MinGW). The WinDivert DLL is not compiled in debug-mode so perhaps that is the problem? This is probably...
I can't think any obvious explanation. Since the problem only appears with the debugger attached, it likely requires knowledge of VS debugging which is simply beyond my expertise. The only...
> If you're using remote debugger it's possible that the debugger packets are being dropped. If the debugger uses ipv6 then this definitely will be a problem. In fact, you...
It should be possible to use the `netdump` tool to see what (if any) traffic the VS debugger is generating.
Is the `SOURCES` file even used? I thought it was redundant since switching to the VS build. Actually, I am wondering why it was not already deleted.
If `addr->IPChecksum` is zero, then it should still be possible to inject the packet with `WinDivertSendEx`. In this case, the driver is supposed to call `WinDivertHelperCalcChecksums` internally. So I am...
I can confirm this problem. It seems to only occur for "close" events. Looking at the code, it is not obvious what the cause is. The WinDivert driver considers the...
No, bitwise or other operators are not supported, and I agree this would be a nice addition to the filter language. I can keep this open as a feature request,...
It seems related to #294. Eyeballing the code, it is strange that it hangs on `WdfDeleteObject`. The `read_queue` object should be managed by WDF and not the WinDivert driver. What...
> AFAIK windivert_cleanup() will be called only when all windivert's handles reach to 0 reference. But on my machine it's still have 3 other handles (1 handle hanging, maybe?), this...