From: Goran <sendmailtogoran@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: vxlan on top of wireguard
Date: Sun, 6 May 2018 13:29:09 +0200 [thread overview]
Message-ID: <CABS5c+FbHoZ+W_=vHm_kgQU0zZHZQPjWVJpPzehMYMcdzY36DQ@mail.gmail.com> (raw)
I have configured a distributed swith (vxlan) on top of a wireguard
tunnel. I learned it from https://insom.github.io/journal/2017/04/02/
but did not tried the workaround described there. The workaround
states that wireguard has some sort of bug and the
hardware-accelerated checksums must be disabled: ethtool -K $i tx off
. As the article is from last year, I tried it first without this
workaround. With that I could send icmp packets but no tcp.
Sometimes I could send a tcp packet with crazy MTU like 64 or so. Does
someone knows why this strange behaviour exists?
With workaround all works fine.
reply other threads:[~2018-05-06 11:26 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='CABS5c+FbHoZ+W_=vHm_kgQU0zZHZQPjWVJpPzehMYMcdzY36DQ@mail.gmail.com' \
--to=sendmailtogoran@gmail.com \
--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).