From: Bob Miller <bob@computerisms.ca>
To: Marek Kierdelewicz <marek@piasta.pl>
Cc: netfilter@vger.kernel.org
Subject: Re: iptaccount/shaping
Date: Thu, 01 Sep 2011 12:47:56 -0700 [thread overview]
Message-ID: <1314906476.28901.608.camel@worklian.computerisms.bob> (raw)
In-Reply-To: <20110901201918.390de5b4@catus>
On Thu, 2011-09-01 at 20:19 +0200, Marek Kierdelewicz wrote:
> >Hello,
>
> Hi,
Marek, thank you *very* much for your response.
>
> >I have a firewall that provides internet to two networks, a private one
> >...
> >My question is: is it somehow possible I am leaking data on my outside
> >port that would trigger the ISP counter but not iptaccount? Is there
> >some layer 2 traffic of which I am not aware that would tell the ISP
> >what the intended traffic before shaping might be? I have been dumping
> >and analyzing traffic for hours and found nothing, but maybe there is
> >something I don't know about that would explain this.
>
> First of all try to compare isp data with what you see on ethernet
> interface connected to that isp:
> ip link show -s dev ethX
>
> You should get something like this:
>
> RX: bytes packets errors dropped overrun mcast
> 714301652 713443 0 0 0 3494
> TX: bytes packets errors dropped carrier collsns
> 79328329 501677 0 0 2 0
>
> Stats show actual data sent/received (since reboot) including layer2
> headers. Gathered data should exacly match your isp stats.
>
I think this is exactly the kind of tool I am looking for.
When I ran the command I found my numbers didn't add up to even close to
what bandwidth usage should have been since last reboot, and a bit of
investigation says that is because the byte count will wrap. This will
require some creativity to use this tool properly, but should provide at
least some of the answers I seek.
Thank you again :)
--
Bob Miller
334-7117/660-5315
http://computerisms.ca
bob@computerisms.ca
Network, Internet, Server,
and Open Source Solutions
next prev parent reply other threads:[~2011-09-01 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 16:33 iptaccount/shaping Bob Miller
2011-09-01 18:19 ` iptaccount/shaping Marek Kierdelewicz
2011-09-01 19:47 ` Bob Miller [this message]
2011-09-01 20:44 ` iptaccount/shaping Jan Engelhardt
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=1314906476.28901.608.camel@worklian.computerisms.bob \
--to=bob@computerisms.ca \
--cc=marek@piasta.pl \
--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;
as well as URLs for NNTP newsgroup(s).