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

keepalive-interval and another problem #4

Closed
XEGARE opened this issue Jul 25, 2022 · 8 comments
Closed

keepalive-interval and another problem #4

XEGARE opened this issue Jul 25, 2022 · 8 comments
Labels
bug Something isn't working

Comments

@XEGARE
Copy link

XEGARE commented Jul 25, 2022

Hello.

invalid argument for flag `/keepalive-interval' (expected time.Duration): time: missing unit in duration "20"

On the current version I get an infinite connection. Lots of tries: peer(jh1+…) - Sending handshake initiation
On the version of July 18, everything connects perfectly

@zhsj
Copy link
Owner

zhsj commented Jul 26, 2022

invalid argument for flag `/keepalive-interval' (expected time.Duration): time: missing unit in duration "20"

You should use 20s. I may add the default unit s to the argument, to align other wireguard configuration.

@zhsj
Copy link
Owner

zhsj commented Jul 26, 2022

On the current version I get an infinite connection. Lots of tries: peer(jh1+…) - Sending handshake initiation
On the version of July 18, everything connects perfectly

However commits from July 18 only affect the dns resolver, it shouldn't affect the wireguard connection...

@zhsj
Copy link
Owner

zhsj commented Jul 26, 2022

Okay, I checked my logs, and see some random Sending handshake initiation, but it doesn't seem to have any side effects?

@XEGARE
Copy link
Author

XEGARE commented Jul 26, 2022

Okay, I checked my logs, and see some random , but it doesn't seem to have any side effects?Sending handshake initiation

It has. It doesn't connect.
f

@zhsj
Copy link
Owner

zhsj commented Jul 26, 2022

Could you check the log with prefix Device config:, and see if it's same with the version of July 18?

I have no clue that the changes since July 18 will affect the connection.

If the version of July 18 works, you can help me narrowing down the bug, by using git bisect. Or if you don't know how to use git bisect, you can just checkout each commit since July 18, and find the first commit that breaks the connection.

@XEGARE
Copy link
Author

XEGARE commented Jul 26, 2022

July 18

s

s

@XEGARE
Copy link
Author

XEGARE commented Jul 26, 2022

git bisect

4dc0f8e is the first bad commit

@zhsj
Copy link
Owner

zhsj commented Jul 26, 2022

Thanks, I now know what happens.

@zhsj zhsj added the bug Something isn't working label Jul 26, 2022
@zhsj zhsj closed this as completed in 56268e4 Jul 26, 2022
zhsj added a commit that referenced this issue Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants