Could you show some code example? That will be very helpful.

@denisvmedia The ipv4.Header.Parse() function says the input b must be in the format used by a raw IP socket on the local system, see here.

The raw socket data on Linux is in network byte order (big endian) while the macOS raw socket data is already in the host byte-order or NativeEndian byte-order (which would be little-endian for Intel Macs). Therefore, I suspect you were trying to store the raw packet data on Linux (which is big endian) and parsing it on macOS (which expects little-endian).

You would likely need to deal with the byte-order before feeding the data to ipv4.Header.Parse(). One option would be always store in network byte-order and convert accordingly to match local system.

@mengzhuo here is a minimal example: https://play.golang.org/p/BIPim30eLCN

The output on Darwin and Linux will be different: 60 on Linux and it's correct, while on Mac it's 15380, which is incorrect. That's because there is a hard-coded runtime.GOOS switch in /ipv4/header.go. Yes - like @shushen says - it's stated in the ipv4.Header.Parse() description that the input must be a raw IP socket on the local system. But that's the problem - before working with a Linux raw packet on Darwin I have to convert it. But I think it's a wrong way. I believe that instead there should be a low-level functionality that would accept not just raw packet data but also an OS where it was captured. In this case the code will behave consistently in any environment.