Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Eddie <stunnel@attglobal.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should wg-quick with SaveConfig accumulate IPv6 link-local addresses
Date: Wed, 18 Jul 2018 17:31:39 -0700	[thread overview]
Message-ID: <c430b4be-fc84-40c3-c9d2-5d5833d8ae89@attglobal.net> (raw)
In-Reply-To: <4T5B-J-USwNbZveJ1mRtq4Mh9Ih8P2yAgR-uqecHysgG0JEw4GpUZwpWRAo8I5WdUihhGnot-qByAePKl7_xiA==@protonmail.ch>

Yeah, Network Manager is installed.

And I'm guessing that it's a different address each time, because the 
(fake) MAC address is random.

Cheers.


On 7/14/2018 11:02 AM, jugs wrote:
> I don't get an IPv6 link local address address on my wg interface. Do you use network manager?
>
>
> ​-jugs​
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On July 10, 2018 10:20 PM, Eddie <stunnel@attglobal.net> wrote:
>
>> ​​
>>
>> Not sure if this is intended behaviour, or not.
>>
>> Every time I start an interface using wg-quick with the SaveConfig =
>>
>> true it reloads all the previous, saved, IPv6 link-local addresses plus
>>
>> generates a new one.  So the first time the interface is started there
>>
>> is 1 link-local address.  The next time, 2.  Then 3. Then 4, etc. etc.
>>
>> Cheers.
>>
>> WireGuard mailing list
>>
>> WireGuard@lists.zx2c4.com
>>
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
>
>

  reply	other threads:[~2018-07-19  0:23 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 [this message]
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=c430b4be-fc84-40c3-c9d2-5d5833d8ae89@attglobal.net \
    --to=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).