From: reiner otto <augustus_meyer@yahoo.de>
To: <wireguard@lists.zx2c4.com>, <neumann@cgws.de>
Subject: Re: WG: Need for HW-clock independent timestamps
Date: Mon, 21 May 2018 11:58:53 +0000 (UTC) [thread overview]
Message-ID: <1522499692.6109802.1526903933505@mail.yahoo.com> (raw)
In-Reply-To: <1522499692.6109802.1526903933505.ref@mail.yahoo.com>
+1;=20
Not just to consider the "very standard case", which why quality of softwar=
e nowadays goes down.
Although you are correct here, that power cycle is almost normal usage proc=
edure.
--------------------------------------------
Axel Neumann <neumann@cgws.de> schrieb am Mo, 21.5.2018:
Betreff: Re: WG: Need for HW-clock independent timestamps
An: wireguard@lists.zx2c4.com
Datum: Montag, 21. Mai, 2018 14:52 Uhr
=20
On 21.05.2018 13:22, Reto Brunner
wrote:
> On Mon, May 21, 2018 at
12:07:38PM +0200, Axel Neumann wrote:
>> entirely superfluous. As discussed
earlier [3] it can be achieved with
>>
essentially one file-system write operation each boot.
>=20
> You might as well
achieve the same with the timestamp.
>
Just add a pre-shutdown hook, which touches a file.
=20
yes, can be an option, but
would only work in "normal" soft-shut-down
cases, not in case of a hard reset or power
cycle. A not-so-uncommon
scenario for
embedded home-network devices and community-network
deployments. Especially when considering the
first choice of a=C2=A0 normal
user (desperately
trying to fix its internet-via-WG tunnel connection):
Power cycle the device.
=20
/axel
=20
>
Restore the system clock to this upon boot (which may very
well be off
> but who cares).
>=20
> After the wg tunnel
is back up, sync with any NTP server you trust and you
> are back up and running.
>=20
> What is the
advantage of doing it with a counter?
> I
fail to see the benefit.
>
_______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
=20
=20
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
=20
next parent reply other threads:[~2018-05-21 11:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1522499692.6109802.1526903933505.ref@mail.yahoo.com>
2018-05-21 11:58 ` reiner otto [this message]
2018-05-11 22:07 Axel Neumann
2018-05-21 10:07 ` Axel Neumann
2018-05-21 11:22 ` Reto Brunner
2018-05-21 11:52 ` Axel Neumann
2018-05-21 12:31 ` Axel Neumann
2018-05-21 12:35 ` Reto Brunner
2018-05-21 13:53 ` Matthias Urlichs
2018-05-21 14:56 ` Bruno Wolff III
2018-05-21 15:34 ` Matthias Urlichs
2018-05-22 20:25 ` Ivan Labáth
2018-05-23 2:51 ` Matthias Urlichs
2019-02-04 14:56 ` Jason A. Donenfeld
2019-02-23 4:00 ` Axel Neumann
2019-02-23 12:35 ` Ivan Labáth
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=1522499692.6109802.1526903933505@mail.yahoo.com \
--to=augustus_meyer@yahoo.de \
--cc=neumann@cgws.de \
--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).