basil00
basil00
Generally you want to divert as little traffic as possible to get the job done. Diverting only SYN packets is a good approach and should have minimal impact, although this...
> This problem seems to be by design and the developers don’t seem to be interested to fix it. Nothing can be done until #53 is fixed anyway.
For latency use ping, and for throughput just use any file transfer tool (`ftp`, `scp`, or even there are some `http` speed testers if you google for them) will do....
The latest WinDivert source code seems to be about ~4x faster than older versions 1.1.X and 1.2.Y, at least with my quick-and-dirty testing. This might not be quite gigabit speeds...
Yes I meant 4x throughput, although it was a very rough test. I was testing 1Gbps speed, and version 1.2.0 choked at about 170Mbps, whereas the new version managed 630Mbps...
Yes `passthru`. The test box is an old system, so might do better with more modern CPUs.
Some benchmarks for `passthru true` at gigabit speeds: ------------------------------------------------------------------ Direct: ##: 0.80 Gbps down, 0.93 Gbps up ------------------------------------------------------------------ WinDivert-1.2.0-rc (#threads) #1: 0.06 Gbps down, 0.06 Gbps up #2: 0.12 Gbps...
> There is no MSVC build for WinDivert 1.3.0? No, try to link against the MINGW version. > can confirm that 1.3.0 is faster than 1.4.0 Version 1.4.0 has a...
That might be something to look into. I also remembered that there are other complications to consider. Specifically, while deep copying sounds slow, it also has the benefit of freeing...
The latest WinDivert-1.4-dev has reverted back to deep copying rather than referencing packets. It appears this mode is actually slightly faster: #3: 0.80 Gbps down, 0.87 Gbps up So there...