Well at least I know. Thanks for responding. Would you happen to
know the errata number and/or how I can get details on it?
----- Original Message -----
From: Rosner, Gedon
To: NT Developers Interest List
Sent: Thursday, April 18, 2002 8:13 AM
Subject: [ntdev] RE: Problem with indicating jumbo frames in multiple buff ers
There is an official Win2k errata for this one. Sorry - no solution other than buffer coalescing…
-----Original Message-----
From: Peter Craft [mailto:xxxxx@alacritech.com]
Sent: Thursday, April 18, 2002 4:48 AM
To: NT Developers Interest List
Subject: [ntdev] Problem with indicating jumbo frames in multiple buffers
To make W2K TCPIP accept Ethernet frames > 1514 bytes, we’ve set the
following OIDs to the larger value eg 9014
OID_GEN_MAXIMUM_FRAME_SIZE 9000
OID_GEN_MAXIMUM_TOTAL_SIZE 9014
Our receive mechanism then receives larger frames (> 1514) into multiple
linked 2K buffers which it proceeds to pass up to TCPIP via NDIS as an
NDIS_PACKET and multiple NDIS_BUFFERS chained off the packet. However
TCPIP drops these packets
and we get no further. If the buffers are copied into a single
contiguous one and this is instead linked to the packet and passed up,
everything works fine. At first we thought that TCPIP may not handle
chained buffers correctly, but a test with chained buffers and frame
sizes <= 1514 worked fine. Is there some other OID or mechanism that
we’re missing?
Thanks
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to ntdev as: xxxxx@alacritech.com
To unsubscribe send a blank email to %%email.unsub%%