From: Paul <paul@makrotopia.org>
To: Steve Gilberd <steve@erayd.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Need for HW-clock independent timestamps
Date: Thu, 17 May 2018 12:40:55 +0900 [thread overview]
Message-ID: <1526528456.18498.0@mail.makrotopia.org> (raw)
In-Reply-To: <CAJQSx3at0rGtjPrpch2mcCqeTQCZVwaiG1kSHBW19Nk4McJxGQ@mail.gmail.com>
Hi all,
If I'm not mistaken replay attacks are checked here [1] and only
compare integers with no reference to local time of the receiving node.
The sending nodes timestamp is generated via tai64n_now [2][3]. From my
understanding this function could simply be changed to a auto increased
counter, periodically saved on disc and increased on boot, following
the approach described by Axel Neumann[4]. Mixing real timestamps and
counter should be compatible to one another. Only drawback is see is
that the overview function is likely mixed up [5].
All could be done by a patch specifically for HW-clock less devices or
added to OpenWrt buildroot only[6].
Any reasons why such a patch could be bad?
[1]:
https://github.com/WireGuard/WireGuard/blob/ddb82700a810c3f929e5a2fff00254b29eadc689/src/noise.c#L454
[2]:
https://github.com/WireGuard/WireGuard/blob/ddb82700a810c3f929e5a2fff00254b29eadc689/src/noise.c#L353
[3]:
https://github.com/WireGuard/WireGuard/blob/ddb82700a810c3f929e5a2fff00254b29eadc689/src/noise.c#L396
[4]: https://github.com/bmx-routing/bmx7/blob/semtor/bmx.c#L1397
[5]:
https://github.com/WireGuard/WireGuard/blob/a7f2ceacb9ee09ab37302cddc0ce15a96fd95e70/src/tools/show.c#L25
[6]:
https://github.com/openwrt/openwrt/tree/master/package/network/services/wireguard/patches
Just a few thoughts regarding GPS:
On Thu, May 17, 2018 at 5:32 AM, Steve Gilberd <steve@erayd.net> wrote:
> > $20 would increase the HW cost of many typical community-networks
> (CN) deployments significantly.
>
> This seems unlikely. In most cases, $20 is notably less than the cost
> of a single node.
I'd doubt that. People massively use TP-Link 841 (~20$, 100%) or
Uqiquity Nanobeams (~60$, 34%) as node hardware.
> > Plus requiering more knowledge, maintenence, and power supply for
> sometimes solar-powered setups... no USB.
>
> If that's a concern, then put the GPS on nodes where those
> constraints aren't a problem. You only need GPS on a few nodes (or
> one node if you don't care about redundancy). Most nodes will get by
> just fine with just plain NTP, and can happily fetch their time from
> the GPS nodes, or from other non-GPS nodes with a correct time sync.
This was already answered and found as unusable as it introduces
additional configuration of all nodes, firewall rules, etc?
>
> > It is really NOT as simple as it sounds to plug a $20 GPS !!!
>
> It's not particularly complicated either. The actual setup of the
> devices isn't particularly difficult, and you're already touching
> these nodes to set up wireguard on them, so "I have to touch the
> config" isn't a barrier in this case.
Opening and closing (in a waterproof manner) the previously mentioned
Nanobeam is not particularly trivial. Also it introduces a whole stack
of device specific knowledge. As stated before, this changes the
configuration from "enter wireguard credentials" to "{open, buy
additional, glue} hardware, setup {wireguard, gps, more?}.
For me it looks like a problem solvable in software (as done for the
BMX routing protocol). Why even bother to get hardware involved?
Sunshine,
Paul
next prev parent reply other threads:[~2018-05-17 3:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 22:07 WG: " Axel Neumann
2018-05-11 22:45 ` Kalin KOZHUHAROV
2018-05-12 0:05 ` Glen Bojsza
2018-05-12 19:29 ` Axel Neumann
2018-05-12 19:41 ` Aaron Jones
2018-05-15 20:21 ` Devan Carpenter
2018-05-15 20:49 ` Kalin KOZHUHAROV
2018-05-16 7:10 ` Matthias Urlichs
2018-05-16 19:32 ` Axel Neumann
2018-05-16 20:32 ` Steve Gilberd
2018-05-17 3:40 ` Paul [this message]
2018-05-17 5:03 ` Roman Mamedov
2018-05-17 5:53 ` Matthias Urlichs
2018-05-17 7:07 ` Axel Neumann
2018-05-17 8:28 ` Matthias Urlichs
2018-05-16 20:35 ` Kalin KOZHUHAROV
2018-05-12 22:10 ` Toke Høiland-Jørgensen
2018-05-12 23:05 ` Reuben Martin
2018-05-13 6:11 ` Matthias Urlichs
2018-05-13 12:37 ` Toke Høiland-Jørgensen
2018-05-16 7:01 ` Axel Neumann
2018-05-16 9:38 ` Toke Høiland-Jørgensen
2018-05-16 11:08 ` Matthias Urlichs
2018-05-16 11:12 ` Axel Neumann
2018-05-13 14:21 ` Wang Jian
2018-05-21 10:07 ` WG: " 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
[not found] <1324673763.992877.1526187430298.ref@mail.yahoo.com>
2018-05-13 4:57 ` reiner otto
2018-05-13 12:35 ` Toke Høiland-Jørgensen
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=1526528456.18498.0@mail.makrotopia.org \
--to=paul@makrotopia.org \
--cc=steve@erayd.net \
--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).