Your application needs to store the type in network order (big-endian
order) in the packet before it sends it out.
Wireshark is programmed to follow the specifications of the protocol,
regardless of what type of CPU wireshark is running on. Similarly,
network applications or network stacks must follow those same
specifications, regardless of the CPU they are running on.
And the Ethernet specification says that the ethernet type is stored
in big-endian order.
--gilbert
On 7/4/07, Amit Paliwal <Amit.Paliwal@xxxxxxxxxxxxxxx> wrote:
Hi,
I registered my proprietary protocol over ethernet and set its typw to say
0x0102.
to test my application i construct and send a raw ethernet packet from my
machine(Windows XP)........
but wireshark captures ethernet type as 0x0201 which is the network order so
i need to manipulate
my ethernet type to 0x0201, than wireshark receives it as 0x0102............
Intel machines probably uses little endian format.
I want to ask is there any provision in Wireshark's code that checks for it
so that next time if from some other machine
ethernet typw will come it will see that it has to take it in little endian
format or big endian format, or do i need to modify the code somewhere......
______________________________________________________________________
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev