From: Roman Mamedov <rm@romanrm.net>
To: lejeczek <peljasz@yahoo.co.uk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wgX iface as slave to a bridge - Linux
Date: Sun, 25 Apr 2021 19:07:31 +0500 [thread overview]
Message-ID: <20210425190731.5625f0ab@natsu> (raw)
In-Reply-To: <0c8b4be5-ee9d-4f19-7179-ad08a28d0574@yahoo.co.uk>
On Sat, 24 Apr 2021 11:11:50 +0100
lejeczek <peljasz@yahoo.co.uk> wrote:
> Hi guys.
>
> Apologies, I'll bother you guys as I failed to find some
> better places to ask, I searched for forums etc. but failed.
>
> Can wiregurard ifaces be enslaved by LInux bridge? I tried
> but it did not work for me. Similarly "mavclan" -
> would/should wireguard work that way?
> What I've tried and failed was on CentOS stream with
> 4.18.0-294.el8.x86_64.
As others have replied, it is an L3 interface, not L2 which can join bridges.
One solution that many use is to run an L2 tunnel over WireGuard, such as
VXLAN or GRETAP. But then you lose even more MTU compared to the standard 1500.
--
With respect,
Roman
prev parent reply other threads:[~2021-04-25 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0c8b4be5-ee9d-4f19-7179-ad08a28d0574.ref@yahoo.co.uk>
2021-04-24 10:11 ` lejeczek
2021-04-25 5:33 ` Mike O'Connor
2021-04-25 12:21 ` Chriztoffer Hansen
2021-04-25 13:13 ` lejeczek
2021-04-27 19:49 ` Ivan Labáth
2021-04-25 14:07 ` Roman Mamedov [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=20210425190731.5625f0ab@natsu \
--to=rm@romanrm.net \
--cc=peljasz@yahoo.co.uk \
--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).