@SerpentFly wrote:
Packet is matched against the filters list and first matching filter action is applied. So there is probably something wrong with your first filter.
Yeah, just came here to say that i found out what was wrong a few minutes ago. In short, i was being stupid.
I was using the “block ntkernel.com” filter as an example, and i changed its filter action to pass.
That filter was set up to look at the destination address and destination ports.
I had to set up another filter to catch source address and source ports, that solved the issue.
So my new filter setup, for anyone interested in doing the same, is:
filter 1 – pass tcp ipv4 packets with destination address of 192.168.7.22:80
filter 2 – pass tcp ipv4 packets with source address of 192.168.7.22:80
filter 3 – send all tcp ipv4 packets to user mode
filter 4 – pass all packets