From: Xand <xand@xand.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: Should wg-quick with SaveConfig accumulate IPv6 link-local addresses
Date: Sat, 8 Dec 2018 13:32:38 +0000 [thread overview]
Message-ID: <6a703cdc-13e4-4881-7bb5-072b0f576a3e@xand.uk> (raw)
In-Reply-To: <c430b4be-fc84-40c3-c9d2-5d5833d8ae89@attglobal.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 648 bytes --]
I'm running Wireguard on a number of Debian 9 and CentOS 7.6 VMs. On the
CentOS VMs I experience the same issue as
https://lists.zx2c4.com/pipermail/wireguard/2018-July/003134.html. I'm
using wireguard-dkms and wireguard-tools from
https://copr-be.cloud.fedoraproject.org/results/jdoss/wireguard/ and
using the wg-quick service.
I do *not* have NetworkManager installed.
Each time wg0 comes up, a different IPv6 link-local address is added to
it. With SaveConfig set to true, these accumulate indefinitely.
Using identical configuration on the Debian 9 VMs, I don't ever get any
link-local addresses assigned to wg0.
Xand
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-12-10 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 22:20 Eddie
2018-07-14 18:02 ` jugs
2018-07-19 0:31 ` Eddie
2018-12-08 13:32 ` Xand [this message]
2018-12-10 1:15 ` Jason A. Donenfeld
2018-12-10 2:04 ` Samuel Holland
2018-12-10 2:05 ` Jason A. Donenfeld
2018-12-10 2:13 ` Samuel Holland
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=6a703cdc-13e4-4881-7bb5-072b0f576a3e@xand.uk \
--to=xand@xand.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 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).