Development discussion of WireGuard
 help / color / mirror / Atom feed
* wg syncconf (and setconf) error when one or more endpoints is unresolvable
@ 2021-06-15  8:35 Christian McDonald
  2021-06-15 10:52 ` Jason A. Donenfeld
  0 siblings, 1 reply; 5+ messages in thread
From: Christian McDonald @ 2021-06-15  8:35 UTC (permalink / raw)
  To: Jason A. Donenfeld; +Cc: WireGuard mailing list

Jason,

Assume a tunnel with say 3 peers. Peer A is accessible via an IPv4
address, Peer B by some FQDN, and Peer C by some other FQDN. Let's
also assume that Peer C was misconfigured with an unresolvable FQDN.
wg syncconf (and setconf) fails with 'Name does not
resolve...Configuration parsing error'

Is it expected behavior in this case that *none* of the peer
configurations are actually applied? It seems like a more appropriate
behavior would be to go ahead and configure the remaining peers (Peer
A + B) but only fail on the peer with an unresolvable endpoint (Peer
C). It of course is completely possible to re-implement syncconf and
setconf using explicit `wg set` calls as a workaround.

Am I missing something here?

Thanks,
Christian
-- 
R. Christian McDonald
E: rcmcdonald91@gmail.com

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-06-15 15:23 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-15  8:35 wg syncconf (and setconf) error when one or more endpoints is unresolvable Christian McDonald
2021-06-15 10:52 ` Jason A. Donenfeld
2021-06-15 13:23   ` Lonnie Abelbeck
2021-06-15 15:07     ` Christian McDonald
2021-06-15 15:22       ` Jason A. Donenfeld

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).