netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 206089] New: veth, virtio tx checksum wrong, forwarding drops packets
Date: Sun, 5 Jan 2020 16:40:38 -0800	[thread overview]
Message-ID: <20200105164038.03dcb625@hermes.lan> (raw)



Begin forwarded message:

Date: Sun, 05 Jan 2020 21:34:41 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 206089] New: veth, virtio tx checksum wrong, forwarding drops packets


https://bugzilla.kernel.org/show_bug.cgi?id=206089

            Bug ID: 206089
           Summary: veth, virtio tx checksum wrong, forwarding drops
                    packets
           Product: Networking
           Version: 2.5
    Kernel Version: 5.3.0-24-generic #26-Ubuntu SMP
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IPV4
          Assignee: stephen@networkplumber.org
          Reporter: hcoin@quietfountain.com
        Regression: No

Both using ipv4 and ipv6 when iface below is a:
virtio net driver in a kvm 
and
on baremetal when one end of a veth pair when the other end is in a filtering
bridge:

ethtool -K iface tx-checksum-ip-generic on
echo -n "rsschecksum test" | nc -w 3 -4 -u -b -s 192.168.172.3 192.168.172.63
52722
tcpdump -e -p -c 3 -n -vv -i iface ...

Bad TX Checksum generated by interface cephnoc0iface
15:04:21.350281 52:54:bc:75:61:1b > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 58: (tos 0x0, ttl 64, id 39761, offset 0, flags [DF], proto UDP (17),
length 44)
192.168.172.3.48926 > 192.168.172.63.52722: [bad udp cksum 0xd9bd -> 0x1f01!]
UDP, length 16

But when

ethtool -K iface tx-checksum-ip-generic off
echo -n "rsschecksum test" | nc -w 3 -4 -u -b -s 192.168.172.3 192.168.172.63
52722
tcpdump -e -p -c 3 -n -vv -i iface ...
tcpdump: listening on ens3, link-type EN10MB (Ethernet), capture size 262144
bytes
14:06:50.791664 52:54:00:0b:3d:7c > 52:54:a2:98:33:f0, ethertype IPv4 (0x0800),
length 61: (tos 0x0, ttl 64, id 9609, offset 0, flags [DF], proto UDP (17),
length 47)
10.12.112.180.34476 > 10.12.112.65.52722: [udp sum ok] UDP, length 19
14:06:50.791734 52:54:00:0b:3d:7c > 52:54:e6:39:16:e8, ethertype IPv4 (0x0800),
length 61: (tos 0x0, ttl 64, id 20912, offset 0, flags [DF], proto UDP (17),
length 47)
10.12.112.180.34476 > 10.12.112.66.52722: [udp sum ok] UDP, length 19
14:06:50.791784 52:54:00:0b:3d:7c > 52:54:da:59:f5:e0, ethertype IPv4 (0x0800),
length 61: (tos 0x0, ttl 64, id 1977, offset 0, flags [DF], proto UDP (17),
length 47)
10.12.112.180.34476 > 10.12.112.67.52722: [udp sum ok] UDP, length 19

The problem was detected when packets got dropped passing through all-linux
routers and filtering vlan bridges.  A vanilla VM instance running chrony on
one VM couldn't access an ntpsec time server on a different subnet running on
bare metal on a physically adjacent server using ipv6.   The above examples are
ip4, but the results are the same with ip6.  The above examples are udp, the
results are the same with tcp.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-01-06  0:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200105164038.03dcb625@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).