Not receiving packets from my ethernet NDIS driver

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello,

I'm writing an NDIS driver which pretends to be an ethernet adapter.
The adapter loads fine and is able to indicate packets to the upper
protocol stack using NdisMEthIndicateReceive. I can see these packets
with the vxsniffer application, but not with my own visual C
application. The receiving application has been tested by using send()
from localhost and it receives things just fine. But anything coming
from my driver just doesn't arrive.

This might have something to do with the fact that some other
application still reports that the driver has IP address 0.0.0.0, mask
0.0.0.0 etc even though I've set a static IP address (192.168.1.1)
through the network adapters dialog of windows mobile. I'm using WM
2005 Pocket PC. The packets I'm sending are also directed to the
192.168.1.1 address.

A related problem may be that I can't seem to join a multicast group on
this interface either, this fails with the error WSAEADDRNOTAVAIL,
which presumably also refers to the 192.168.1.1 address. I think the
problem is therefore related to the fact that windows thinks the
interface address is 0.0.0.0.

Any ideas on why NDIS doesn't assign the correct address or how I can
change that? Or other ideas about why my packets don't arrive at the
receiver application / why the multicast join fails?


regards,
John

.



Relevant Pages

  • Re: question regarding load-balancing intermediate driver
    ... I am working on an load-balancing/fail-over intermediate driver ... Whenever I disable one of the physical adapter which is part of team, ... driver stops receiving packets. ... MAC address of the adapter that was disabled? ...
    (microsoft.public.development.device.drivers)
  • Re: question regarding load-balancing intermediate driver
    ... The driver can load balance the traffic across many ports. ... The physical device is receiving the packets ... It seem that the Ethereal capture proves that packets are being sent to the adapter, but does not show that they are being received by the adapter. ...
    (microsoft.public.development.device.drivers)
  • Re: Wireless Sniffing in Windows 7 with Netmon 3.4
    ... adapter / driver that appears to successfully sniff 802.11n frames ... the Intel 11n adapters do not.) ... Chipset is Broadcom 43xx, the driver is ... So the packets probably are 802.11n. ...
    (alt.internet.wireless)
  • Re: NdisMIndicateReceivePacket for large packets
    ... perfectly well with adapter X and fail with adapter Y for no obvious ... I'd really like to tell this to a lot of the Wi-Fi miniport driver ... test claims to support. ... supports larger packets than the test one. ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS driver multiple ip addresses
    ... Well, it's not a driver that gets an IP address, it's an instance of the ... adapter that the driver manages. ... Paul T. ... Is it possible to assign more than one ip address to a NDIS driver? ...
    (microsoft.public.windowsce.platbuilder)