Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Linus Karl <linus@lotz.li>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: wireguard@lists.zx2c4.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: wireguard: add netlink mcast on endpoint change
Date: Sun, 10 Apr 2022 21:06:34 +0200	[thread overview]
Message-ID: <20220410190635.1171195-1-linus@lotz.li> (raw)

This patch adds the possibility to retrieve notifications of peer
endpoint changes via netlink multicast messages. It has been a while
since I posted v2, the main difference is that I've added an extra
attribute to the netlink device attributes to allow enabling or
disabling of this feature. It is per default disabled.



             reply	other threads:[~2022-04-10 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10 19:06 Linus Karl [this message]
2022-04-10 19:06 ` [PATCH v3] " Linus Karl

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=20220410190635.1171195-1-linus@lotz.li \
    --to=linus@lotz.li \
    --cc=Jason@zx2c4.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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).