Revision history  [back]

Hi, I see in the ZMG-390_Log.pcapng capture after packet 948, the next multicast packet is 976 approximately 23.493sec later. Did you notice that is when Wireshark starts reporting IPv4 checksum errors and IPv6 multicast packets? Wireshark believes this could "IP checksum offload". The other file doesn't have IPv4 checksum errors or IPv6. Filter for IPv4 checksum is "ip.checksum_bad.expert"

Hi, I see in the ZMG-390_Log.pcapng capture after packet 948, the next multicast packet is 976 approximately 23.493sec later. Did you notice that is when Wireshark starts reporting IPv4 checksum errors and IPv6 packets? Wireshark believes this could "IP checksum offload". The other file doesn't have IPv4 checksum errors or IPv6. errors.
Filter for IPv4 checksum is "ip.checksum_bad.expert"

Hi, I see in the ZMG-390_Log.pcapng capture after packet 948, the next multicast packet is 976 approximately 23.493sec later. Did you notice that is when Wireshark is starts reporting IPv4 checksum errors and IPv6 packets? errors? Wireshark believes this could "IP checksum offload". The other file doesn't have IPv4 checksum errors.
Filter for IPv4 checksum is "ip.checksum_bad.expert"

Hi, I see in the ZMG-390_Log.pcapng capture after packet 948, the next multicast packet is 976 approximately 23.493sec later. Did you notice that is when Wireshark is starts reporting IPv4 checksum errors? Wireshark believes this could "IP checksum offload". UDP offloading. The other file doesn't have IPv4 checksum errors.
Filter for IPv4 checksum is "ip.checksum_bad.expert"

Hi, I see in the ZMG-390_Log.pcapng capture after packet 948, the next multicast packet is 976 approximately 23.493sec later. Did you notice that is when Wireshark is starts reporting IPv4 checksum errors? Wireshark believes this could UDP offloading. The other file doesn't have IPv4 checksum errors.
Filter for IPv4 checksum is "ip.checksum_bad.expert"