netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 212317] New: /proc/net/dev: reversed counter for network namespaces?
Date: Wed, 17 Mar 2021 11:01:24 -0700	[thread overview]
Message-ID: <20210317110124.71b7240b@hermes.local> (raw)



Begin forwarded message:

Date: Wed, 17 Mar 2021 14:14:36 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 212317] New: /proc/net/dev: reversed counter for network namespaces?


https://bugzilla.kernel.org/show_bug.cgi?id=212317

            Bug ID: 212317
           Summary: /proc/net/dev: reversed counter for network
                    namespaces?
           Product: Networking
           Version: 2.5
    Kernel Version: 5.10.23
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: steffen@sdaoden.eu
        Regression: No

Hello.
Yesterday i extended my tmux status line to include all "network devices", and
now i am looking at a line

  RF:W~B~ wlp1s0~158/16 wg0~6/2 browse~8/124

which are /proc/net/dev devices (less in-namespace stuff) with non-0 byte
counts.
wlp1s0 is the sole connection to the internet, and browse is a network
namespace that boxes graphical browser usage, and can only access the internet,
no local services (but DNS).

As you can see it states it has send 124 MiB and receives 8 MiB, which i deem
wrong, especially since the entire up/downstream bytes of wlp1s0 state
something different.  Could it be the counts are reversed?

Thank you!!

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-03-17 18:02 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=20210317110124.71b7240b@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    /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).