* Race condition/no locking on configuration load
@ 2023-04-02 12:54 caskd
0 siblings, 0 replies; only message in thread
From: caskd @ 2023-04-02 12:54 UTC (permalink / raw)
[-- Attachment #1.1: Type: text/plain, Size: 756 bytes --]
i've hit a weird edgecase where the wireguard config gets loaded and during the load the interface gets a address assigned which just disappears. Here's how i replicate it.
ip link add $IFNAME type wireguard
wg setconf $IFNAME $CONFIG #-- while this runs, run the command below in parallel
ip -6 address add $ADDR dev $IFNAME
Following this, the added interface address doesn't persist, yet no error is returned by either iproute2 or wireguard-tools.
Is this a known problem? I assume it has to do with no locking being done or similar but i haven't looked deeper into it.
RedXen System & Infrastructure Administration
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-04-03 22:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-04-02 12:54 Race condition/no locking on configuration load caskd
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).