Microsoft developed TDI (Transport Driver Interface)Â for the purpose of giving additional functionalityÂ combined withÂ flexibility (compared to the existing interfaces). Windows 2000 (and later versions) has the transport providers directly interface with the TDI (Transport Driver Interface).Â This allows the TDI (Transport Driver Interface) to offer a more consistent interface with the (NTP)Â network transport protocols.
Have you been able to view Barak’s free Winsock LSP video?Â You can see this video on the same page as the free LSP guide – or you can view the video on YouTube.Â The LSP resource page here on Komodia is also a wealth of information.Â Are you interested in a free TDI firewall source code?Â Then please follow this link.Â Â How about free help winsock functions or any number of other great information?Â Komodia is the place to be for all LSP information.
TDI FilterÂ is sometimes prefered because the thought that there’s no conflicts within this technology, but the opposite is true, it can conflict, the reason that you don’t see many conflicts is because you know in advance not to install two FW products on your machine, and why? because those two can conflict.
NDIS FilterÂ is used to perform packet filtering, modification and inspection, unlike other technologies like LSP and TDI which operate on streams.
NDIS Filter is actually a NDIS IM driver which receives packets (to send or receive), can perform processing on them and then send them to the next layer or drop them, that’s why NDIS IM drivers are used for: Firewalls, corporate firewalls, custom network solutions and more.
When stream operations is requires, NDIS IM is sometimes a bad choice because it imposes additional work to convert packets to streams, which can be avoided if using TDI or LSP.