From: "Art History" <foobear.cf@gmail.com>
To: netfilter@vger.kernel.org
Subject: sar interface stats
Date: Fri, 12 Sep 2008 12:56:05 -0600 [thread overview]
Message-ID: <14ab6e880809121156pc96d230p38a620590241e22a@mail.gmail.com> (raw)
On a RHEL5.x86_64 firewall system (one interface internet-exposed, the
other on intranet), totals for received bytes/sec and transmitted
bytes/sec, as reported by 'sar -n DEV', are always nearly equal for
both interfaces. This despite the fact that for sure the external
interface is kept very busy dropping the usual internet cruft. Do
interface 'received' statistics as maintained by the kernel NOT
reflect traffic that is DENYed/DROPed/REJECTed by netfilter (iptables)
rules, and why not? Or if it's not the case that the dropped
traffic isn't counted, why the near equality for total traffic on both
interfaces? If traffic that is REJECTed is not counted in the received
counts, are the resets or icmp unreachables also not counted in the
transmitted counts?
thanks.
next reply other threads:[~2008-09-12 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 18:56 Art History [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-12 18:21 sar interface stats val
2008-09-11 22:03 val
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=14ab6e880809121156pc96d230p38a620590241e22a@mail.gmail.com \
--to=foobear.cf@gmail.com \
--cc=netfilter@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