Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Nikolai Vladychevski <niko@isl.net.mx>
To: lartc@vger.kernel.org
Subject: [LARTC] some prio questions
Date: Mon, 25 Jun 2001 19:55:25 +0000	[thread overview]
Message-ID: <marc-lartc-99349881020133@msgid-missing> (raw)

Hello,

I have some questions about prio queue discipline, hope somebody can
clear things up. I can't find good docs about it anywehere...


1) How does mapping works? For example, in this command

tc qdisc add dev ppp0 parent 2:1 handle 1: prio \
    bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1

Does this mean I have 16 priorities mapped this way?
Priority       BAND
   1      ->     1
   2      ->     2
   3      ->     2
   4      ->     2
   5      ->     1
   6      ->     2
   7      ->     0
   8      ->     0
   9      ->     1
  10      ->     1
  11      ->     1
  12      ->     1
  13      ->     1
  14      ->     1
  15      ->     1
  16      ->     1
 
2) On my local network, I want the machine 192.168.1.1 to have the
highest priority for every tcp/udp connection, and the 192.168.1.4 the
lowest, would the following setup correct?

tc qdisc add dev ppp0 root handle 10: prio
tc filter add dev ppp0 parent 10:0 protocol ip prio 16 u32 match ip src
192.168.1.4
tc filter add dev ppp0 parent 10:0 protocol ip prio  0 u32 match ip src
192.168.1.1

I also use ip tables to masq local machines on my DialUP linux machine,
like this:
iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE

I beleive the queueing is done before the packet is sent to the ppp0
interface, so I could use src 192.168.1.XX as u32 classifier, and after
that the masquerading is applied,so my rules will be matched, is that
correct?

(I use 2.4 kernel)

Thanks in advance

Nikolai

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

                 reply	other threads:[~2001-06-25 19:55 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=marc-lartc-99349881020133@msgid-missing \
    --to=niko@isl.net.mx \
    --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