* Wireguard-go: How fast wireguard-go devices startup?
@ 2020-11-03 4:28 Denis Tingajkin
0 siblings, 0 replies; only message in thread
From: Denis Tingajkin @ 2020-11-03 4:28 UTC (permalink / raw)
To: wireguard
Hello,
During testing wireguard-go device between two k8s clusters, we found that sometimes devices could long start (~30 sec) (we expected < ~15s)
Question: Do you have any benchmarks on the startup of wireguard device? (if yes, what is the duration expected?)
Logs:
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: decryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: encryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: decryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: encryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: handshake worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: decryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: decryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: encryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: handshake worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: TUN reader - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: handshake worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: encryption worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: event worker - started
INFO: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Interface set up
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: handshake worker - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: receive incoming IPv6 - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: receive incoming IPv4 - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 UDP bind has been updated
INFO: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Interface set down
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Received message with unknown type
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: receive incoming IPv6 - stopped
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:42 Routine: receive incoming IPv4 - stopped
INFO: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:43 Interface set up
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:43 Routine: receive incoming IPv6 - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:43 Routine: receive incoming IPv4 - started
DEBUG: Wireguard Device (nsmuXYqpJH5I): 2020/09/30 07:22:43 UDP bind has been updated
<---sleep here—>
Time="2020-09-30T07:23:02Z" level=info msg=">><<-- GRPC->/forwarder.Forwarder/Request()=\"\" span=43fba74bac35dba6:2e78b16ec532cd52:551cd27633276554:1"
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-11-10 13:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-03 4:28 Wireguard-go: How fast wireguard-go devices startup? Denis Tingajkin
Development discussion of WireGuard
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.vuxu.org/wireguard
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 wireguard wireguard/ http://inbox.vuxu.org/wireguard \
wireguard@lists.zx2c4.com
public-inbox-index wireguard
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://inbox.vuxu.org/vuxu.archive.wireguard
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git