Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: <mingching.tiew@redtone.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] API using cbq / tc ?
Date: Fri, 14 Feb 2003 03:58:01 +0000	[thread overview]
Message-ID: <marc-lartc-104519524006481@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104453716713244@msgid-missing>

I have yet uploaded fwstat-0.89 to

  http://www.geocities.com/mctiew/ffw/fwstat-0.89.tgz

This version of fwstat supports collection and charting of tc class/qdisc
and
iptables firewall rules.

A) For 'floppyfw', it is plug and play. Absolutely no configuration
     needed. Just copy 'fwstatp.bz2' and 'post-fwstatp.ini' into /packages.

B) For other Linux Firewall/QoS systems, you could setup similar things by
    editing post-fwstatp.ini.

B) For the Linux MRTG station, you setup MRTG,  fwstat.cfg and mrtg.cfg.

C) For Windows, use FFWGrapher.exe, downloadable from

    http://www.geocities.com/mctiew/ffw/ffwgrapher0.88.zip


-------------------------------fwstat-cfg example-------------------
# this sample configuration collects 8 different traffic data from fwtat
server 192.168.0.19
port 50000
interfaces lo0 eth0 eth1 ppp0
eth1 rx
eth1 tx
eth0 tx
ppp0 tx
eth1 class cbq 1:
eth0 qdisc htb 1:
iptables FORWARD tcp dpt:80
iptables PREROUTING tcp dpt:80 to:192.168.0.3:80



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-02-14  3:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:20 [LARTC] API using cbq / tc ? Srikanth
2003-02-07  2:28 ` S Mohan
2003-02-07  4:37 ` Srikanth
2003-02-07  7:44 ` Stef Coene
2003-02-08  7:02 ` Ming-Ching Tiew
2003-02-08 10:39 ` Stef Coene
2003-02-08 13:04 ` Ming-Ching Tiew
2003-02-08 13:22 ` Stef Coene
2003-02-09  3:45 ` Ming-Ching Tiew
2003-02-09  7:26 ` Henry Yen
2003-02-09 13:39 ` Stef Coene
2003-02-10  1:58 ` mingching.tiew
2003-02-10  8:59 ` Stef Coene
2003-02-10 18:01 ` Jay Wineinger
2003-02-10 18:20 ` Stef Coene
2003-02-11 16:59 ` Martin Devera
2003-02-11 18:16 ` Stef Coene
2003-02-12  8:29 ` devik
2003-02-12 17:45 ` Stef Coene
2003-02-13  8:30 ` devik
2003-02-13 10:36 ` mingching.tiew
2003-02-13 18:39 ` Stef Coene
2003-02-13 18:40 ` Stef Coene
2003-02-14  3:58 ` mingching.tiew [this message]

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=marc-lartc-104519524006481@msgid-missing \
    --to=mingching.tiew@redtone.com \
    --cc=lartc@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