From: Fokin Denis <fokin33@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Too litle timeout for networkwatcher
Date: Fri, 18 Mar 2022 14:18:53 +0300 [thread overview]
Message-ID: <CAF=+C5203fZkUFSAaDR=yvAv8dtbAMPmp=q3Mg6-6zfD6yXR7g@mail.gmail.com> (raw)
Hello!
Timeout for NetworkWatcher is one minute now.
It is too little on some PC
For example about 2 minutes (i use modified version - set timeout to one hour):
2022-03-17 00:22:57.612: [TUN] [client1] Starting WireGuard/0.5.3
(Windows 6.1.7601; amd64)
2022-03-17 00:22:57.612: [TUN] [client1] Watching network interfaces
2022-03-17 00:22:57.612: [TUN] [client1] Resolving DNS names
2022-03-17 00:22:57.612: [TUN] [client1] Creating network adapter
2022-03-17 00:22:57.676: [TUN] [client1] Using existing driver 0.10
2022-03-17 00:22:57.680: [TUN] [client1] Creating adapter
2022-03-17 00:22:58.056: [TUN] [client1] Using WireGuardNT/0.10
2022-03-17 00:22:58.056: [TUN] [client1] Enabling firewall rules
2022-03-17 00:22:58.029: [TUN] [client1] Interface created
2022-03-17 00:22:58.059: [TUN] [client1] Dropping privileges
2022-03-17 00:22:58.060: [TUN] [client1] Setting interface configuration
2022-03-17 00:22:58.060: [TUN] [client1] Peer 1 created
2022-03-17 00:22:58.060: [TUN] [client1] Sending keepalive packet to
peer 1 (167.99.208.250:51820)
2022-03-17 00:22:58.060: [TUN] [client1] Sending handshake initiation
to peer 1 (167.99.208.250:51820)
2022-03-17 00:22:58.060: [TUN] [client1] Interface up
2022-03-17 00:22:58.107: [TUN] [client1] Receiving handshake response
from peer 1 (167.99.208.250:51820)
2022-03-17 00:22:58.107: [TUN] [client1] Keypair 1 created for peer 1
2022-03-17 00:23:19.329: [TUN] [client1] Sending keepalive packet to
peer 1 (167.99.208.250:51820)
2022-03-17 00:23:40.579: [TUN] [client1] Sending keepalive packet to
peer 1 (167.99.208.250:51820)
2022-03-17 00:24:01.830: [TUN] [client1] Sending keepalive packet to
peer 1 (167.99.208.250:51820)
2022-03-17 00:24:23.079: [TUN] [client1] Sending keepalive packet to
peer 1 (167.99.208.250:51820)
2022-03-17 00:24:28.038: [TUN] [client1] Monitoring MTU of default v4 routes
2022-03-17 00:24:28.107: [TUN] [client1] Setting device v4 addresses
2022-03-17 00:24:28.239: [TUN] [client1] Monitoring MTU of default v6 routes
2022-03-17 00:24:28.239: [TUN] [client1] Startup complete
2022-03-17 00:24:28.239: [TUN] [client1] Setting device v6 addresses
Maybe set timeout to 5 minutes or make setting for it ?
Thank you for great VPN!
reply other threads:[~2022-03-21 19:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAF=+C5203fZkUFSAaDR=yvAv8dtbAMPmp=q3Mg6-6zfD6yXR7g@mail.gmail.com' \
--to=fokin33@gmail.com \
--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).