ndis

NDIS 6.x ethernet bridge driver

南笙酒味 提交于 2019-12-12 03:52:11
问题 I was wondering what would be the best choice and way to build an ethernet bridge using NDIS 6.x. Where should I start and which one should I use for this, Miniport, IM, protocol or filter driver? Tried to customize the protocol driver sample available in WDK and successfully got attached to the ethernet adapters. What next? Any help is much appreciated. Using Windows 7x64 回答1: Let's look at the NDIS driver types that are available: miniports, lightweight filters, and protocols. An NDIS

How to determine whether a 802.11 raw packet has FCS (4bytes) in a NDIS 6 filter driver?

时光毁灭记忆、已成空白 提交于 2019-12-12 01:56:22
问题 I have a NDIS 6 filter driver working on Windows Vista and later systems. I have bound it below NativeWiFi Filter so I can see 802.11 packets instead of fake Ethernet packets . And I have set the NDIS_PACKET_TYPE_802_11_RAW_DATA and NDIS_PACKET_TYPE_802_11_RAW_MGMT in the packet filter based on: https://msdn.microsoft.com/en-us/library/windows/hardware/ff554833(v=vs.85).aspx, so I can receive the Raw 802.11 Packets indications from the miniport. Then I switched my wireless adapter to Monitor

NDIS filter driver's FilterAttach routine isn't called under Windows 8

烈酒焚心 提交于 2019-12-12 01:42:39
问题 everybody. I have ported the famous packet capture software WinPcap from the NDIS 5 protocol to an NDIS 6 LWF. Everything is OK under Win7. However, the FilterAttach routine is never called under Win8. I found NdisFRegisterFilterDriver invoke in DriverEntry returns NDIS_STATUS_SUCCESS, this is so strange. Can anyone help me? thx! Here's the code of DriverEntry _Use_decl_annotations_ NTSTATUS DriverEntry( IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath ) { NDIS_FILTER_DRIVER

Was compatibility for NDIS 5.x drivers removed in Windows 10?

不想你离开。 提交于 2019-12-11 13:45:38
问题 I have an NDIS 5.x Passthru driver that was adapted from this sample. Obviously NDIS 6 has been available for quite some time, rendering 5.x obsolete, but backward compatibility has allowed the driver to continue to run in up to and including Windows 8.1 so the code has not been updated. Now the same driver does not function on Windows 10. (Edited to add: The driver loads, but "netcfg /b" shows that it did not bind to any adapters.) The sys file is the same, installed the same way and with

Raw ethernet broadcasting

做~自己de王妃 提交于 2019-12-11 12:12:08
问题 I downloaded WinDDK and am using ndisprot 5x to broadcast raw ethernet packets from my user app, specifying destination MAC all 0xff's, on large and repetitive data sets it doesn't seem to be very productive. What currently works great is a loopback - specifying destination and source MAC's as my own I get needed speed, but the packet never leaves my network card. Maybe I am missing some ndis driver options and wait for a broadcast to complete using this sample MS driver? All I want is the

The compatibility issue between NDIS version and Windows version

二次信任 提交于 2019-12-10 11:42:20
问题 everyone. I am doing some modifications to the WinPcap, a packet capturing library. My boss want me to transfer the NDIS version of WinPcap from NDIS 4 to NDIS 6. And the compatibility requirement is Windows XP/Vista/7/8 (32bit and 64bit). I found that the latest version of NDIS is 6.3, but I'm afraid that NDIS 6.3 does not support XP any more, is this true? Also I found in WinPcap website that the current WinPcap 4.1.3 has already supported Windows XP/2003/Vista/2008/Win7/2008R2/Win8 (x86

.INF files and NCF_HAS_UI: how to write .dll for displaying advanced properties tab of network driver?

為{幸葍}努か 提交于 2019-12-10 11:33:31
问题 I have a NDIS driver, which gets listed both in connection properties's installed items list and in device manager; the question is, how do I write an extension which will be used for managing driver's properties, and how to install it? Of course, a plain GUI program may communicate with the driver, set properties, get version numbers and other statistical info etc, that's what DeviceIoControl exists for; but, does this means that no dedicated interface exists to inform the driver about

DummyNet error NDIS drivers install on Windows 7 x64

a 夏天 提交于 2019-12-09 13:15:51
问题 I've download the current version of DummyNet and according to readme I'm following these steps: Windows: INSTALL THE NDIS DRIVER open the configuration panel for the network card in use (right click on the icon on the SYSTRAY, or go to Control Panel -> Network and select one card) click on Properties->Install->Service->Add click on 'Driver Disk' and select 'netipfw.inf' in this folder select 'ipfw+dummynet' which is the only service you should see click accept on the warnings for the

Is FilterSendNetBufferLists handler a must for an NDIS filter to use NdisFSendNetBufferLists?

孤人 提交于 2019-12-06 15:53:49
问题 everyone, I am porting the WinPcap from NDIS6 protocol to NDIS6 filter. It is nearly finished, but I still have a bit of questions: The comment of ndislwf said "A filter that doesn't provide a FilerSendNetBufferList handler can not originate a send on its own." Does it mean if I used the NdisFSendNetBufferLists function, I have to provide the FilerSendNetBufferList handler? My driver will send self-constructed packets by NdisFSendNetBufferLists, but I don't want to filter other programs' sent

.INF files and NCF_HAS_UI: how to write .dll for displaying advanced properties tab of network driver?

孤者浪人 提交于 2019-12-06 13:30:00
I have a NDIS driver, which gets listed both in connection properties's installed items list and in device manager; the question is, how do I write an extension which will be used for managing driver's properties, and how to install it? Of course, a plain GUI program may communicate with the driver, set properties, get version numbers and other statistical info etc, that's what DeviceIoControl exists for; but, does this means that no dedicated interface exists to inform the driver about configuration changes? It would be pleasant if someone can forward this question to eggheadcafe/osr's ntdev