From: Aleksej <aleksej05@googlemail.com>
To: netfilter@vger.kernel.org
Subject: Re: monitoring with iptables question
Date: Tue, 23 Sep 2008 08:34:48 +0200 [thread overview]
Message-ID: <16d377d70809222334i2c5c506aj4c41e31339095efa@mail.gmail.com> (raw)
In-Reply-To: <1222109240.3502.50.camel@pauloric.contatogs.com.br>
Thanks for the links, I'm reading it now, but there is a lot of information...
My problem is that I don't know how much available bandwidth I have
(this is about wireless networks). Otherwise I could just calculate
the total throughput on the interface and see if there is some free
bandwidth left. Can one with linux traffic control tools or iptables
derive the load of interface/queue? The only thing I need to know is
whether the output transmission queue can cope with all the traffic
waiting for transmission, in other words, is the queue full loaded or
not.
Thanks,
Aleksej.
2008/9/22 paulobruck1 <paulobruck1@gmail.com>:
> Em Seg, 2008-09-22 às 20:25 +0200, Aleksej escreveu:
>> Hi,
>>
>
> Hi
>
>> I know that iptables can be used for some monitoring tasks. Is it
>> possible to solve the following task with iptables?
>>
>> Let's say I have an application that generates 20 Mbps data for
>> transmission, but due to high network load only 10Mbps is actually
>> transmitted. So, the output transmission queue is always loaded with
>> packets waiting for transmission. Is it possible to see somehow with
>> iptables that the output transmission queue is always busy? Or maybe
>> it is possible to count how many packets were generated for
>> transmission and how many packets have been actually transmitted?
>>
>> I need this for monitoring the queue load. The main task is to monitor
>> what portion of time the output transmission queue is empty/busy.
>>
> Instead of only monitor what about shape/priorize?? see :
>
>
> http://lartc.org/howto
>
> http://www.linuxfoundation.org/en/Net:IFB
>
> best regards
>
>
>> Thanks for any hints!!
>>
>> Aleksej.
>> --
>> To unsubscribe from this list: send the line "unsubscribe netfilter" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2008-09-23 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 18:25 monitoring with iptables question Aleksej
2008-09-22 18:47 ` paulobruck1
2008-09-23 6:34 ` Aleksej [this message]
2008-09-23 7:27 ` Vladislav Kurz
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=16d377d70809222334i2c5c506aj4c41e31339095efa@mail.gmail.com \
--to=aleksej05@googlemail.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