[alex_s]

@SerpentFly wrote:

Do you mean to filter OpenVPN virtual adapter?

I do 🙂

[alex_s]

@SerpentFly wrote:

If fsndis5.sys would not take the new modified (LNM driver) handlers from TCPIP.SYS dispatcher table it could just exclude LNM driver from the stack and keep system stable. However, in general the re-patching approach in F-Secure driver is not compatible with any other TDI filter based on patching the dispatcher table.

Thanks for this comprehensive report. All in all this is a good news in way 🙂

[alex_s]

@SerpentFly wrote:

Does winpkt implement SPI and DPI in any way ?

Stateful Packet Inspection? WinpkFilter is a library which takes packet from kernel level and delivers to user mode where you can implement SPI, DPI or whatever you want. It does not implement packet inspection itself.

It’s OK. But what may happen in case a packet is twisted in a way ? For example wrong packet length or something like that. Can a twisted packet cause BSOD, for example ? (It is rather DPI than SPI I think).

[alex_s]

@Samael6 wrote:

I have found a solution.
No more help needed

VolumeDeviceToDosName ?

[alex_s]

@SerpentFly wrote:

Do you run WinpkFilter inside Virtual PC (guest) system? It should work fine in this environment unless you also have installed some software which conflicts with WinpkFilter drivers.

What ListAdapters does show you? Also could you specify host and guest operating systems along with version of Virtual PC?

At the moment I can only say that host system is XP Home and guest is XP Prof.
I made clean install of XP Prof and installed there our product (based on pktfilter).
No adapters were cought 🙁
That is to say the same procedure runs fine under VMWare.

Accurate adapters list I will post later, as long as VP is installed at my home
computer and now I’m in the office 🙂

[Author]

Posts