Re: NDIS ntohs/htons
- From: Gammaraman <Gammaraman@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 18 Aug 2008 21:26:00 -0700
Thanks, Peter.
Just to clarify, the MAC header and payload is already in network byte order
in the call to MiniportSendPackets/MiniportSend. I am sure over the air it
will be in network byte order just wasn't sure about at the Miniport send
interface.
Just for my education, is this behavior documented somewhere?
So would my check look something like
if( ntohs(nEthtypeLength) >= 0x0600 )
{
// DIX
}
else
{
// 802.3
}
"Peter" wrote:
The data of the MAC header and packet payload in the egress packet is in.
network byte order.
"Gammaraman" <Gammaraman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:20EE665F-6471-4894-8251-6C0A64F2C431@xxxxxxxxxxxxxxxx
Hi,
I am trying to inspect the Ethertype/length field in the Ethernet header
of
an egress NDIS packet handed to the miniport by a protocol driver. What
byte-order does NDIS use for the header and payload? Do I need to put the
Ethertype/length value through a call to ntohs() or htons() or just use
the
value as is?
I am assuming for an ingress NDIS packet, the byte order is network byte
order so I would need to use ntohs() to inpect a short. Is this correct?
Thanks.
- Follow-Ups:
- Re: NDIS ntohs/htons
- From: Peter
- Re: NDIS ntohs/htons
- References:
- NDIS ntohs/htons
- From: Gammaraman
- Re: NDIS ntohs/htons
- From: Peter
- NDIS ntohs/htons
- Prev by Date: Re: How to get Full Image path in NotifyRoutine
- Next by Date: Re: OverlappedIO - Q126282: is this applies to New windows OS also
- Previous by thread: Re: NDIS ntohs/htons
- Next by thread: Re: NDIS ntohs/htons
- Index(es):
Relevant Pages
|