wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: uxDWzco-wg@moenia.de
Cc: wireguard@lists.zx2c4.com
Subject: Re: linux: bridging/bonding not possible
Date: Thu, 14 Oct 2021 12:53:18 +0500	[thread overview]
Message-ID: <20211014125318.0e569dfc@nvm> (raw)
In-Reply-To: <78fa512a-82c6-0b0c-d759-162d31a134b4@moenia.de>

On Thu, 14 Oct 2021 04:45:32 +0200
uxDWzco-wg@moenia.de wrote:

> as I understand, linux needs the ability to change hardware-addresses on
> netdevs to put them into a bridge or bond, but wireguard-netdevs on
> linux don't support hw-addresses at all (at least in kernel 5.10).
> 
> is it possible (or even planned) to add hw-addresses to the
> wireguard-netdevs or does this interfere with the concept of wireguard?

Hello,

It is not a matter of hw-addresses;

Wireguard is L3 interface, transferring IPv4 and IPv6 packets.

For bridging you would need an L2 interface, which transfers Ethernet frames.

It is possible to do a bridge with WG, by using an L2-over-L3 tunnel such as
VXLAN or GRETAP over WG, and bridging that. Of course this leads to additional
overhead and MTU reduction.

If you would prefer to have an L2 VPN directly, there are other solutions such
as Tinc and OpenVPN.

-- 
With respect,
Roman

  parent reply	other threads:[~2021-10-14  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  2:45 uxDWzco-wg
2021-10-14  3:25 ` Benda Xu
2021-10-14  7:53 ` Roman Mamedov [this message]
     [not found] <76173@imapsync>
2021-10-14  7:12 ` wireguard

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=20211014125318.0e569dfc@nvm \
    --to=rm@romanrm.net \
    --cc=uxDWzco-wg@moenia.de \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: linux: bridging/bonding not possible' \
    /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

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).