wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: wireguard@qupfer.de
To: wireguard@lists.zx2c4.com
Subject: Re: linux: bridging/bonding not possible
Date: Thu, 14 Oct 2021 09:12:27 +0200	[thread overview]
Message-ID: <84cf0d10-471a-5e25-a160-79dd7cdfc367@qupfer.de> (raw)
In-Reply-To: <76173@imapsync>


 >> is it possible (or even planned) to add hw-addresses to the
 >> wireguard-netdevs or does this interfere with the concept of wireguard?

I hope I say nothing wrong, but its not (directly) possible and probably 
not plant.

Wireguard is a so called Layer-3 VPN, bridging is a Layer-2 thing. So it 
will no work together.
But you could use an (un)secure Layer-2-VPN (like L2TP) and transport it 
through wireguard. (similar to the often used L2TP over IPsec).
You could also take a look to softether vpn 
(https://www.softether.org/), which also includes a Layer-2 VPN. But I 
have no clue about the security quality.

       reply	other threads:[~2021-10-14 15:34 UTC|newest]

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

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:

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

  git send-email \
    --in-reply-to=84cf0d10-471a-5e25-a160-79dd7cdfc367@qupfer.de \
    --to=wireguard@qupfer.de \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: linux: bridging/bonding not possible' \


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