linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: urgrue <urgrue@tumsan.fi>
To: admin <linux-admin@vger.kernel.org>
Subject: simple tc priorization
Date: Wed, 13 Apr 2005 15:30:32 +0300	[thread overview]
Message-ID: <20050413123032.GA2471@fede2.dev.ascom.fi> (raw)

simply put i need to prioritize one form of traffic over another. its 
okay if it even hogs up all the bandwidth. whats the simplest way to 
achieve this? a simple prio qdisc simply doesnt seem to work, for 
example:
tc qdisc add dev eth0 root handle 1: prio
tc qdisc add dev eth0 parent 1:1 handle 10: sfq
tc qdisc add dev eth0 parent 1:2 handle 20: sfq
tc filter add dev eth0 parent 1: protocol ip u32 match ip sport 19  
0xffff flowid 1:1
tc filter add dev eth0 parent 1: protocol ip u32 match ip sport 22 
0xffff flowid 1:2

but this doesnt work and it just ends up splitting traffic evenly 
between the two ports. im assuming my problem is that im not limiting 
traffic on the root level, and thus PRIO never realizes my bandwidth is 
full?
but how can i

                 reply	other threads:[~2005-04-13 12:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050413123032.GA2471@fede2.dev.ascom.fi \
    --to=urgrue@tumsan.fi \
    --cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).