All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tóth Nándor" <nug@sch.bme.hu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why there is any traffic in default class?
Date: Mon, 31 Jan 2005 09:55:53 +0000	[thread overview]
Message-ID: <41FE00A9.6050004@sch.bme.hu> (raw)
In-Reply-To: <3cfad9ca05013101435f72a4d9@mail.gmail.com>

Hi!

Denis Kot wrote:
> I have:
> 
> tc qdisc add dev imq0 root handle 1: htb default 30
> tc class add dev imq0 parent 1: classid 1:1 htb rate 512kbit ceil 512kbit
> tc class add dev imq0 parent 1:1 classid 1:30 htb rate 64kbit ceil 512kbit
> 
> then:
> 
> iptables -t mangle -A PREROUTING  -i ppp0 -s 192.168.2.2 -j IMQ --todev 0

If i understand you correctly, it should be:
iptables -t mangle -A PREROUTING  -i ppp0 -j IMQ --todev 0
iptables -t mangle -A PREROUTING  -s 192.168.2.2 -j IMQ --todev 0

Your rule means: traffic which came from ppp0 AND has source ip 
192.168.2.2 go to IMQ.

> tc class add dev imq0 parent 1:1 classid 1:22 htb rate 64kbit ceil 128kbit
> tc filter add dev imq0 protocol ip parent 1:0 prio 1 u32 match ip src
> 192.168.2.2 flowid 1:22
> 
> so, as I understand any traffic from source 192.168.2.2 and from
> interface ppp0 must be going directly in to class 1:22, so default
> class 30 must not have any traffic. isn´t it?

This part may or may not be ok, i do not know.

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

  reply	other threads:[~2005-01-31  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31  9:43 [LARTC] why there is any traffic in default class? Denis Kot
2005-01-31  9:55 ` Tóth Nándor [this message]
2005-01-31 10:11 ` Denis Kot

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=41FE00A9.6050004@sch.bme.hu \
    --to=nug@sch.bme.hu \
    --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.