How is network byte order handled. about dpkt HOT 2 CLOSED

Let's have a look at the "dpkt" source code.
There are a lot of classes that allows us to work with many type of the packets: TCP, UDP, HTTP, Radius and the like.
All of them inherits dpkt.Packet class which actually determines byte order.
Here is the answer (from dpkt.py):
-----//------
class Packet(object):

Base packet class, with metaclass magic to generate members from self.hdr.
hdr should be defined as a list of (name, structfmt, default) tuples
__byte_order__ can be set to override the default ('>')

-----//------
byte_order field determines either big-endian or little-endian byte order should be used.
The default byte order for dpkt is set in _MetaPacket class line 37:
-----//------

t.__hdr_fmt__ = getattr(t, 'byte_order', '>') + ''.join([x[1] for x in st])

-----//------
To sum up, "dpkt" takes care about byte ordering and it uses big-endian (which is default network byte order) format as a default byte order.

Some more info could be found here:

https://en.wikipedia.org/wiki/Endianness
http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/
Official python documentation: https://docs.python.org/2/library/struct.html#struct-alignment

@kbandla or @brifordwylie please, have a look at the answer and close the issue if the answer is full and correct.

from dpkt.

Yup this is the right answer. I tagged this issue with documentation so that we can add this to the docs later.

from dpkt.