Forum Replies Created
-
Posts
-
You can’t load 32 bit driver on 64 bit system and vice versa, so you should use drivers according target architecture. However, you can use 32 bit application on 64 bit Windows, ndisapi.dll does all required conversions.
Well, we can’t be responsible for NAT32 behaviour because everything depends on how this application routes packets. If you can describe the problem with WinpkFilter itself I can try to help, but hardly likely I can help with NAT32. 🙄
When dealing with NDIS IM drivers you should sign both CAT file and driver binaries (embedded signing).
Normally all WAN connections in Windows go through the NDISWANIP (for IPv4)/NDISWANIPV6 (for IPv6) Ethernet 802.3 emulation on top of WAN miniports. So if you need to filter packets going through WAN connection you are supposed to filter on NDISWANIP (or NDISWANIPV6) network adapter listed by listadapters.
Update:
ndisrd.inf describes protocol part of NDIS IM driver and installed with hidden attribute.Hook driver is installed using the direct creation of the registry key. If you want to be able to install through command line you can create a simple console application to do that. Or alternatively you can use regini tool from the DDK along with appropriate INI file. Although I’m not sure if regeini supports removal of the registry keys.
It seems I have to use snetcfg.exe in order to make a silent install, right ?
Yes, that’s right.
In the mail I received, it is said I can send you new names for drivers and devices and information to include in the resource.What exactly can be changed, and where will I see it ? I mean, I don’t know exactly what I can custom.
It supposed that you provide the new name for driver binaries instead NDISRD (ndisrd.sys/ndisrd.vxd) used for the standard build. And any copyright/product name information you would like to include into the binaries resource.
By devices, does it mean that you can change the name of VirtNet adapter for us, or will we have to do it thank to its source code ?
We don’t customize VirtNet and you can do it yourself when needed. By the way, in order to get the source code for VirtNet please send a request to support(at)ntkernel.com along with your Plimus order ID.
Actually what exactly happens after calling SendPacketToAdapter or SendPacketToMstcp it will remove from the adapter queue or not also if i call FlushAdapterPacketQueue which packets will be clear exactly means the packets which are in queue or some other means new packets?
SendPacketToAdapter and SendPacketToMstcp don’t affect adapter packet queue, but ReadPacket does. The packet is added to the queue when it comes from the MSTCP or from the network and removed from the queue when you read it.
What exactly the flushadapterpacketqueue will do?
If there are packets queued for the particular network adapter they are removed from the queue and silently dropped.
Also at what frequency the packets will enter in queue means my packet processing is slow or what?
If the queue reaches its maximum size and causes newly coming packets to be dropped then probably your packet processing is slow. However, in reality packet queue size may vary depending of the system load.
Normally flushing packets is supposed to be used when you finish with packet processing and want to deallocate resources.
WinpkFilter orders are processed by Plimus e-commerce provider (http://www.plimus.com). I think it makes sense for you to contact their support regarding the bills you need from them.
Hook driver won’t be displayed in network connection properties. However, it worth to mention that NDIS IM driver also can be hidden from the network connection properties if needed.
Manual WinpkFilter driver installation is covered by my post above. As for possible network configuration problems it is not that easy to advise as I have no idea what may have happen. Most probably there was unsuccessful instillation of the driver which has left some remnants in the system registry and does not allow to install the driver once again. You can check if the registry key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesndisrd exists on the target system.
If snetcfg fails then may be this is something wrong with system network configuration. I would recommend to try manual installation and see if it works first.
If i want to install the driver through snetcfg there we are specifying the names like ndisrd.inf and ndisrd_m.inf these relate to which driver exactly like IM driver or hook driver.
NDIS IM
Also one more question if i install hook driver it will not display in Network properties?
No
These drivers are different by their architecture and only one of them can be installed, otherwise you meet a conflict conditions (both drivers share the same name).
It does not really matters which of the drivers is to use for XP, NDIS hook is easier to install but requires system reboot. While NDIS IM is more complex to install but in most cases reboot is not needed.
Have you had enough privilege to install the driver? Also can you try to install NDIS IM driver manually for the case if something went wrong with snetcfg utility:
Prepare a floppy disk (or installation directory) that contains these files: ndisrd.inf, ndisrd_m.inf and ndisrd.sys. On the desktop, right-click the My Network Places icon and choose Properties. Right-click on the relevant Local Area Connection icon and choose Properties. Click Install, then Service, then Add, then Have Disk. Browse to the drive/directory containing the files listed above. Click OK. This should show “WinpkFilter Driver” in a list of Network Services. Highlight this and click OK. This should install the WinpkFilter driver. Click OK or Yes each time the system prompts with a warning regarding installation of unsigned files. This is necessary because binaries generated via the DDK build environment are not signed. Two .INF files are needed rather than one because WinpkFilter is installed both as a protocol and a miniport.
This is not a usual case as WinpkFilter does not have any known issues with Windows XP SP3, most probably something has prevented driver from being installed.
