From: Richard Hauswald <staenker@rhcs.de>
To: S.Guenther@in-put.de
Cc: netfilter@lists.netfilter.org
Subject: Re: Accounting with iptables vs. snmp
Date: Wed, 27 Apr 2005 00:32:35 +0200 [thread overview]
Message-ID: <426EC183.2020701@rhcs.de> (raw)
In-Reply-To: <200504262117.51465.S.Guenther@in-put.de>
Stefan-Michael. Guenther (in-put GbR) wrote:
> Hello Richard,
>
>
>>Hello Stefan,
>>maybe (!)... your problem is simple so solve. You are appending this
>>rules with the LOG target. So you will not count traffic which is
>>blocked. Just write an -I instead of -A. But i don't know if thats the
>>problem which took up to 25% of traffic difference. It sounds very
>>strange, if you say that some times you count more than your provider
>>and another day your provider counts more. Maybe you have an failure
>>based on rounding the bytes to megabytes?
>>
>
> I don't block packets on this box, there is a cisco box between the net and
> the linux box. Last wednesday the difference was about 2.6 GB in only 24
> hours!
Thats much traffic...
> The scripts doesn't do any rounding, I've switched this feature off to
> get exact results. Even with all those portscans and P2P-packets, I don't
> think that this could add up to 2.6 GB.
Sure? :-)
> And it wouldn't explain why the box
> sometimes reports more traffic that the provider.
Maybe there is another way to get access to the Internet. I mean another
way then to use the Linux box as gateway. That would explain why
sometimes more and some times less traffic is reported by your box than
from your ISP. If you have a DMZ and your traffic counter is in the DMZ,
than it will not count traffic for other DMZ servers. Is the box
directly connected to the cisco gateway? I mean using a cross over cat5?
If not, do so to exclude this failure possibility.
> Could it be that the box is to slow, to see and log all packets?
No. You are using iptables and not snort with a box connected to a
monitoring port on a switch with 100MBit and much network traffic.
> Sometimes I find lines like "last message repeated 10 times" in the logfile but my
> scripts is able to analyse these lines, too.
You could also change the LOG rule to a accept rule. If you do so, you
have to tell cron.hourly (for example) to grep/awk out the values for
the rule counters. It does not make sense with the log rule. If you
want, you can grep it out every minute. that won't produce much system
load. Try this way and test again.
> And again, this would mean equal
> or less traffic, but no more traffic than the providers reports.
And again: This sounds very strange. :-(
>
> Stefan
Richard
--
There are only 10 types of people in the world:
Those who understand binary, and those who don't
next prev parent reply other threads:[~2005-04-26 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0MKsEO-1DQUpM3MdQ-00057r@mxeu13.kundenserver.de>
2005-04-26 19:17 ` Re: Accounting with iptables vs. snmp Stefan-Michael. Guenther (in-put GbR)
2005-04-26 22:32 ` Richard Hauswald [this message]
2005-04-26 11:45 Stefan-Michael. Guenther (in-put GbR)
2005-04-26 14:15 ` Richard Hauswald
2005-04-26 19:26 ` Steven M Campbell
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=426EC183.2020701@rhcs.de \
--to=staenker@rhcs.de \
--cc=S.Guenther@in-put.de \
--cc=netfilter@lists.netfilter.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.