wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Sune Mølgaard" <sune@molgaard.org>
To: wireguard@lists.zx2c4.com
Subject: Wireguard, bridging and DHCP?
Date: Mon, 14 Oct 2019 17:30:27 +0200	[thread overview]
Message-ID: <a4ca89a7-5eee-e570-e721-e559e9eb0e23@molgaard.org> (raw)

Hi all,

1. Would it be possible, on the server, to bridge wg0 with another
interface, e.g. the one attached to the local net and, hence, avoid
extra subnets and routes?

2. If so, would it also be possible for Wireguard *not* to assign any IP
addresses to the clients, but have them obtain such via DHCP on the
local net, which wg0 is bridged to on the server?

Best regards,

Sune Mølgaard

-- 
Black holes are where God divided by zero.
- Steven Wright
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2019-11-27  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 15:30 Sune Mølgaard [this message]
2019-11-27 12:25 ` Wireguard, bridging and DHCP? Jason A. Donenfeld

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=a4ca89a7-5eee-e570-e721-e559e9eb0e23@molgaard.org \
    --to=sune@molgaard.org \
    --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).