Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: bad udp cksum messages in tcpdump for wg0
Date: Fri, 27 Dec 2019 15:45:04 +0100	[thread overview]
Message-ID: <b9511f60-672c-2b5b-d6aa-893dfd87954b@urlichs.de> (raw)
In-Reply-To: <49-5dfcd100-9-66d44b80@213097787>

Hi,
> ethtool -K wg0 tx off rx off
>
> I want to know if the behavior described above with the checksum
> errors is to be expected? Or is it necessary to turn those checks off
> on all the interfaces?

Yeah. I need that too, on one of my routers. Apparently some checksum
offloading hardware gets confused by wireguard.

Interestingly, on that machine fixing this problem requires turning off
checksumming on the wg interface _or_ on the hardware interface, either
way is sufficient.

-- 
-- Matthias Urlichs


_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-12-27 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 13:47 google gsuite
2019-12-27 14:45 ` Matthias Urlichs [this message]

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=b9511f60-672c-2b5b-d6aa-893dfd87954b@urlichs.de \
    --to=matthias@urlichs.de \
    --cc=wireguard@lists.zx2c4.com \
    /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).