From: paulobruck1 <paulobruck1@gmail.com>
To: netfilter@vger.kernel.org
Cc: Aleksej <aleksej05@googlemail.com>
Subject: Re: monitoring with iptables question
Date: Mon, 22 Sep 2008 15:47:20 -0300 [thread overview]
Message-ID: <1222109240.3502.50.camel@pauloric.contatogs.com.br> (raw)
In-Reply-To: <16d377d70809221125l5e3195cage4035a92352577d8@mail.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-22 18:47 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 [this message]
2008-09-23 6:34 ` Aleksej
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=1222109240.3502.50.camel@pauloric.contatogs.com.br \
--to=paulobruck1@gmail.com \
--cc=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