Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ server_mode ] Cannot connect , 1970-01-01 Timestamp for latest handshake, no data sent to client #343

Open
benchonaut opened this issue Apr 27, 2023 · 0 comments

Comments

@benchonaut
Copy link

benchonaut commented Apr 27, 2023

What happened ?

  • openvz machine ( yes , creepy :D )

  • trying to replace wireguard go with boringtun results in "nothing" ( no bytes sent back to client )

How did that happen ?

( before )

wireguard-go thingy
wg setconf thingy /etc/wireguard/thingy.conf

(after)

screen -dmS wireguard boringtun-cli -f --disable-drop-privileges  thingy
WG_QUICK_USERSPACE_IMPLEMENTATION=boringtun-cli           wg-quick up thingy
wireguard-go thingy

Did it produce some logs ?

Client does not receive any byte

The Server says

peer: abcde/FGEHJ=
  preshared key: (hidden)
  endpoint: w.x.y.z:49861
  allowed ips: 10.1.1.101/32, fdbe:1111:1111:110::/60
  latest handshake: 53 years, 129 days, 9 hours, 19 minutes, 16 seconds ago
  transfer: 216 B received, 486 B sent
  • regular wireguard(-go) says "never" instead of 53 years ago ( unix TS 0 == 1970-01-01)
  • regular wireguard(-go) works under same conditions

Any ideas ?

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant