Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iptables mark & iproute related !
Date: Wed, 02 Jan 2002 10:31:57 +0000	[thread overview]
Message-ID: <marc-lartc-100996869116572@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100994719519192@msgid-missing>

On Wednesday 02 January 2002 05:59, Arindam Haldar wrote:
> hi all
>
> i did the following test again but ..:( .. failed again !!
> i  need some guidance now from Gurus here..
If you execute iptables -L -v -n -t nat, you can see the byte counters for 
each rule you inserted.  Are these incremented or not if you generate some 
traffic ?

Stef

>
> iptables -A PREROUTING -t mangle -i eth1 -s ..... -j mark 101
> iptables -A PREROUTING -t nat -i eth1 -s  ... -j REDIRECT --to-port 3128
>
> tc qdisc ............... handle 101 fw flowid 1:170
>
> iptables -nvL INPUT , iptables -nvL -t mangle , iptables -nvL -t nat did
> show data passing BUT i couldnt limit bandwidth !!!
> tc -s -d class/qdisc...... command didnt show any data pasing thru--i.e
> it remained ZERO !

-- 

stef.coene@docum.org
 More QOS info : http://www.docum.org/
 Title : "Using Linux as bandwidth manager"
     

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

  reply	other threads:[~2002-01-02 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02  4:53 [LARTC] iptables mark & iproute related ! Arindam Haldar
2002-01-02 10:31 ` Stef Coene [this message]
2002-01-03 14:29 ` Arindam Haldar
2002-01-03 15:23 ` Stef Coene
2002-01-04  5:48 ` Arindam Haldar

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-100996869116572@msgid-missing \
    --to=stef.coene@docum.org \
    --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