Created attachment 1627960 [details] packet sample Description of problem: ovs-tcpundump doesn't work well on special packet Version-Release number of selected component (if applicable): openvswitch2.11-test-2.11.0-26.el8fdp.noarch How reproducible: Always Steps to Reproduce: 1. tcpdump -n -r vm1.pcap -vv -xx -c 1 | ovs-tcpundump 2. 3. Actual results: lose the last two bits: 000000000100000000000001080045000035e33e00004011becd2a2a2a024242423e9cb300350021d8de2c960100000100000000000003666f6f03636f6d00000100 Expected results: 000000000100000000000001080045000035e33e00004011becd2a2a2a024242423e9cb300350021d8de2c960100000100000000000003666f6f03636f6d0000010001 Additional info: [root@ibm-x3650m5-03 test]# tcpdump -n -r vm1.pcap -vv -xx -c 1 reading from file vm1.pcap, link-type EN10MB (Ethernet) 05:18:33.583714 IP (tos 0x0, ttl 64, id 58174, offset 0, flags [none], proto UDP (17), length 53) 42.42.42.2.40115 > 66.66.66.62.domain: [bad udp cksum 0xd8de -> 0x74da!] 11414+ A? foo.com. (25) 0x0000: 0000 0000 0100 0000 0000 0001 0800 4500 0x0010: 0035 e33e 0000 4011 becd 2a2a 2a02 4242 0x0020: 423e 9cb3 0035 0021 d8de 2c96 0100 0001 0x0030: 0000 0000 0000 0366 6f6f 0363 6f6d 0000 0x0040: 0100 01 [root@ibm-x3650m5-03 test]# rpm -qa | grep openvswitch openvswitch-selinux-extra-policy-1.0-19.el8fdp.noarch openvswitch2.11-test-2.11.0-26.el8fdp.noarch kernel-kernel-networking-openvswitch-ovn-common-1.0-1.noarch openvswitch2.11-2.11.0-26.el8fdp.x86_64 python3-openvswitch2.11-2.11.0-26.el8fdp.x86_64
https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/363791.html
The bug fix has been verified: [root@netqe30 jhsiao]# tcpdump -n -r vm1.pcap -vv -xx -c 1 | ovs-tcpundump reading from file vm1.pcap, link-type EN10MB (Ethernet) 00000000010000000000000108004500003526c9000040117b432a2a2a024242423ed92d00350021d8deae570100000100000000000003666f6f03636f6d0000010001 [root@netqe30 jhsiao]# rpm -q openvswitch2.11 openvswitch2.11-2.11.0-35.el8fdp.x86_64 [root@netqe30 jhsiao]# uname -r 4.18.0-147.el8.x86_64 [root@netqe30 jhsiao]#
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:0171