From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: luca@z3ntu.xyz
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: build.wireguard.com down
Date: Sun, 5 Sep 2021 14:23:32 +0200 [thread overview]
Message-ID: <CAHmME9o3p-z+geceaHybP_RjUmotwddLCV5RQhdxTZBGf1fyiA@mail.gmail.com> (raw)
In-Reply-To: <1126168D-D01E-48E8-B3F4-308F16666C61@z3ntu.xyz>
Sorry for that.
We're all set now, though I don't yet understand root cause.
Apparently it shutdown on Sept 2 and returned with different NICs (I
think?), which had a different stable identifier and so an IP address
wasn't configured on them. Going to begin analyzing the situation now
that connectivity is restored.
Jason
prev parent reply other threads:[~2021-09-05 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 11:46 Luca Weiss
2021-09-05 12:23 ` Jason A. Donenfeld [this message]
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=CAHmME9o3p-z+geceaHybP_RjUmotwddLCV5RQhdxTZBGf1fyiA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=luca@z3ntu.xyz \
--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).