I guess this is known since HEPv3 uses network byte order but I wanted to create this placeholder to try to address HEPv2 in a minimally invasive way.

I first discovered this when setting up a capture server on a big endian machine with agents that are little endian. Is there a published standard for HEPv2 or would it be safe to assume that the timestamps need to be little endian? If so, maybe a quick fix is to add some macros to sipcapture and siptrace modules that are basically the reverse of ntohl. I.e. they would only reverse the byte order on big endian machines.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.