Wireshark mailing list archives
the Fragment offset field in IP packet should follow the Raw bitstream?
From: damker <damker () sina com>
Date: Fri, 19 Jun 2020 15:48:41 +0800
an IP packet decode As follows: ... Flags: 0x006b 0... .... .... .... = Reserved bit: Not set .0.. .... .... .... = Don't fragment: Not set ..0. .... .... .... = More fragments: Not set ...0 0011 0101 1000 = Fragment offset: 856 Time to live: 128 I know that it says "The fragment offset is measured in units of 8 octets (64 bits)" in RFC 791. my question is: Flags = 0x006b, the "...0 0011 0101 1000 = Fragment offset: 856" should be "...0 0000 0110 1011 = Fragment offset: 856"? I think the second one is more clear. damker
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Leverage wireshark dissection tree in a 3rd party program Matt (Jun 17)
- the Fragment offset field in IP packet should follow the Raw bitstream? damker (Jun 19)
- Re: the Fragment offset field in IP packet should follow the Raw bitstream? Jaap Keuter (Jun 19)
- the Fragment offset field in IP packet should follow the Raw bitstream? damker (Jun 19)