All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] prio qdisc problem
Date: Thu, 13 Feb 2003 18:33:47 +0000	[thread overview]
Message-ID: <marc-lartc-104516153329620@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104515101911481@msgid-missing>

On Thursday 13 February 2003 17:53, Esteban wrote:
> Hello there,
> I'm trying to do some prio qdisc, but it doesn't seem to work.
> Can anybody tell me why ???
> here is my simple prio qdisc script:
>
>
>
> OPTIONS="bandwidth 100mbit allot 1514 maxburst 20 prio 3 avpkt 1000"
> IPTABLES="/usr/local/bin/iptables.static"
> INTERNAL=eth0
> EXTERNAL=eth1
>
>
> tc qdisc del dev eth0 root 2>/dev/null
> tc qdisc add dev eth0 root handle 10: cbq bandwidth 100mbit avpkt 1000
> tc class add dev eth0 parent 10: classid 10:1 cbq rate 512kbit bounded
> $OPTIONS
>
> tc qdisc add dev eth0 parent 10:1 handle 20: prio
>
>
> tc filter add dev eth0 parent 10: protocol ip prio 100 u32 \
> match ip protocol 0x01 0xff \
> flowid 20:1
> tc filter add dev eth0 parent 10: protocol ip prio 100 u32 \
> match ip dport 110 0xffff \
> flowid 20:2
> tc filter add dev eth0 parent 10: protocol ip prio 100 u32 \
> match ip src 0.0.0.0/0 \
> flowid 20:3
>
>
> Is it the correct way to do that ?
No.
Create a catch all filter that redirect all traffic to 10:1 (tc filter add u32 
src 0.0.0.0/0 flowid 10:1 or something like that).  And add your 3 filters to 
the 20: class.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

      reply	other threads:[~2003-02-13 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 15:43 [LARTC] prio qdisc problem Esteban
2003-02-13 18:33 ` Stef Coene [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-104516153329620@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 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.