From: Rick Jones <rick.jones2@hp.com>
To: lartc@vger.kernel.org
Subject: Re: Traffic accounted in interface that has no ip and is not in promisc mode
Date: Thu, 06 Nov 2014 23:11:25 +0000 [thread overview]
Message-ID: <545C001D.4000704@hp.com> (raw)
In-Reply-To: <545BA547.1090201@conversis.de>
On 11/06/2014 03:00 PM, Dennis Jacobfeuerborn wrote:
> The only broadcast traffic I see is a couple of arp packets per seconds
> and there is no multicast traffic.
>
> Since this is a virtual machine that is plugged into a bridge on the
> host side I'm wondering if that might have something to do with it but
> according to my understanding even if packets were forwarded from the
> host side that are not targeted at the vm then the vm would drop these
> packets and not account them under received packets/bytes for that
> interface.
Perhaps the bridge has yet to learn the MACs involved and so is
flooding. Whether then the "NIC" driver would/should count/not count
such traffic as having been received is probably a matter of
interpretation. If you take the point of view that any packet which
came into the host should "count" then the current behaviour would seem
to make sense.
It is also interesting that this non-configured interface has
transmitted a large (though smaller than RX count) number of packets. I
would have expected your (first) tcpdump to have shows the ether host
transmitting (very) roughly one packet for every 100 received.
rick jones
next prev parent reply other threads:[~2014-11-06 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 16:43 Traffic accounted in interface that has no ip and is not in promisc mode Dennis Jacobfeuerborn
2014-11-06 17:15 ` Joel Gerber
2014-11-06 23:00 ` Dennis Jacobfeuerborn
2014-11-06 23:11 ` Rick Jones [this message]
2014-11-06 23:38 ` Dennis Jacobfeuerborn
2014-11-07 0:07 ` Rick Jones
2014-11-09 0:32 ` Dennis Jacobfeuerborn
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=545C001D.4000704@hp.com \
--to=rick.jones2@hp.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.