From: jugs <jugs@protonmail.ch>
To: "stunnel@attglobal.net" <stunnel@attglobal.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should wg-quick with SaveConfig accumulate IPv6 link-local addresses
Date: Sat, 14 Jul 2018 14:02:58 -0400 [thread overview]
Message-ID: <4T5B-J-USwNbZveJ1mRtq4Mh9Ih8P2yAgR-uqecHysgG0JEw4GpUZwpWRAo8I5WdUihhGnot-qByAePKl7_xiA==@protonmail.ch> (raw)
In-Reply-To: <2e6b4759-1acd-ddd3-2471-14ce932ac82a@attglobal.net>
I don't get an IPv6 link local address address on my wg interface. Do you u=
se network manager?
=E2=80=8B-jugs=E2=80=8B
=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On July 10, 2018 10:20 PM, Eddie <stunnel@attglobal.net> wrote:
> =E2=80=8B=E2=80=8B
>=20
> Not sure if this is intended behaviour, or not.
>=20
> Every time I start an interface using wg-quick with the SaveConfig =3D
>=20
> true it reloads all the previous, saved, IPv6 link-local addresses plus
>=20
> generates a new one.=C2=A0 So the first time the interface is started the=
re
>=20
> is 1 link-local address.=C2=A0 The next time, 2.=C2=A0 Then 3. Then 4, et=
c. etc.
>=20
> Cheers.
>=20
> WireGuard mailing list
>=20
> WireGuard@lists.zx2c4.com
>=20
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-07-14 17:55 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 [this message]
2018-07-19 0:31 ` Eddie
2018-12-08 13:32 ` Xand
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='4T5B-J-USwNbZveJ1mRtq4Mh9Ih8P2yAgR-uqecHysgG0JEw4GpUZwpWRAo8I5WdUihhGnot-qByAePKl7_xiA==@protonmail.ch' \
--to=jugs@protonmail.ch \
--cc=stunnel@attglobal.net \
--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).