From: Derrick Lyndon Pallas <derrick@pallas.us>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Long outage when changing private key
Date: Thu, 24 Jan 2019 13:22:04 -0800 [thread overview]
Message-ID: <8ae75832-91dd-428e-9b04-a48cec019bf6@pallas.us> (raw)
With two peers, A with persistent keepalive & B without, I am trying to
change the private key on peer A. First I update the public key for A at
B, then `wg set wg0 private-key XXXX` on A. It takes roughly the length
of the persistent keepalive to reestablish pings from B to A.
If instead I update the public key for A at B, remove peer B at A,
change A's private key, and then re-add peer B at A, I am able to
reestablish pings almost immediately.
My guess was that there was a timer that needed to be reset when
wg_set_device processes WGDEVICE_A_PRIVATE_KEY, but an attempt to reset
timers was unsuccessful. I am new to this code and could use some
pointers/advice on where to look next.
~Derrick
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-01-24 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 21:22 Derrick Lyndon Pallas [this message]
2019-01-24 23:25 ` Derrick Lyndon Pallas
2019-01-24 23:59 ` Jason A. Donenfeld
2019-01-25 0:00 ` Jason A. Donenfeld
2019-01-25 1:55 ` Derrick Lyndon Pallas
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=8ae75832-91dd-428e-9b04-a48cec019bf6@pallas.us \
--to=derrick@pallas.us \
--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).