Hi:
I have a TDI client whose ClientEventChainedReceive handler I want to
test. I have noticed that when I send any data to the remote node over an
established connection, only the ClientEventReceive handler is called. I
want to know if there is any way I can generate traffic to test the
chained receive handler.
I do not have an expedited receive handler. I understand that expedited
receives may be sent to the chained receive handler. Is this true?
KK
What platform are you testing on? ChainedReceives are related to NDIS 5.0
miniports that support NdisReceivePacket function. With TDI filter I see TCP
being called at ChainedEventReceive handler.
What size replies are being sent from the remote end? Are replies
sufficiently long to actually span multiple packets?
Are you running a sniffer on the same machine? If so, the sniffer setting
promiscuous mode may effect whether or not the ChainedReceives are called.
Good luck,
Thomas F; Divine
www.pcausa.com
“Keshab Koch” wrote in message news:xxxxx@ntdev…
>
> Hi:
>
> I have a TDI client whose ClientEventChainedReceive handler I want to
> test. I have noticed that when I send any data to the remote node over an
> established connection, only the ClientEventReceive handler is called. I
> want to know if there is any way I can generate traffic to test the
> chained receive handler.
>
> I do not have an expedited receive handler. I understand that expedited
> receives may be sent to the chained receive handler. Is this true?
>
> KK
>
>
> I have a TDI client whose ClientEventChainedReceive handler I want
to
test. I have noticed that when I send any data to the remote node
over an
established connection, only the ClientEventReceive handler is
called. I
want to know if there is any way I can generate traffic to test the
chained receive handler.
This depends on your NIC miniport, whether it calls
NdisMEthIndicateReceive or NdisMIndicateReceivePacket. Try with some
other NIC, with RTL8139, for instance.
I do not have an expedited receive handler. I understand that
expedited
receives may be sent to the chained receive handler.
No. “Expedited” is TCP’s OOB data.
Max