All of lore.kernel.org
 help / color / mirror / Atom feed
From: 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 14:13:24 +0100	[thread overview]
Message-ID: <4eeeaa84-65a9-d53e-972b-c2212babc944@yahoo.co.uk> (raw)
In-Reply-To: <CA+cYV6uTvNYv3wkZ9vS8wBP5BHEmg8rZHg7WBvyRkHdd+fjpVg@mail.gmail.com>



On 25/04/2021 13:21, Chriztoffer Hansen wrote:
>> 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?
> Why would you want to enslave an L3-only capable interface to an L2 bridge?
>
> What is your use case behind the question?
>
Containers. Simple (but also can be complex too as scales 
easily) case where containers would be glued together and be 
able to communicate across nodes/hosts via wireguard 
tunnel/link.
I'm looking at it from a 'regular' admin standpoint.
Then it'd be just one wiregurard host-to-host link which all 
container could utilize, as oppose to separate wireguard 
for/in each container.

many thanks, L.


  reply	other threads:[~2021-04-25 13:15 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 ` wgX iface as slave to a bridge - Linux lejeczek
2021-04-25  5:33   ` Mike O'Connor
2021-04-25 12:21   ` Chriztoffer Hansen
2021-04-25 13:13     ` lejeczek [this message]
2021-04-27 19:49       ` Ivan Labáth
2021-04-25 14:07   ` 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:
  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=4eeeaa84-65a9-d53e-972b-c2212babc944@yahoo.co.uk \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.