Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Nikolai Lusan <nikolai@lusan.id.au>
To: wireguard@lists.zx2c4.com
Subject: Using wg-quick without having it set routes
Date: Sat, 21 Nov 2020 22:59:17 +1000	[thread overview]
Message-ID: <6492535965d6a99ee429384b762b29b8631e2ec5.camel@lusan.id.au> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

I have recently started using wireguard as a VPN between my home
network[s] and my external servers. In addition to this I have been
deploying it on other machines I would like to have connected to my
network via VPN (mostly friends who I want to have access to my
internal network, and me to their machines for remote admin/trouble
shoothing).

I am running Debian and had set things up using
/etc/network/interfaces.d/ files. I was wanting move to use wg-quick
with systemd - trying to bring up newly created interfaces on the main
server/termination point using wg-quick leads to wg trying to create
routes for all IP ranges in "AllowedIPs". I would like to be able to
_not_ have this happen, is it possible? Or should I just stick with the
interfaces.d file method and "auto wg[0-N]"?

- -- 
Nikolai Lusan <nikolai@lusan.id.au>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEVfd4GW6z4nsBxdLo4ZaDRV2VL6QFAl+5DyUACgkQ4ZaDRV2V
L6RDvBAAsxW7dmnX8ObVkiv57IB2tgIUtdSkMNqcx75HfTp7WBBH0t2tq9LZRs8j
TcWrBXM1JK9MCcjtHTVDRZJaAXlwZlvvhnEUjEHkFiBHpU/3yTb053GZpGP2YYnE
al6z1EcifqDXTmO07w8TVhRmYMsS0hFnCtD6AxpS/OHRr676SVfNuyYt6KYeQnOW
0HrD7LkLyukOXtFMQ+0HO0Vd5+I4YN1w5eMKP7nakBEJSPjp5drxNqFVib+MvL4t
b/bNCU+nPvA4noVnsMTwx/Th7UalnqFrpeoQHmuxymGz0EzXuMgTQqdUyZcUPOhN
Hg09+0BQ9X1x8H1qE8BP0T24/tpe6qttqrk5gy7XVZcS/Vpum0GMoPMloBgQK/8t
Jezj2I4O9D+Tc2as/1CeOuqbAoHC6sldSMeJerUv5gihaHQ4Eux4qXcBqrLnKFV7
ndQI2+wmEkd25zYADeia03zbVgBD/Y6iHr9WCIOSaWvm6dFXfQfo+FssSnyqeIOs
f45Ww6n88fJfLLtTIs9eoM+JlnsoXZUWq+aKdloeMRxMfOmcGNUlZn7sa12Jq3dm
xjvI9Y1CTGL8soi6Zb7wrxK2wvr/svDaFYjy9oDd6IRZRAp3zcrnqElYyt7kXr4z
9hg9Vzo76Gh14rrE2Fof6R5HXbc8JgMSODvv9UelWgyMvG2Y/24=
=1T+E
-----END PGP SIGNATURE-----


             reply	other threads:[~2020-11-23 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21 12:59 Nikolai Lusan [this message]
2020-11-23 14:44 ` PGNet Dev

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=6492535965d6a99ee429384b762b29b8631e2ec5.camel@lusan.id.au \
    --to=nikolai@lusan.id.au \
    --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).