I really appreciate the resumption.
Whatever mechanisms wireguard introduces to handle non-RTC devices with
limited flash-write cycles (which far most of the openWrt community
uses) would significantly ease the configuration of
every-even-ntp-traffic-secured networks.
Regarding
> Initiation of
On 21.05.2018 13:52, Axel Neumann wrote:
> 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
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.
>
> You might as well achieve the sa
Hello,
With regards to the subject, ...to discuss the demand and identify
solutions for a "HW-clock INDEPENDENT WG solution", I've seen
essentially three different suggestions so fare:
a) Buy and connect a HW clock.
IMO: Often difficult considering available HW, budget, and skills.
b) Rely on th
Am 17. Mai 2018 07:53:17 MESZ schrieb Matthias Urlichs :
>On 17.05.2018 07:03, Roman Mamedov wrote:
>> Personally I am puzzled this is even an issue in WG. Not a single
>other VPN
>> protocol mandates every node to keep a monotonically increasing
>counter,
>> including even over reboots.
>
>Wireg
Am 15. Mai 2018 22:49:15 MESZ schrieb Kalin KOZHUHAROV :
>On Tue, May 15, 2018 at 10:21 PM, Devan Carpenter
>> Using NTP is not a viable solution for a distributed mesh network.
>What
>> if the Internet is only accesible via WG, or what if the network is
>not
>> connected to the Internet at all
Am 16. Mai 2018 11:38:23 MESZ schrieb "Toke Høiland-Jørgensen" :
>Axel Neumann writes:
>
>> On 13.05.2018 14:37, Toke Høiland-Jørgensen wrote:> Matthias Urlichs
>> writes:
>>>
>>>> Can anybody think of problems with this solution?
>>>
On 13.05.2018 14:37, Toke Høiland-Jørgensen wrote:> Matthias Urlichs
writes:
>
>> Can anybody think of problems with this solution?
>
> Well, the possibility of DOS if you set the counter too high,
Correct me please, but skipping even many counter values should not be a
problem at all. So do you
sequence number
instead of a timestamp?
More inline below...
On 12.05.2018 00:45, Kalin KOZHUHAROV wrote:
> On Sat, May 12, 2018 at 12:07 AM, Axel Neumann wrote:
>> We have the following chicken-egg problem:
>> We are using WG on openwrt devices which do not have a hardware clock so
Hello,
We have the following chicken-egg problem:
We are using WG on openwrt devices which do not have a hardware clock so
that time is resetted after each reboot.
Because internet access shall be routed via WG tunnels the internet and
network-time services (NTP) is not available unless WG works p
10 matches
Mail list logo
