Development discussion of WireGuard
 help / color / mirror / Atom feed
From: xtus <xtus@nexmanti.net>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: wg set fail to update endpoint if traffic is flowing
Date: Tue, 31 Mar 2020 08:36:52 +0000	[thread overview]
Message-ID: <i2UwKoKpd7CcDmlKuf5GHwFTjVhsyWaKbbI_QaLQ5yjGbpBkH7klwefEhR8B7TICn7B4uguk3sK23sExHYpQFUX9txdU-RDQR7w0bCuNj4E=@nexmanti.net> (raw)

Hi,

I was trying to update dynamically the endpoint for an interface, using `reresolve-dns.sh` or something like the following:

# wg set <interface> peer "<publickey>" endpoint "<FQDN>:<port>"

But the endpoint did not change, even if the `wg set` returns successfully, with retcode `0`.

Changing something like `persistent-keepalive` does work.

I debugged a bit, and I saw that if traffic is flowing throw the wireguard interface, then the endpoint change via `wg set` does not take effect.

The set endpoint works only if no traffic is flowing.

Is this expected behavior?

Thanks,
xtus


             reply	other threads:[~2020-04-04 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  8:36 xtus [this message]
2020-04-10  8:01 ` Luis Ressel

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='i2UwKoKpd7CcDmlKuf5GHwFTjVhsyWaKbbI_QaLQ5yjGbpBkH7klwefEhR8B7TICn7B4uguk3sK23sExHYpQFUX9txdU-RDQR7w0bCuNj4E=@nexmanti.net' \
    --to=xtus@nexmanti.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).