curvetun is hyper sensitive to time and clock drifting, needs a reliable NTP source? #141

Closed
zoobab opened this Issue Apr 21, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@zoobab

zoobab commented Apr 21, 2015

Hi,

I am raising this issue as I have had the impression that curvetun is super sensitive to clock differences.

My tunnel was not working, and when I resynced the machine with ntpdate to an NTP server, it worked again.

Could you mention somewhere in bug fat warning that you need a decent NTP clock sync to make it work properly?

@tklauser

This comment has been minimized.

Show comment
Hide comment
@tklauser

tklauser Oct 20, 2017

Contributor

This is mentioned in the manpage:

First, make sure that the servers and clients clocks are periodically

and we expect users to consult the manpage (at least in case of problems 😉), so I consider this fixed.

Contributor

tklauser commented Oct 20, 2017

This is mentioned in the manpage:

First, make sure that the servers and clients clocks are periodically

and we expect users to consult the manpage (at least in case of problems 😉), so I consider this fixed.

@tklauser tklauser closed this Oct 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment