Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Sellaro <sellaro@email.it>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems with HTB
Date: Mon, 04 Feb 2002 11:07:56 +0000	[thread overview]
Message-ID: <marc-lartc-101282088305225@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 2709 bytes --]

Hi folks

I've read Advanced Routing HOWTO and decided to implement some concepts
on a network I manage. I am trying to set up a simple HTB-based traffic
shaping with four classes on my firewall machine (2.4.17 HTB patch
applied. iproute2 compiled with HTB patch, PH_ECHO line removed).
Firewall box has two interfaces: eth0 - 172.18.200.1/24 and eth1 - to
Internet.

Class 1:10 and 1:12 has a 76 kbps rate (max of 256 kbps).
Class 1:11 has a 54 kbps rate (max of 256 kpbs).
Class 1:13 has a 50 kbps rate (max of 256).

Filters are quite simple:

Traffic from IPs 172.18.200.223 to 172.18.200.226 should go to class
1:10. Traffic from IPs 172.18.200.2 and 172.18.200.4 should go to class
1:11. Traffic from IP 172.18.200.232 should go to class 1:12. All other
traffic must follow 1:13.

The problem is also simple: nothing is being filtered. All traffic
follow 1:13. I'm quite frustrated and really don't know what could be
wrong. I've talked to a few fellows at #lartc on Open Projects, but it
also didn't work.

This is what I am using for creation of this scenario:

tc qdisc add dev eth0 root handle 1: htb default 13

tc class add dev eth0 parent 1: classid 1:1 htb rate 256kbit ceil 2mbit
burst 15k

tc class add dev eth0 parent 1:1 classid 1:10 htb rate 76kbit ceil
256kbit burst 15k

tc class add dev eth0 parent 1:1 classid 1:11 htb rate 54kbit ceil
256kbit burst 15k

tc class add dev eth0 parent 1:1 classid 1:12 htb rate 76kbit ceil 
256kbit burst 15k

tc class add dev eth0 parent 1:1 classid 1:13 htb rate 50kbit ceil
256kbit burst 15k

tc qdisc add dev eth0 parent 1:10 handle 10: sfq perturb 10
tc qdisc add dev eth0 parent 1:11 handle 20: sfq perturb 10
tc qdisc add dev eth0 parent 1:12 handle 30: sfq perturb 10
tc qdisc add dev eth0 parent 1:13 handle 40: sfq perturb 10

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip src
172.18.200.223 flowid 1:10

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip src
172.18.200.224 flowid 1:10

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip src
172.18.200.225 flowid 1:10

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip src
172.18.200.226 flowid 1:10

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip src
172.18.200.2 flowid 1:11

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip src
172.18.200.4 flowid 1:11

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip src
172.18.200.232 flowid 1:12
-- 
Sellaro

Agente Livre - Linux Community (www.agentelivre.org)

PGP Key ID: 3ADF8645
PGP Key Fingerprint: 6AB0 D60B 69B5 B3F9 4553  2242 A1D0 17C0 3ADF 8645

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2002-02-04 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04 11:07 Sellaro [this message]
2002-02-04 17:26 ` [LARTC] Problems with HTB Martin Devera

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-101282088305225@msgid-missing \
    --to=sellaro@email.it \
    --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