From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: wireguard@lists.zx2c4.com
Subject: TX counters not updated on wireguard interface
Date: Sat, 13 May 2017 09:08:43 +0200 [thread overview]
Message-ID: <20170513070843.GB22218@tuxmachine.polynome.dn42> (raw)
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Hi,
While trying 0.0.20170421-2 on Debian jessie, I noticed that the TX
counters are not updated:
$ ip -s link show
7: wg: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/none
RX: bytes packets errors dropped overrun mcast
4384059324 4073303 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
This is after a bidirectional TCP iperf, so they has been some trafic in
both directions. Bandwidth monitors like bmon also don't show any
outgoing trafic.
Baptiste
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-05-13 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 7:08 Baptiste Jonglez [this message]
2017-05-13 22:53 ` Jason A. Donenfeld
2017-05-13 23:17 ` Jason A. Donenfeld
2017-05-14 12:34 ` Jason A. Donenfeld
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=20170513070843.GB22218@tuxmachine.polynome.dn42 \
--to=baptiste@bitsofnetworks.org \
--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).